From: Jon Masters <jonmasters@gmail.com>
To: Piotr Perak <peri@aqua.aspd.pwr.wroc.pl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6.x on 405CR
Date: Wed, 29 Sep 2004 12:58:46 +0100 [thread overview]
Message-ID: <35fb2e59040929045822511b4b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0409291256250.3154-100000@aqua.aspd.pwr.wroc.pl>
On Wed, 29 Sep 2004 13:20:17 +0200 (CEST), Piotr Perak
<peri@aqua.aspd.pwr.wroc.pl> wrote:
> I'm a trainee in some firm. They use 2.4.23 now in their boxes.
Well you and I have the 2.4.23 bit in common. I'm the entire kernel
team in the company I work at, which is somewhat fun. Also means lists
like this are really useful on occasion.
> Porting 2.6.8.1 to their board is my project. I was told that they have some
> hardware debbuger, but it doesn't work with virtual memory.
I don't have one capable of working with virtual memory but I do have
a JTAG debugger since JTAG is used to program all of our boards - and
using insight with a large cup of coffee, System.map and the output of
a full objdump of the kernel binary in combination with modifying the
code in memory to insert infinate loops or changing the mode in the
MSR usually works for me. Seriously, if you don't have a vm capable
debugger that's a lot of masochistic fun to be had debugging.
Jon.
next prev parent reply other threads:[~2004-09-29 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 10:46 2.6.x on 405CR Piotr Perak
2004-09-27 13:57 ` Matt Porter
2004-09-27 14:10 ` Jon Masters
2004-09-27 15:16 ` Matt Porter
2004-09-27 16:24 ` Piotr Perak
2004-09-28 9:57 ` Piotr Perak
2004-09-28 13:44 ` Matt Porter
2004-09-28 15:47 ` Piotr Perak
2004-09-28 16:43 ` Matt Porter
2004-09-28 17:00 ` Mark Chambers
2004-09-29 11:20 ` Piotr Perak
2004-09-29 11:58 ` Jon Masters [this message]
2004-09-29 13:22 ` Mark Chambers
2004-09-29 14:22 ` Jon Masters
2004-09-27 15:19 ` Matt Porter
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=35fb2e59040929045822511b4b@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=peri@aqua.aspd.pwr.wroc.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).