From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hiscom.nl (unknown [130.78.143.1]) by dsl2.external.hp.com (Postfix) with ESMTP id 9FAED4829 for ; Wed, 16 Apr 2003 08:13:48 -0600 (MDT) Message-Id: <03Apr16.163312cest.119050@ns.hiscom.nl> From: =?iso-8859-1?Q?=22Beerse=2C_Corn=E9=22?= To: "'M. Grabert'" , Matthew Wilcox Cc: Gavin Hubbard , parisc-linux@lists.parisc-linux.org Subject: RE: [parisc-linux] Re: Presicionbook success Date: Wed, 16 Apr 2003 16:13:32 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C30422.5CC0E350" Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C30422.5CC0E350 Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: M. Grabert [mailto:xam@cs.ucc.ie] > > On Wed, 16 Apr 2003, Matthew Wilcox wrote: > > > Date: Wed, 16 Apr 2003 14:44:33 +0100 > > > > On Wed, Apr 16, 2003 at 02:36:25PM +0100, M. Grabert wrote: > > [...] > > > > 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. > > Maybe I was a little bit confusing to you: > > 1. Using a kernel with CMD IDE support, it will hang with the message > "will probe IRQs later" ... > 2. it will not hang if you pass a ide=nodma, but then it will show > no devices > 3. It will just boot fine without any CMD IDE support in the kernel > > > > 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. This gives me more and more the impression it is definitly some predecessor of http://www6.tomshardware.com/storage/20030130/index.html I think the ide interface is not perfectly hidden behind the scsi interface, the cpu can still somehow recognize the ide interface. The ide interface cannot do dma and irq since that is hooked to the scsi interface, not to the cpu/memory. Hence, I think the best the ide driver can do is not to try later but to be disabled at all. Btw, what happens if the ide says to try later, is there a total system pause (resulting in a halt)? or does the remainder of the system continue (and is it save to ignore)? CBee ------_=_NextPart_001_01C30422.5CC0E350 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [parisc-linux] Re: Presicionbook success

> -----Original Message-----
> From: M. Grabert [mailto:xam@cs.ucc.ie]
>
> On Wed, 16 Apr 2003, Matthew Wilcox = wrote:
>
> > Date: Wed, 16 Apr 2003 14:44:33 = +0100
> >
> > On Wed, Apr 16, 2003 at 02:36:25PM +0100, = M. Grabert wrote:
>
> [...]
>
> > > 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.
>
> Maybe I was a little bit confusing to = you:
>
> 1. Using a kernel with CMD IDE support, it will = hang with the message
>    "will probe IRQs = later" ...
> 2. it will not hang if you pass a ide=3Dnodma, = but then it will show
>    no devices
> 3. It will just boot fine without any CMD IDE = support in the kernel
>
> > > 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.

This gives me more and more the impression it is = definitly some predecessor of http://www6.tomshardware.com/storage/20030130/index.ht= ml

I think the ide interface is not perfectly hidden = behind the scsi interface, the cpu can still somehow recognize the ide = interface. The ide interface cannot do dma and irq since that is hooked = to the scsi interface, not to the cpu/memory. Hence, I think the best = the ide driver can do is not to try later but to be disabled at all. = Btw, what happens if the ide says to try later, is there a total system = pause (resulting in a halt)? or does the remainder of the system = continue (and is it save to ignore)?


CBee

------_=_NextPart_001_01C30422.5CC0E350--