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: <20141006163147.GA22482@srcf.ucam.org>
Date:	Mon, 6 Oct 2014 17:31:47 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Suravee Suthikulanit <suravee.suthikulpanit@....com>,
	catalin.marinas@....com, will.deacon@....com,
	linux-arm-kernel@...ts.infradead.org, linux-acpi@...r.kernel.org,
	mark.rutland@....com, graeme.gregory@...aro.org,
	marc.zyngier@....com, rjw@...ysocki.net,
	linux-kernel@...r.kernel.org, astone@...hat.com,
	grant.likely@...aro.org, hanjun.guo@...aro.org,
	Sudeep.Holla@....com, olof@...om.net, jason@...edaemon.net,
	"Duran, Leo" <leo.duran@....com>, Jon Masters <jcm@...hat.com>
Subject: Re: [PATCH 1/4] ata: ahci_platform: Add ACPI support for AMD Seattle
 SATA controller

On Thu, Oct 02, 2014 at 10:39:18AM +0200, Arnd Bergmann wrote:

> I think part of the problem is that there is no specification for what
> an AHCI device should look like when it's not connected to a PCI
> bus, the AHCI document published by Intel just states:

One thing that has come out of further discussion on this - ACPI defines 
a _CLS object, which allows ACPI devices to declare compatibility with a 
PCI class device. We don't have support for it at the moment, but it 
would be easy enough to add this to the kernel and then just expose the 
AHCI PCI class via _CLS. That would avoid us having problems with people 
doing similar things with USB hosts.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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