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:	Mon, 3 Nov 2008 23:51:46 -0700
From:	David Brownell <david-b@...bell.net>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Steven Noonan <steven@...inklabs.net>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Greg KH <greg@...ah.com>
Subject: Re: [PATCH] EHCI pci-quirks.c: wait for BIOS handoff too long

On Monday 03 November 2008, Jeff Garzik wrote:
> That tells us nothing about the original reason for choosing the 5000 
> value, and what if any impact lowering the value has on those who 
> thought 5000 was needed.

You mean, the source code should have a comment about that?

The *original* BIOS-broken timeout was some fraction of a second
(I'm thinking 250 msec, maybe not), but I got some reports about
BIOS versions that were too sluggish to work with that.  ISTR
that half a second wasn't quite reliable, so 1+ seconds seemed
to be called for.

So rather than incremental increases, it went from 250 msec up
to 5000 msec, and this is the first complaint we've had about
that in *many* years.

- Dave
--
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