linux-kernel - Re: [PATCH 1/2] usb: Prefer firmware values when determining whether a port is removable

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] [day] [month] [year] [list]

Message-ID: <CAPeXnHtWsgeO9eMAuy9M0W_hEhO17_8LyzNteBO482q60n3EiA@mail.gmail.com>
Date:	Thu, 9 Apr 2015 10:19:04 -0700
From:	Matthew Garrett <matthew.garrett@...eos.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Matthew Garrett <mjg59@...eos.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] usb: Prefer firmware values when determining whether
 a port is removable

On Thu, Apr 9, 2015 at 2:31 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> Anyway, is this all a Windows 8 requirement?  If so, I'll feel
> comfortable making these changes, otherwise we are at the mercy of the
> bios people to randomly get things right, and we all know how often that
> works...

It's covered by
System.Fundamentals.SystemUSB.XHCIControllersMustHaveEmbeddedInfo - I
guess there's an argument for having the order depend on the
controller, but I suspect that anything with _PLD and _UPC objects
will be fine. The alternative means we're just relying on a different
set of firmware information (ie, did the hardware vendor bother
setting the hub flags), so...


-- 
Matthew Garrett | matthew.garrett@...eos.com
--
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/