From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: understanding of sysfs.
Date: Tue, 23 May 2017 11:23:17 +0200 [thread overview]
Message-ID: <20170523092317.GC22923@kroah.com> (raw)
In-Reply-To: <CAA2oCOnLdwd1P2KSr+4cp3VTwvMLnSdUya__oogst23LzhA6NQ@mail.gmail.com>
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 :)
> > Not only in /sys/class, for that matter why there is no character device
> > entries present in /sys file system.
>
> What do you exactly mean by "character device entries"?
>
>
> like block and net why there is no char folder??
Again, look closer please.
> > please help me to understand for what purpose char devices are kept away
> from /
> > sys file system.
>
> Have you read the driver model chapter in the Linux Device drivers book,
> or the in-kernel sysfs documentation?
Again, please read all of the copious documentation that we have written
already about this topic. If after that, you still have questions, I
will be more than glad to help answer them.
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-23 9:23 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 [this message]
2017-05-29 5:28 ` Madhu K
2017-05-29 5:43 ` 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=20170523092317.GC22923@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.