From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: understanding of sysfs.
Date: Mon, 29 May 2017 07:43:09 +0200 [thread overview]
Message-ID: <20170529054309.GB3701@kroah.com> (raw)
In-Reply-To: <CAA2oCO=dF49rH4PbAp-3w-MxSn43KdsStFhETvag+MxTW=fZ4w@mail.gmail.com>
On Mon, May 29, 2017 at 10:58:09AM +0530, Madhu K wrote:
>
>
> On Tue, May 23, 2017 at 2:53 PM, Greg KH <greg@kroah.com> wrote:
>
> On Tue, May 23, 2017 at 12:58:07PM +0530, Madhu K wrote:
> > Hi Greg,
> >
> > Thanks for your response.
> >
> >
> > On Tue, May 23, 2017 at 12:04 PM, Greg KH <greg@kroah.com> wrote:
> >
> >? ? ?On Tue, May 23, 2017 at 11:58:31AM +0530, Madhu K wrote:
> >? ? ?> Hi All,
> >? ? ?>
> >? ? ?> why there is no character device entry present in /sys/class? where
> as
> >? ? ?block
> >? ? ?> and net device entries are present.
> >
> >? ? ?I see character devices there, but not the device nodes.? I don't see
> >? ? ?block device nodes there either.
> >
> >
> > If I am wrong please correct me, there is a folder called block in /sys/
> class.
> > is block not containing block device nodes??
>
> Nope, look closer :)
>
>
> I checked the block folder, the entries which are present in /sys/class/block
> are softlink to /sys/devices nodes.
What do you exactly mean by "nodes"? /sys/class/block/ points to the
block device "class devices" in the kernel device hierarchy, just like
the other /sys/class/* entries point to other class devices.
> what i understand from this is, all block net and char node entries
> are present in /sys/devices. Am i correct?
Again, what do you mean by a "node"? Did you read the documentation
about sysfs and the driver model?
thanks,
greg k-h
prev parent reply other threads:[~2017-05-29 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 6:28 understanding of sysfs Madhu K
2017-05-23 6:34 ` Greg KH
2017-05-23 7:28 ` Madhu K
2017-05-23 9:23 ` Greg KH
2017-05-29 5:28 ` Madhu K
2017-05-29 5:43 ` Greg KH [this message]
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=20170529054309.GB3701@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).