Linux PARISC architecture development
 help / color / mirror / Atom feed
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:13:32 +0200	[thread overview]
Message-ID: <03Apr16.163312cest.119050@ns.hiscom.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]

> -----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

[-- Attachment #2: Type: text/html, Size: 3449 bytes --]

             reply	other threads:[~2003-04-16 14:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 14:13 "Beerse, Corné" [this message]
2003-04-16 14:18 ` [parisc-linux] Re: Presicionbook success M. Grabert
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16 15:05 "Beerse, Corné"
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
     [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.163312cest.119050@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