lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 01 Nov 2006 00:35:09 -0500
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Linus Torvalds <torvalds@...l.org>
CC:	Conke Hu <conke.hu@....com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: AHCI should try to claim all AHCI controllers

Linus Torvalds wrote:
> 
> On Wed, 1 Nov 2006, Jeff Garzik wrote:
>> For the benefit of others, some background:  we should not be -removing- any
>> PCI IDs due to this, because quite often the PCI class code will be RAID or
>> something else, yet still be drive-able with this ahci driver.
> 
> Well, it might obviously be worthwhile removing the PCI ID's that actually 
> do say that they are AHCI. Maybe that's not all of them, but I wouldn't be 
> surprised if it's actually the majority of them..

The same PCI ID maps to either RAID or AHCI.  The PCI ID only changes 
when it's no longer in AHCI mode (IDE/legacy mode).

To confuse matters even further, sometimes you can use AHCI even though 
it claims it is in IDE mode.  And the reverse is -often- true:  you can 
usually use legacy IDE mode even if the PCI ID and class code claim AHCI 
mode.

Who knows what beasts lurk behind the same PCI ID...


> (We had the same issue with "PCI IDE controller". Some PCI IDE controllers 
> are clearly exactly that from a programming interface standpoint, but 
> because they support RAID in hardware, they claim to be RAID controllers, 
> since that is more "glamorous". Gaah ;^).

Heck these days 'RAID' is a marketing requirement for your hardware, 
regardless of its capabilities...

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ