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]

Message-ID: <Pine.LNX.4.44L0.0708031101530.2597-100000@iolanthe.rowland.org>
Date:	Fri, 3 Aug 2007 11:03:23 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	David Engraf <david.engraf@...com.eu>
cc:	Greg KH <gregkh@...e.de>, <linux-pci@...ey.karlin.mff.cuni.cz>,
	<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 Fri, 3 Aug 2007, David Engraf wrote:

> So we have hardware which has problems when we are not doing the
> handoff, and hardware which has
> problems when we are  doing the handoff...

What hardware has problems when we do the handoff?  Your system and 
mine experience a delay, but it doesn't break anything.

> What is the best way to solve the problem? Maybe a kernel parameter, a
> config flag or an automatic
> hardware dependent check of the system?
> In fact it is hard to find a solution which works for both as long as
> the hardware has this bugs.

If we really need it, I say we should use a Kconfig flag.

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/