From: Doug Thompson <norsk5@yahoo.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Thu, 17 Nov 2005 09:20:53 -0800 (PST) [thread overview]
Message-ID: <20051117172053.87207.qmail@web50112.mail.yahoo.com> (raw)
In-Reply-To: <20051117070516.GB20760@kroah.com>
--- Greg KH <greg@kroah.com> wrote:
> On Tue, Nov 15, 2005 at 04:26:38PM -0800, Doug
> Thompson wrote:
> > My question is: Should I remove entirely my old
> > /proc/sys/mc sysctl tree? Or still maintain the
> > aliases there (which seems weird)?
>
> That would be wierd, just drop the sysctl stuff.
>
> > If I do that, then /etc/sysctl.conf will no longer
> > allow for setting things up there.
>
> True.
>
> > Is there going to be a similiar functionality as
> > /etc/sysctl.conf for those items we place in
> sysfs, in
> > the future?
>
> If you want to write one, sure :)
Good idea. Seems I have hit the edge of current
features. That's is good for now there is another food
item for a TODO list.
>
> But you can just probably use a udev rule to
> initialize your things
> properly, that's what all of the distros are now
> using.
Ok. That's another area for me to research. edac does
not have any /dev/ entries, just the files and
controls previous mentioned.
So, from your comment then, udev has some mechanism to
set controls in sysfs?
>
> > PS. These questions on sysfs seem a perfect food
> > stream for your 'HOWTO do kernel development'.
> Trying
> > to do new entries in sysfs has been a painstaking
> > adventure. After googling the web for info, it
> > definitely has been a bit thin on information on
> sysfs
> > at the level I am seeking.
>
> sysfs and the driver model are woefully
> underdocumented. Right now, I'd
> recommend the Linux Device Drivers, third edition,
> free online if you
> don't want to buy it, for anyone doing any driver
> core stuff. It has a
> whole chapter that is the most up-to-date and the
> best description I've
> seen so far.
Yes, I have LDD 3rd and it is good. I have also have
Robert Love's book and it has some good stuff on the
device model and sysfs, but I assume since the whole
feature is fairly new its documentation and
understanding are still in the nursery.
I also came across Patrick Mochel's paper given at
Linux Symposium in June 2005. That helped.
>From the src on the machinecheck currently in sysfs, I
see it implements the 'subsystem' feature of sysfs.
>From that code I see the pattern I can use.
>
> But even then, it is out of date, due to api
> changes, sorry.
>
> thanks,
>
> greg k-h
>
at least there is some docs AND some people to ask
questions to.
thanks
doug t
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you
want and they will surprise you with their ingenuity."
Gen George Patton
next prev parent reply other threads:[~2005-11-17 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:14 Doug Thompson
2005-11-14 22:31 ` Greg KH
2005-11-15 0:30 ` Dave Jones
2005-11-15 17:24 ` Greg KH
2005-11-15 0:47 ` Doug Thompson
2005-11-15 1:12 ` Doug Thompson
2005-11-15 17:25 ` Greg KH
2005-11-16 0:26 ` Doug Thompson
2005-11-17 7:05 ` Greg KH
2005-11-17 17:20 ` Doug Thompson [this message]
2005-11-17 17:18 ` Greg KH
2005-11-17 18:32 ` Kay Sievers
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=20051117172053.87207.qmail@web50112.mail.yahoo.com \
--to=norsk5@yahoo.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
all inboxes | Powered by JetHome®