RE: [ECOS] CYG_TRACE thread safe?

RE: [ECOS] CYG_TRACE thread safe?

[Trenton D. Adams]

  > > Is there any way you can confirm this?  Afterall, 
  > downloading over 
  > > serial really bytes.  It takes forever.
  > 
  > Sure, want a support contract? ;-)
  > 

At roughly $1000 per hour, I don't think so! ;-)

  > My theory is that the ethernet hardware will have been 
  > configured to generate interrupts when its ready to 
  > transmit, or other status events. But diag output is done 
  > with interrupts disabled. Look at the driver code for your 
  > ethernet card to see how it works with interrupts.
  > 

Ok, thanks.

Re: [ECOS] CYG_TRACE thread safe?

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
>   > > Is there any way you can confirm this?  Afterall,
>   > downloading over
>   > > serial really bytes.  It takes forever.
>   >
>   > Sure, want a support contract? ;-)
> 
> At roughly $1000 per hour, I don't think so! ;-)

I feel I need to comment on this in case this impression sticks in people's
minds.

I don't know where you got that figure from, not least because the support
is based on "incidents" not time. So if it takes us days to find and fix
problems for you, we'll do it! If someone at Red Hat told you this, mail me
off the list as they shouldn't have.

As for the actual cost - it varies a lot depending on the target, whether
there's any custom development required, etc.etc. I don't know if we are
able to provide any general guidelines publically here on the list. Paul?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] CYG_TRACE thread safe?

[Trenton D. Adams]

  > 
  > "Trenton D. Adams" wrote:
  > >
  > >   > > Is there any way you can confirm this?  Afterall,
  > >   > downloading over
  > >   > > serial really bytes.  It takes forever.
  > >   >
  > >   > Sure, want a support contract? ;-)
  > >
  > > At roughly $1000 per hour, I don't think so! ;-)
  > 
  > I feel I need to comment on this in case this impression sticks in
  > people's
  > minds.
  > 
  > I don't know where you got that figure from, not least because the
  > support
  > is based on "incidents" not time. So if it takes us days to find and
fix
  > problems for you, we'll do it! If someone at Red Hat told you this,
mail
  > me
  > off the list as they shouldn't have.
  > 
  > As for the actual cost - it varies a lot depending on the target,
  > whether
  > there's any custom development required, etc.etc. I don't know if we
are
  > able to provide any general guidelines publically here on the list.
  > Paul?
  > 

I thought I seen it on your website.  $40,000 for roughly 40 hours of
support or something like that.  I could be wrong though, maybe it was
40 incidents.

Re: [ECOS] CYG_TRACE thread safe?

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> I thought I seen it on your website.  $40,000 for roughly 40 hours of
> support or something like that.  I could be wrong though, maybe it was
> 40 incidents.

I've found it. This looks like it is out of date. We'll get this resolved
internally.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] CYG_TRACE thread safe?

[Trenton D. Adams]

Oops, forgot the cc once again.  To early in the morning I guess.

I updated to latest CVS yesterday.  I set it to compile over night, and
when I get back this morning, it doesn't freeze anymore.  Where do I get
the list of changes in the last couple of weeks to the eCos sources?

  > -----Original Message-----
  > From: jlarmour@cambridge.redhat.com 
  > [ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
  > Sent: Thursday, July 12, 2001 8:53 AM
  > To: Trenton D. Adams
  > Subject: Re: [ECOS] CYG_TRACE thread safe?
  > 
  > 
  > "Trenton D. Adams" wrote:
  > > 
  > >   > My theory is that the ethernet hardware will have been
  > >   > configured to generate interrupts when its ready to
  > >   > transmit, or other status events. But diag output is done
  > >   > with interrupts disabled. Look at the driver code for your
  > >   > ethernet card to see how it works with interrupts.
  > >   >
  > > Oh, one other thing.  Does it disable interrupts just during the 
  > > CYG_TRACEx call?
  > 
  > Yes.
  > 
  > >  If so, I should probably use diag_printf () in between #ifdef 
  > > CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT and #endif right?
  > 
  > Worth a go.
  > 
  > Jifl
  > -- 
  > Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: 
  > +44 (1223) 271062 Maybe this world is another planet's Hell 
  > -Aldous Huxley || Opinions==mine Come to the Red Hat 
  > TechWorld open source conference in Brussels!
  > Keynotes, techie talks and exhibitions    
  > http://www.redhat-techworld.com/
  > 

RE: [ECOS] CYG_TRACE thread safe?

[Trenton D. Adams]

Oops, forgot the cc.

  > 
  > I was going to say yes, but it just occurred to me that 
  > what probably _doesn't_ work is tracing when you are 
  > debugging over ethernet because interrupts get disabled. 
  > The hardware might get all worked up for various reasons.
  > 
  > If that's what Trenton is doing, that could be the problem.

Is there any way you can confirm this?  Afterall, downloading over
serial really bytes.  It takes forever.

Re: [ECOS] CYG_TRACE thread safe?

[Jonathan Larmour]

rob.wj.jansen@philips.com wrote:
> 
> Trenton,
> 
> > I'm wondering if CYG_TRACEx is thread safe!  Is it?
> >
> > My driver was locking up in a DSR.  Now that TRACING and ASSERTIONS
> > aren't working my program doesn't lock up.
> 
> Are you using CYG_TRACEx from within the DSR ?
> I'm not sure if it is safe to use tracing from within DSRs (Jonathan ?).

I was going to say yes, but it just occurred to me that what probably
_doesn't_ work is tracing when you are debugging over ethernet because
interrupts get disabled. The hardware might get all worked up for various
reasons.

If that's what Trenton is doing, that could be the problem.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

Re: [ECOS] CYG_TRACE thread safe?

[rob.wj.jansen]

Trenton,

> I'm wondering if CYG_TRACEx is thread safe!  Is it?
>
> My driver was locking up in a DSR.  Now that TRACING and ASSERTIONS
> aren't working my program doesn't lock up.

Are you using CYG_TRACEx from within the DSR ?
I'm not sure if it is safe to use tracing from within DSRs (Jonathan ?).

Regards,

     Rob Jansen

Software Engineer
Competence Center Platforms
BU Mobile Communications
Meijhorst 60-10, 6537 KT Nijmegen, The Netherlands
Tel: +31-24-353-6329
Fax: +31-24-353-3613
mailto:Rob.WJ.Jansen@philips.com

Re: [ECOS] CYG_TRACE thread safe?

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> I'm wondering if CYG_TRACEx is thread safe!  Is it?

It's meant to be. If it isn't it's a bug.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

[ECOS] CYG_TRACE thread safe?

[Trenton D. Adams]

I'm wondering if CYG_TRACEx is thread safe!  Is it?  

My driver was locking up in a DSR.  Now that TRACING and ASSERTIONS
aren't working my program doesn't lock up.