From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org, nsujir@broadcom.com
Subject: Re: [PATCH v2 -next 4/4] tg3: Add binary sysfs file to export bulk sensor data
Date: Tue, 26 Jun 2012 22:04:59 -0700 (PDT) [thread overview]
Message-ID: <20120626.220459.548918770401348569.davem@davemloft.net> (raw)
In-Reply-To: <1340773249.4344.74.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Tue, 26 Jun 2012 22:00:49 -0700
> On Tue, 2012-06-26 at 21:02 -0700, David Miller wrote:
>> Ben stated merely that a binary attribute existed for sysfs files. He
>> did not, however, say that this is the path down which you should
>> implement your feature.
>
> He said that if the data was difficult to parse in the driver, then a
> binary sysfs or private ioctl (which we would stay away) would be
> appropriate. There are hundreds of bytes of this data, most of which is
> not useful to the user but needed for Lights out management. It will
> greatly bloat the tg3 driver to add code to parse all that data and
> export each one separately.
I don't want us to get into the habit of just going "oh it's LOM
stuff, binary blob." And that's the precedence you're setting here.
It also sets up a situation where functionality could end up only
being available in proprietary binary only tools.
It's not like this is some standardized format like a DMI table or
similar, is it?
next prev parent reply other threads:[~2012-06-27 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 0:53 [PATCH v2 -next 1/4] tg3: Add common function tg3_ape_event_lock() Michael Chan
2012-06-27 0:53 ` [PATCH v2 -next 2/4] tg3: Add APE scratchpad read and write functions Michael Chan
2012-06-27 0:53 ` [PATCH v2 -next 3/4] tg3: Add hwmon support Michael Chan
2012-06-27 0:53 ` [PATCH v2 -next 4/4] tg3: Add binary sysfs file to export bulk sensor data Michael Chan
2012-06-27 4:02 ` David Miller
2012-06-27 5:00 ` Michael Chan
2012-06-27 5:04 ` David Miller [this message]
2012-06-27 5:12 ` Michael Chan
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=20120626.220459.548918770401348569.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=nsujir@broadcom.com \
/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;
as well as URLs for NNTP newsgroup(s).