All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Conn Clark <clark@esteem.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How much easier makes owning a BDI2000 things?
Date: Tue, 09 Nov 2004 20:51:36 +0100	[thread overview]
Message-ID: <20041109195141.82111C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 09 Nov 2004 09:27:59 PST." <4190FE1F.4080105@esteem.com>

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.


Best regards,

Wolfgang Denk

-- 
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Name one thing windows is better than unix in?
                                          Making money for Microsoft?
         -- Randal L. Schwartz in <8cvi5t4c3t.fsf@gadget.cscaper.com>

  reply	other threads:[~2004-11-09 21:10 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 [this message]
2004-11-10  1:05     ` Conn Clark
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=20041109195141.82111C1430@atlas.denx.de \
    --to=wd@denx.de \
    --cc=clark@esteem.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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.