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:	Thu, 2 Aug 2007 10:32:21 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	David Engraf <david.engraf@...com.eu>
cc:	linux-pci@...ey.karlin.mff.cuni.cz, <gregkh@...e.de>,
	<linux-kernel@...r.kernel.org>,
	<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 Thu, 2 Aug 2007, David Engraf wrote:

> This would be solution too, but what if someone uses the uhci controller
> and don't want the
> ehci. So a single Kconfig flag wouldn't be enough, we have to add 3
> flags for uchi, ohci and
> ehci. I think this maybe a little bit difficult when configuring the kernel.
> The best solution would be when we could use the CONFIG_USB_xxxx_HCD
> flag, but it
> seems that some hardware has problems when we disable the handoff and
> let the BIOS
> control the usb controller. Do you know any of this hardware?

The email messages are hidden in the depths of the linux-usb-devel 
archives.  Maybe you can find them by checking the Git history for 
drivers/usb/host/pci-quirks.c, finding the dates for patches that 
affected the handoff code, and then searching through the archives near 
those dates.

IIRC the problems arose on some MIPS machines.  And I don't think the 
problem involved letting the firmware manage the USB controller; I 
think the problem came when the controller driver tried to do the 
handoff later on.

Alan Stern

-
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