[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E25892C.8070102@redhat.com>
Date: Tue, 19 Jul 2011 09:39:56 -0400
From: Prarit Bhargava <prarit@...hat.com>
To: linux-kernel@...r.kernel.org
CC: Andi Kleen <andi@...stfloor.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 01/34] System Firmware Interface
On 07/19/2011 09:21 AM, Andi Kleen wrote:
> On Tue, Jul 19, 2011 at 10:05:44AM +0100, Alan Cox wrote:
>
>>> Could you expand somewhat WHY you want this. What is wrong with the
>>> current code?
>>>
>> See the previous discussions
>>
> Ok I will put that now as description into all my code submissions @)
>
> Seriously, that REALLY belongs into a patch description.
>
I can certainly do that on the next version. Sorry about that Andi.
>
>>
>>> As for user space access on x86 "dmidecode"/libdmi works for nearly everyone,
>>> doesn't it?
>>>
>> "on x86" (and on PC only generally)
>>
>> There are three core problems
>>
>> 1. DMI in this sense is basically an x86 PC class device hack
>> 2. It is obsoleted and at some point it'll vanish even on PC
>>
> Huh? What obsoleted it?
>
>
The DMI specification has not been updated since January of 2003. It
has been replaced by SMBIOS.
>> 3. Every other platform without DMI would benefit from the
>> interface being generic
>>
> Can you expand on that? The information will be always system
> specific anyways. Do you really think there's that much commonality?
>
>
There seems to be some commonalities. We have other arches checking for
model and vendor info.
P.
--
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