All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: akpm@osdl.org, alan@lxorguk.ukuu.org.uk, jgarzik@pobox.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata: PIIX3 support
Date: Sat, 13 Jan 2007 19:27:20 -0600	[thread overview]
Message-ID: <45A986F8.3000300@shaw.ca> (raw)
In-Reply-To: <fa.wgyMaLVtkeBqyNAZjGg9fEi3shs@ifi.uio.no>

Mikael Pettersson wrote:
> On Wed, 10 Jan 2007 17:13:38 +0000, Alan <alan@lxorguk.ukuu.org.uk> wrote:
>> This I believe completes the PIIX range of support for libata
>>
>> This adds the table entries needed for the PIIX3, both a new PCI
>> identifier and a new mode list. It also fixes an erroneous access to PCI
>> configuration 0x48 on non UDMA capable chips.
> 
> Works fine here on a 430HX box (ASUS T2P4).
> I'm appending kernel messages for boots with the IDE driver and
> with the updated libata driver, in case you want to compare them.
> 
> I did notice that ata_piix identified the disk as
> "QUANTUM FIREBALL A5U." when IDE correctly identified it as
> "QUANTUM FIREBALL CR8.4A".

I believe libata truncates the ATA device ID string to fit the max 
allowable for SCSI. The A5U. part is presumably the drive's firmware 
revision.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-01-14  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.wgyMaLVtkeBqyNAZjGg9fEi3shs@ifi.uio.no>
2007-01-14  1:27 ` Robert Hancock [this message]
2007-01-12  1:08 [PATCH] libata: PIIX3 support Mikael Pettersson
2007-01-12  1:26 ` Alan
  -- strict thread matches above, loose matches on Subject: below --
2007-01-10 17:13 Alan
2007-01-10 17:27 ` Jeff Garzik
2007-01-20  0:14 ` Jeff Garzik

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=45A986F8.3000300@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.