From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: 2.6 - sysfs sensor nameing inconsistency
Date: Sun, 2 Nov 2003 21:50:48 +0300 [thread overview]
Message-ID: <200311022150.48638.arvidjaar@mail.ru> (raw)
In-Reply-To: <20030922222910.GA306@kroah.com>
On Tuesday 23 September 2003 02:29, Greg KH wrote:
>
> Thanks, I've applied this and will send it off to Linus in a bit.
>
thank you.
> > it just arbitrarily (re-)names them. "min" is not hysteresis; name is
> > badly chosen.
>
> Do you have a proposed change to the current
> Documentation/i2c/sysfs-interface document? If you can think of better
> names that make more sense, I'd be glad to change things to make it
> easier.
>
it is probably too late now to change sysfs names when some programs already
use it. I'll check sysfs-interface, thank you for pointer.
> > > > 4. I do not have the slightest idea how ISA adapters look like in
> > > > sysfs and where they are located. Anyone can give me example?
> > >
> > > They show up on the legacy bus:
> > >
> > > $ tree /sys/class/i2c-adapter/i2c-1/
> > > /sys/class/i2c-adapter/i2c-1/
> > >
> > > |-- device -> ../../../devices/legacy/i2c-1
> >
> > This does not help much. Libsensors expects as adapter identification
> > either "i2c-N" or "isa". If I set it to "isa" I do not have any way to
> > determine sysfs path except by rescanning /sys/class/i2c-adapter every
> > time. Having /sys/class/i2-adapter/isa/... would be better, apparently it
> > is assumed that only one such adapter can exist.
>
> No, we internally do not differentiate between isa and non-isa adapters,
> so why should we force that on the user? They work the same as far as
> users notice, and now we are consistant in our naming.
>
Well, I just tried to match what users get out of libsensors on 2.4. The
reason was compatibility with /etc/sensors.conf where "isa" can possibly be
used as part of chip name. But I'd like that someone from sensors developers
comment on this.
thank you for your comments.
-andrey
next prev parent reply other threads:[~2003-11-02 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 18:14 2.6 - sysfs sensor nameing inconsistency Andrey Borzenkov
2003-07-15 20:18 ` Greg KH
2003-07-26 18:00 ` Andrey Borzenkov
2003-08-15 20:51 ` Greg KH
2003-08-16 15:38 ` Andrey Borzenkov
2003-08-16 16:50 ` Greg KH
2003-08-18 16:49 ` Andrey Borzenkov
2003-08-18 21:31 ` Greg KH
2003-08-19 19:19 ` Andrey Borzenkov
2003-08-19 19:45 ` Greg KH
2003-08-31 16:25 ` Andrey Borzenkov
2003-09-22 22:29 ` Greg KH
2003-11-02 18:50 ` Andrey Borzenkov [this message]
2003-07-27 4:42 Margit Schubert-While
2003-07-27 6:23 Andrey Borzenkov
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=200311022150.48638.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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).