From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Parallel ATA with libata status with the patches I'm working on
Date: Sat, 05 Nov 2005 08:50:30 +1100 [thread overview]
Message-ID: <1131141030.29195.18.camel@gaston> (raw)
In-Reply-To: <1131111297.26925.24.camel@localhost.localdomain>
On Fri, 2005-11-04 at 13:34 +0000, Alan Cox wrote:
> On Gwe, 2005-11-04 at 17:43 +1100, Benjamin Herrenschmidt wrote:
> > > - HPA
> > > - IRQ mask
> >
> > Why do we need the above at all ? It always looked to me like a gross
> > hack but then, I don't fully understand what the problem was on those
> > old x86 that needed it :)
>
> You can't do anything useful with some systems without disabling the HPA
> because it is used to mask most of the drive at boot to hide from old
> incompatible BIOS.
I know, I was talking about IRQ Mask :)
> IRQ mask is on my todo list and looks quite easy. A small number of
> controllers mishandle the case when the FIFO empties. Instead of
> stalling the drive they dribble random numbers.
OK, but my question why, what is the reason why we need IRQ mask ? Some
old non-PCI controllers can't grok un-related ISA IO cycles during a
FIFO read/write ? I suppose those would be broken on SMP too (though I
suspect then that those don't exist as SMP machines then :)
Ben.
next prev parent reply other threads:[~2005-11-04 21:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 14:54 Parallel ATA with libata status with the patches I'm working on Alan Cox
2005-11-03 14:48 ` Russell King
2005-11-03 15:02 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:28 ` David S. Miller
2005-11-03 15:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 16:27 ` Alan Cox
2005-11-03 15:56 ` Alan Cox
2005-11-03 20:55 ` Krzysztof Halasa
2005-11-03 21:29 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:29 ` Krzysztof Halasa
2005-11-03 22:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:54 ` Alan Cox
2005-11-04 1:30 ` Rogério Brito
2005-11-04 13:38 ` Alan Cox
2005-11-04 13:41 ` Alan Cox
2005-11-04 23:10 ` Russell King
2005-11-04 23:19 ` Benjamin Herrenschmidt
2005-11-03 15:58 ` Alan Cox
2005-11-03 15:30 ` Russell King
2005-11-03 16:23 ` Alan Cox
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 8:43 ` Xavier Bestel
2005-11-03 14:58 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:49 ` Alan Cox
2005-11-03 15:34 ` Bartlomiej Zolnierkiewicz
2005-11-04 0:14 ` Mark Lord
2005-11-04 0:17 ` Mark Lord
2005-11-04 1:18 ` Alan Cox
2005-11-04 3:49 ` Jeff Garzik
2005-11-05 22:31 ` Mark Lord
2005-11-04 6:43 ` Benjamin Herrenschmidt
2005-11-04 7:00 ` Jeff Garzik
2005-11-04 13:34 ` Alan Cox
2005-11-04 21:50 ` Benjamin Herrenschmidt [this message]
2005-11-06 20:41 ` 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=1131141030.29195.18.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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