[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <45640FF4.76E4.0078.0@novell.com>
Date: Wed, 22 Nov 2006 08:53:08 +0100
From: "Jan Beulich" <jbeulich@...ell.com>
To: "Chris Wright" <chrisw@...s-sol.org>
Cc: "Zwane Mwaikambo" <zwane@....linux.org.uk>,
"Michael Buesch" <mb@...sch.de>,
"Metathronius Galabant" <m.galabant@...glemail.com>,
<stable@...nel.org>, "Michael Krufky" <mkrufky@...uxtv.org>,
"Justin Forbes" <jmforbes@...uxtx.org>, <alan@...rguk.ukuu.org.uk>,
"Theodore Ts'o" <tytso@....edu>,
"Chris Wedgwood" <reviews@...cw.f00f.org>, <akpm@...l.org>,
<torvalds@...l.org>, "Chuck Wolber" <chuckw@...ntumlinux.com>,
"Dave Jones" <davej@...hat.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
<linux-kernel@...r.kernel.org>,
"Randy Dunlap" <rdunlap@...otime.net>
Subject: Re: [stable] [PATCH 46/61] fix Intel RNG detection
>It does appear to work w/out the patch. I've asked for a small bit
>of diagnostics (below), perhaps you've got something you'd rather see?
>I expect this to be a 24C0 LPC Bridge.
Yes, that's what I'd have asked for. If it works, I expect the device
code to be different, or both manufacturer and device code to be
invalid. Depending on the outcome, perhaps we'll need an override
option so that this test can be partially (i.e. just the device code
part) or entirely (all the FWH detection) skipped.
The base problem is the vague documentation of the whole
detection mechanism - a lot of this I had to read between the lines.
Jan
-
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