From: Johnnie Peters <jpeters@phx.mcd.mot.com>
To: Cort Dougan <cort@ppc.kernel.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: new bootloader
Date: Tue, 16 Mar 1999 07:58:37 -0700 [thread overview]
Message-ID: <36EE719D.EF7C5C6D@phx.mcd.mot.com> (raw)
In-Reply-To: Pine.LNX.3.96.990316032305.21674A-100000@persephone.cs.nmt.edu
Hi Cort,
I have it running. I had some troubles with 2.2.2. The SCSI system tended
to lock up after awhile but this seems to be gone on 2.2.3. The only thing
I have so far noticed is that when compiled with SMP enabled, the 2.2.2
release hung during semaphore handling in the SCSI driver and in 2.2.3 it
panics at the same place. I traced it down that far but have not had the time
to
go further.
I was glad to see that you have merged in the open firmware changes from
Gary Thomas. I am finally preparing a patch of all the stuff I have been
doing
and will get that to you today.
Johnnie
Cort Dougan wrote:
> Has anyone tried it yet? I haven't had any complaints and it's hard to
> believe it works for everyone as it is now.
>
> If you haven't tried it and were having trouble before please do give it a
> test. Even if you can't give me patches for your hardware a quick
> description of the problem will help me get things in position to work
> sooner.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-16 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 10:24 new bootloader Cort Dougan
1999-03-16 14:58 ` Johnnie Peters [this message]
1999-03-16 19:23 ` Benjamin Herrenschmidt
1999-03-17 1:55 ` Michael Meissner
1999-03-17 8:05 ` Cort Dougan
1999-03-17 14:38 ` Gary Thomas
1999-03-23 3:27 ` Michael Meissner
1999-03-23 13:39 ` Michael Meissner
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=36EE719D.EF7C5C6D@phx.mcd.mot.com \
--to=jpeters@phx.mcd.mot.com \
--cc=cort@ppc.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;
as well as URLs for NNTP newsgroup(s).