From: Matthew Wilcox <willy@debian.org>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: Matthew Wilcox <willy@debian.org>,
Gavin Hubbard <ghub005@xtra.co.nz>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Presicionbook success
Date: Wed, 16 Apr 2003 14:44:33 +0100 [thread overview]
Message-ID: <20030416134433.GP30643@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0304161432590.28370-100000@sal.ucc.ie>
On Wed, Apr 16, 2003 at 02:36:25PM +0100, M. Grabert wrote:
> On Wed, 16 Apr 2003, Matthew Wilcox wrote:
>
> > On Thu, Apr 17, 2003 at 01:15:31AM +1200, Gavin Hubbard wrote:
> > > Before anyone loses too much sleep over this, the Precisionbook has
> > > internal SCSI-IDE bridges that sit between the HBA and the drives. I
> > > believe a similar system was used in some of the earlier Apple Powerbooks.
> >
> > Yep, someone pointed that out in an earlier email. I'm just trying to
> > figure out how to handle this for the best.
> >
> > 1) Provide a pci quirk that deletes the IDE device from the bus
> > 2) Hack the IDE driver to not claim that device if it's on a PrecisionBook
> > 3) Ignore the scsi device and let the IDE driver drive the chips
> > 4) Er.. something else.
>
> The initialization of the CMD PCI0643 IDE controller fails when using
> the ESIEE kernel (which has support built-in for this chip).
> Something like "failed to get IRQ, will probe later".
Oh, I thought you said the kernel hung when probing with this driver.
If it just whines about being unable to do anything, that's no problem.
> So no devices were found on the IDE bus, just on the LASI SCSI.
> Probably it's the best just to use SCSI and not to use IDE support at all ...
*nod*. It might be fun for someone to play with fixing the IDE driver,
but I don't think that's necessary.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-04-16 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030416123824.22413.48893.Mailman@dsl2.external.hp.com>
2003-04-16 13:15 ` [parisc-linux] Re: Presicionbook success Gavin Hubbard
2003-04-16 13:27 ` Matthew Wilcox
2003-04-16 13:36 ` M. Grabert
2003-04-16 13:44 ` Matthew Wilcox [this message]
2003-04-16 13:48 ` M. Grabert
2003-04-16 15:02 ` Alan Cox
2003-04-16 14:00 "Beerse, Corné"
2003-04-16 14:09 ` M. Grabert
2003-04-16 14:15 ` Matthew Wilcox
2003-04-16 14:20 ` Bjorn Helgaas
2003-04-16 14:41 ` Alan Cox
2003-04-17 1:18 ` Stan Sieler
2003-04-18 4:41 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 14:13 "Beerse, Corné"
2003-04-16 14:18 ` M. Grabert
2003-04-16 15:05 "Beerse, Corné"
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=20030416134433.GP30643@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=ghub005@xtra.co.nz \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@cs.ucc.ie \
/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