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]
Message-ID: <456699CA.9060904@gmail.com>
Date:	Fri, 24 Nov 2006 16:05:46 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Conke Hu <conke.hu@....com>
CC:	linux-kernel@...r.kernel.org, alan@...rguk.ukuu.org.uk,
	Andrew Morton <akpm@...l.org>, Jeff Garzik <jeff@...zik.org>,
	arjan@...radead.org
Subject: Re: [PATCH] Add IDE mode support for SB600 SATA

Tejun Heo wrote:
> Conke Hu wrote:
>> ATI SB600 SATA controller supports 4 modes: Legacy IDE, Native IDE, 
>> AHCI and RAID. Legacy/Native IDE mode is designed for compatibility 
>> with some old OS without AHCI driver but looses SATAII/AHCI features 
>> such as NCQ. This patch will make SB600 SATA run in AHCI mode even if 
>> it was set as IDE mode by system BIOS.
[--snip--]
> Other than that, Acked-by: Tejun Heo <htejun@...il.com>

At the second thought, I think this should be done in 
ahci_init_controller().

* Unlike Jmicron's case, this doesn't affect PCI bus scan.  Actually, it 
does change class code but that's not as disruptive as Jmicron's case 
and as long as ahci ignores class code, it doesn't really matter. 
Driver can be chosen by changing loading order - this is both plus and 
minus.

* As Arjan pointed out, that unlock-modify-lock sequence should be done 
on resume too.  ahci_init_controller() is the right place for such 
stuff.  This chip is going into notebooks, right?

-- 
tejun
-
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