lkcd
[Top] [All Lists]

Re: lcrash for powerpc linux

To: tinglett@xxxxxxxxxx
Subject: Re: lcrash for powerpc linux
From: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
Date: Tue, 15 Aug 2000 11:09:34 -0700 (PDT)
Cc: lkcd@xxxxxxxxxxx
In-reply-to: <OF6E0BA60F.4D19E36A-ON8625693B.004B640A@RCHLAND.IBM.COM>
Sender: owner-lkcd@xxxxxxxxxxx
On Mon, 14 Aug 2000 tinglett@xxxxxxxxxx wrote:
|>Hello all...just joined this list and hope there's someone out there :).
|>
|>I work on the PowerPC Linux team within IBM (concentrating on RS/6000
|>hardware of course) and thought it would be useful to have lkcd work on
|>32-bit powerpc.  I snagged the 2.0.1 sources last week and have it more or
|>less running on a 2.4.0-test5 kernel (i.e. you did a good job separating
|>architecture dependent code).  I'm still learning what current function
|>exists, but the main function missing so far is a traceback which I'll
|>start working on this week.

The traceback and disassemble functions are the key to getting LKCD
up and running.

|>I'll need to run this by our legal, but they are used to talking to us so
|>it should go pretty fast.  Since I just joined this list I'm not sure how
|>you guys are handling changes such as this.  Any advice?  I can certainly
|>send a patch to the list, but there is probably a better way considering
|>it's size.

Well, you can send us your SourceForge login, and you can check in the
sources (my guess is there is no direct conflicts with what we're
currently doing development on, and that your stuff is architecture
specific).  If so, let us know the login, and you can check the code
into SourceForge.

Hey, the more, the merrier.  Code reviewing's the easy part. :)

|>-Todd Inglett

--Matt


<Prev in Thread] Current Thread [Next in Thread>