* no need to add new DID's to AHCI driver?
@ 2007-08-22 18:19 Gaston, Jason D
2007-08-22 19:19 ` Jeff Garzik
0 siblings, 1 reply; 3+ messages in thread
From: Gaston, Jason D @ 2007-08-22 18:19 UTC (permalink / raw)
To: IDE/ATA development list, Jeff Garzik, Tejun Heo
Hello,
Now that the AHCI driver has support for all controllers with the 0x0106
(AHCI) class code, I am not planning on adding controller DeviceID's for
AHCI controllers. I want to verify that this is the correct course of
action.
Note: I still will have to add the Intel SW "RAID" controller
DeviceID's as they have a 0x0104 (RAID) class code.
Thanks,
Jason
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: no need to add new DID's to AHCI driver?
2007-08-22 18:19 no need to add new DID's to AHCI driver? Gaston, Jason D
@ 2007-08-22 19:19 ` Jeff Garzik
2007-08-23 0:53 ` Tejun Heo
0 siblings, 1 reply; 3+ messages in thread
From: Jeff Garzik @ 2007-08-22 19:19 UTC (permalink / raw)
To: Gaston, Jason D; +Cc: IDE/ATA development list, Tejun Heo
Gaston, Jason D wrote:
> Hello,
>
> Now that the AHCI driver has support for all controllers with the 0x0106
> (AHCI) class code, I am not planning on adding controller DeviceID's for
> AHCI controllers. I want to verify that this is the correct course of
> action.
>
> Note: I still will have to add the Intel SW "RAID" controller
> DeviceID's as they have a 0x0104 (RAID) class code.
Yep, that's fine -- and the encouraged direction.
The ideal situation for users is when new hardware is "automagically"
supported, without needing any driver PCI ID modifications at all.
Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: no need to add new DID's to AHCI driver?
2007-08-22 19:19 ` Jeff Garzik
@ 2007-08-23 0:53 ` Tejun Heo
0 siblings, 0 replies; 3+ messages in thread
From: Tejun Heo @ 2007-08-23 0:53 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Gaston, Jason D, IDE/ATA development list
Jeff Garzik wrote:
> Gaston, Jason D wrote:
>> Hello,
>>
>> Now that the AHCI driver has support for all controllers with the 0x0106
>> (AHCI) class code, I am not planning on adding controller DeviceID's for
>> AHCI controllers. I want to verify that this is the correct course of
>> action.
>>
>> Note: I still will have to add the Intel SW "RAID" controller
>> DeviceID's as they have a 0x0104 (RAID) class code.
>
> Yep, that's fine -- and the encouraged direction.
>
> The ideal situation for users is when new hardware is "automagically"
> supported, without needing any driver PCI ID modifications at all.
One remaining hurdle tho is the distinction between board_ahci and
board_ahci_pi (whether to honor PORTS_IMPL or not). AHCI class matching
uses board_ahci so PI will be ignored by default. There's a pending
patch which removes this distinction, so this won't be a problem after
the patch is merged.
--
tejun
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-08-23 0:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-22 18:19 no need to add new DID's to AHCI driver? Gaston, Jason D
2007-08-22 19:19 ` Jeff Garzik
2007-08-23 0:53 ` Tejun Heo
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).