From: Conn Clark <clark@esteem.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How much easier makes owning a BDI2000 things?
Date: Tue, 09 Nov 2004 17:05:16 -0800 [thread overview]
Message-ID: <4191694C.60305@esteem.com> (raw)
In-Reply-To: <20041109195141.82111C1430@atlas.denx.de>
Wolfgang Denk wrote:
> In message <4190FE1F.4080105@esteem.com> you wrote:
>
>> Its worth it weight in gold bringing up custom boards the first time
>>and writing/debuging the boot rom. It allows you to change register
>
>
> ... or when debugging the Linux kernel, device drivers and especially
> RTAI real-time modules (because you can really freeze the CPU state,
> including timers etc.).
>
>
>> We haven't used ours much for debugging once things were up and
>>running(we have fallen back to using printk statements for debugging).
>>Though it can be used for that and some core kernel developers do use
>>it. (probably for debugging the printk code of the kernel ;-) )
>
>
> Seems you never had to deal with any time critical problems, then.
>
I have, however I used I/O bits and an Oscilliscope ;-)
>
> Best regards,
>
> Wolfgang Denk
>
Best Regards
-- Conn Clark
*****************************************************************
Give a man a match and you heat him for a moment. Set him on fire
and you'll heat him for life.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
next prev parent reply other threads:[~2004-11-10 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 14:33 How much easier makes owning a BDI2000 things? Peter Asemann
2004-11-09 17:27 ` Conn Clark
2004-11-09 19:51 ` Wolfgang Denk
2004-11-10 1:05 ` Conn Clark [this message]
2004-11-11 7:22 ` Sam Song
2004-11-08 14:44 VanBaren, Gerald (AGRE)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4191694C.60305@esteem.com \
--to=clark@esteem.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.