[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200803041018.29035.jbarnes@virtuousgeek.org>
Date: Tue, 4 Mar 2008 10:18:28 -0800
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Greg KH <gregkh@...e.de>
Cc: Matthew Wilcox <matthew@....cx>, Alex Chiang <achiang@...com>,
Gary Hade <garyhade@...ibm.com>,
kaneshige.kenji@...fujitsu.com, warthog19@...lescrag.net,
kristen.c.accardi@...el.com, rick.jones2@...com,
linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH 4/4] ACPI PCI slot detection driver
On Monday, March 03, 2008 9:49 pm Greg KH wrote:
> On Sat, Mar 01, 2008 at 07:43:07AM -0700, Matthew Wilcox wrote:
> > On Fri, Feb 29, 2008 at 09:25:42PM -0800, Greg KH wrote:
> > > What is the guarantee that the names of these slots are correct and do
> > > not happen to be the same as the hotpluggable ones?
> >
> > That would be a bug -- and yes, bugs happen, and we have to deal with
> > them.
>
> My main concern is that BIOS vendors will not fix these bugs, as no
> other OS cares/does this kind of thing today. The ammount of bad
> information out there might be quite large, and I think this was
> confirmed by some initial testing of IBM systems, right?
Yeah, but there's a flip side to this too: if no one uses the data, no one
will complain when it's wrong. If Linux starts making it easy to see this
stuff, there's a chance system vendors will start taking an extra 5 min.
before shipment to make sure that the BIOS info is up to date...
OTOH, I'm not sure which is worse, bad data or no data.
Jesse
--
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