From: Milton Miller <miltonm@bga.com>
To: Krzysiek.Taraszka@sullivan.realtime.net (dzimi@pld.org.pl)
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Date: Sat, 31 Aug 2002 18:32:51 -0500 (CDT) [thread overview]
Message-ID: <200208312332.g7VNWpL37633@sullivan.realtime.net> (raw)
In-Reply-To: <Pine.LNX.4.44L.0208301938150.24037-200000@ep09.kernel.pl>
At Fri Aug 30 2002 - 12:54:37 EST Krzysiek Taraszka (dzimi@pld.org.pl) wrote:
> Great work, but in 2.2.22rc2 powerpc's still broken.
> First of All Sources have got a lot of unsed stuff.
> For example look like that:
>
> [dzimi@cyborg linux]$ rgrep -n -R '*.*' 'CONFIG_PPC64' .
...
Doesn't sound like -rc (release canidate) changes.
> Second kernel-2.2.21 still have got time init problems in symbios driver
> on powerpc platform.
> I send to you my ugly hack witch work, but IMHO he's ugly ;) I need to do
> it correct.
> Third, kernel for powerpc boot and work on g3-266 but on g3-333 Ops ...
> (kernel traps, kernel wrote: Caused by SRR1 or somethink like that, in 2.3
> i saw #define FIX_SRR1 macro ...)
Well, SRR1 doesn't cause traps, but it does help tell you why they occurred.
And the FIX_SRR1 stuff isn't the solution either if you look at it closer.
How about a decoded oops? Also, you didn't say what platform you were using.
As far as the open-pic changes you posted, how about explaining what your
trying to fix (partly hidden by the rename and move to chrp_setup.c from
open_pic.c)?
I see you are wrapping the 8259 checks, but it also refers to a few new
functions/macros I didn't see defined.
How about discussing these problems and patches over at
linuxppc-dev@lists.linuxppc.org ? (I set the reply-to there).
milton
prev parent reply other threads:[~2002-08-31 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 14:55 Linux 2.2.22rc2 Alan Cox
2002-08-30 17:54 ` Krzysiek Taraszka
2002-08-31 23:32 ` Milton Miller [this message]
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=200208312332.g7VNWpL37633@sullivan.realtime.net \
--to=miltonm@bga.com \
--cc=Krzysiek.Taraszka@sullivan.realtime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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
all inboxes | Powered by JetHome®