From: "\"Beerse, Corné\"" <c.beerse@torex-hiscom.nl>
To: "'M. Grabert'" <xam@cs.ucc.ie>, Matthew Wilcox <willy@debian.org>
Cc: Gavin Hubbard <ghub005@xtra.co.nz>, parisc-linux@lists.parisc-linux.org
Subject: RE: [parisc-linux] Re: Presicionbook success
Date: Wed, 16 Apr 2003 16:00:52 +0200 [thread overview]
Message-ID: <03Apr16.162029cest.119065@ns.hiscom.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
> -----Original Message-----
> From: M. Grabert [mailto:xam@cs.ucc.ie]
> Sent: woensdag 16 april 2003 15:36
> To: Matthew Wilcox
> Cc: Gavin Hubbard; parisc-linux@lists.parisc-linux.org
> Subject: Re: [parisc-linux] Re: Presicionbook success
>
>
> 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".
>
> 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 ...
Is this something like
http://www6.tomshardware.com/storage/20030130/index.html ? Then you
(electronically) cannot find any ide at all, its hidden behind the scsi
interface. If you see part of it, then best to try to handle it as good as
possible (try 'not at all' for a start). I think the 'will probe later' can
be canceled, triggered by a found scsi interface.
For what its worth, I think the IRQ is hooked to the scsi interface, not to
the processor.
btw, what does an `ioscan` from HP-UX report? I guess it only sees scsi.
CBee
[-- Attachment #2: Type: text/html, Size: 3486 bytes --]
next reply other threads:[~2003-04-16 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 14:00 "Beerse, Corné" [this message]
2003-04-16 14:09 ` [parisc-linux] Re: Presicionbook success 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 15:05 "Beerse, Corné"
2003-04-16 14:13 "Beerse, Corné"
2003-04-16 14:18 ` M. Grabert
[not found] <20030416123824.22413.48893.Mailman@dsl2.external.hp.com>
2003-04-16 13:15 ` Gavin Hubbard
2003-04-16 13:27 ` Matthew Wilcox
2003-04-16 13:36 ` M. Grabert
2003-04-16 13:44 ` Matthew Wilcox
2003-04-16 13:48 ` M. Grabert
2003-04-16 15:02 ` Alan Cox
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=03Apr16.162029cest.119065@ns.hiscom.nl \
--to=c.beerse@torex-hiscom.nl \
--cc=ghub005@xtra.co.nz \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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