From: Ben Hutchings <ben@decadent.org.uk>
To: Alan Cox <alan@linux.intel.com>
Cc: David Miller <davem@davemloft.net>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: piix vs ata_piix device ID tables
Date: Mon, 04 Oct 2010 21:09:10 +0100 [thread overview]
Message-ID: <1286222950.3916.327.camel@localhost> (raw)
In-Reply-To: <20101004102145.2f34cc62@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
On Mon, 2010-10-04 at 10:21 +0100, Alan Cox wrote:
> On Mon, 04 Oct 2010 04:50:52 +0100
> Ben Hutchings <ben@decadent.org.uk> wrote:
[...]
> > PCI_DEVICE_ID_INTEL_82801DB_1 == 0x24c1 (ICH4 device 31 function 1)
> >
> > piix seems to treat this the same as most other ICH PATA interfaces,
> > which are handled by ata_piix.
> >
> > Does anyone know why these aren't handled by the libata-based drivers?
>
> I don't know about 0x24C1 however it isn't listed in the Intel ICH
> programming manual so given we've also had no reports about it I
> suspect it's an error in the PIIX driver ?
Correction, this is a function of the ICH4-L not the ordinary ICH4. It
is documented in
<http://www.intel.com/assets/pdf/specupdate/290745.pdf>.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2010-10-04 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 3:50 piix vs ata_piix device ID tables Ben Hutchings
2010-10-04 9:21 ` Alan Cox
2010-10-04 20:09 ` Ben Hutchings [this message]
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=1286222950.3916.327.camel@localhost \
--to=ben@decadent.org.uk \
--cc=alan@linux.intel.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).