linux-kernel - Re: [linux-usb-devel] [PATCH] USB BIOS early handoff only when the we the driver is configured

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, 1 Aug 2007 13:23:47 -0700
From:	Greg KH <gregkh@...e.de>
To:	David Engraf <david.engraf@...com.eu>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
	linux-usb-devel@...ts.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] USB BIOS early handoff only when the
	we the driver is configured

On Wed, Aug 01, 2007 at 09:21:12AM +0200, David Engraf wrote:
> At the moment I have a Jetway/VIA Mainboard which seems to have a
> problem with the handoff.
> Evenwhen I wait about 20 seconds the EHCI_USBLEGSUP_BIOS flag is not
> cleared. I think this is a BIOS
> bug and I will have to talk to Jetway/VIA.

This sounds like a BIOS bug.

> On the other hand, I don't need the EHCI controller in my kernel, so I
> think the kernel shouldn't take the
> handover for the EHCI controller like other OS which do not have an usb
> driver and so don't know that
> there is a EHCI_USBLEGSUP_BIOS flag which should be cleared.

We need to do this early to handle a wide range of machines that do very
nasty things if we do not grab the device as early as possible.  Even if
we do not ever get around to loading that usb driver.

Yeah, hardware sucks at times :(

thanks,

greg k-h
-
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/