From: Robert E Brose II <bob@kunk.jriver.com>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Subject: Re: SOLVED: mesh SCSI bus locks hard on 7500 when burning a CD-R in
Date: Mon, 5 Feb 2001 13:53:31 -0600 (CST) [thread overview]
Message-ID: <20010205195429.18772.qmail@kunk.jriver.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102051934180.18886-100000@opal.biophys.uni-duesseldorf.de> "from Michael Schmitz at Feb 5, 2001 08:28:21 pm"
User Michael Schmitz says:
>
> Unless Paul had specific reasons not to use the generic NCR53C9x driver
> code for the mac53c94 driver, I'd say we should start from scratch using
> the generic driver code base. I know it looks messy and a lot of the Sparc
> cruft should be stripped out (IIRC Sparc still uses esp.c) but it might be
> worth the trouble.
>
> Problem is, the only Powermacs I could use for testing are a 7100 and a G3
> (233 MHz desktop). Which one of these does use the 53C94?
I just did some online searching and wasn't able to find out. I
think the easiest way to find out would be to boot a kernel on each
machine and check the dmesg. You could just use a YDL or LPPC install
CD on the G3-233 but the 7100 is NuBus so you'd need to try the
experimental NuBus kernel.
I have a spare 7200 which I can use for testing as well.
Bob
--
Robert E. Brose II N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-05 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 2:39 SOLVED: mesh SCSI bus locks hard on 7500 when burning a CD-R in Robert E Brose II
2001-02-05 19:28 ` Michael Schmitz
2001-02-05 19:53 ` Robert E Brose II [this message]
2001-02-06 4:01 ` Takashi Oe
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 7:38 Iain Sandoe
2001-02-06 13:20 ` Tony Mantler
2001-02-06 17:41 ` Michael Schmitz
2001-02-06 18:27 ` Daniel Eisenbud
2001-02-06 21:01 ` Michael Schmitz
2001-02-07 10:51 ` Geert Uytterhoeven
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=20010205195429.18772.qmail@kunk.jriver.com \
--to=bob@kunk.jriver.com \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).