From: Christian Kujau <evil@g-house.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc32 lockups with 2.6
Date: Fri, 14 Nov 2003 00:56:04 +0100 [thread overview]
Message-ID: <3FB41A14.3040108@g-house.de> (raw)
In-Reply-To: <20031113174745.GA11560@ip68-0-152-218.tc.ph.cox.net>
Tom Rini wrote:
>
> Ok, it's been a while since anyone tried KGDB it seems. The following
> is an untested (yet) patch that makes it compile and maybe work:
>
> ===== arch/ppc/Kconfig 1.46 vs edited =====
[...]
ok, i could have done the stuff in Kconfig though, next time i will do
so at once. well, compiling wnt fine on the ppc now (my i386 cross
compile is still pending), but the things with the serial console will
have to wait now. hm, i'm not online at the weekend, so don't expect
much results these days. thank you very much for checking back to this
issue, i (and hopefully some other PreP people out there) really
appreciate this.
Christian.
PS: oh, will this patch reach mainline anytime soon?
--
BOFH excuse #433:
error: one bad user found in front of screen
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-13 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 20:31 ppc32 lockups with 2.6 Christian Kujau
2003-11-06 21:34 ` Christian
2003-11-10 18:50 ` linas
2003-11-10 20:32 ` Tom Rini
2003-11-10 22:39 ` Christian
2003-11-10 23:57 ` linas
2003-11-11 0:25 ` Christian
2003-11-11 15:36 ` Tom Rini
2003-11-13 0:59 ` Christian Kujau
2003-11-13 17:47 ` Tom Rini
2003-11-13 23:56 ` Christian Kujau [this message]
2003-11-14 15:57 ` Tom Rini
2003-11-18 12:33 ` Christian Kujau
2003-11-18 14:14 ` Christian Kujau
2003-11-21 15:25 ` Christian Kujau
2003-11-21 17:54 ` Tom Rini
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=3FB41A14.3040108@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 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).