From: Prarit Bhargava <prarit@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, dzickus@redhat.com
Subject: Re: [PATCH]: SMBIOS: Add initial code and export version via sysfs
Date: Thu, 17 Mar 2011 16:08:47 -0400 [thread overview]
Message-ID: <4D826A4F.9070608@redhat.com> (raw)
In-Reply-To: <4D826718.3030001@redhat.com>
Sorry Greg, I missed replying to one of your questions.
>>
>>
>>> +}
>>> +
>>> +/* add additional sysfs files here */
>>> +static struct device_attribute smbios_attrs[] = {
>>> + __ATTR_RO(version),
>>> +};
>>>
>>>
>> So a whole new class just for a single version file in sysfs?
>>
>>
Right now it is only the version file. Eventually I was thinking that
this would grow to include sysfs entries for the BIOS info (date,
vendor, etc.) and Product and Chassis info, not to mention all the
various SMBIOS structs. We have at least one driver that goes through a
lot of trouble to get this info, and IIRC, the PCI code now outputs
type41 and type9 fields for the network device naming stuff.
I thought that meant it needed a new class but, as you pointed out, that
isn't the case. I'll ping kernel-mentors and see if anyone there might
point me to the right class for this data.
>> I'm confused, what exactly are you trying to show here that you can't
>> show in the existing device/class structure?
>>
>>
I want to show the version of the SMBIOS on the system. But it doesn't
seem to make sense to me to expose it in the DMI sysfs code. The SMBIOS
provides the DMI code, not the other way around. We've become used to
the DMI code, and we're adding SMBIOS decoding to it but the other parts
of the kernel are doing their own decoding of the SMBIOS to get
additional info. To me, at least, this means we should have a central
place for it.
Thanks again,
P.
next prev parent reply other threads:[~2011-03-17 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:57 [PATCH]: SMBIOS: Add initial code and export version via sysfs Prarit Bhargava
2011-03-17 19:09 ` Alan Cox
2011-03-17 19:12 ` Prarit Bhargava
2011-03-17 19:22 ` Greg KH
2011-03-17 19:30 ` Greg KH
2011-03-17 19:55 ` Prarit Bhargava
2011-03-17 20:07 ` Greg KH
2011-03-21 15:45 ` Prarit Bhargava
2011-03-21 16:06 ` Alan Cox
2011-03-27 22:29 ` Prarit Bhargava
2011-03-17 20:08 ` Prarit Bhargava [this message]
2011-03-17 20:15 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D826A4F.9070608@redhat.com \
--to=prarit@redhat.com \
--cc=dzickus@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox