From: Gregory Anders <greg@gpanders.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Device file not appearing
Date: Wed, 17 Mar 2021 10:13:22 -0600 [thread overview]
Message-ID: <YFIqovtMkFG6/IVB@gpanders.com> (raw)
In-Reply-To: <YFInTGEanJC4ibgv@kroah.com>
On Wed, 17 Mar 2021 16:59:08 +0100, Greg KH <greg@kroah.com> wrote:
>Is your char device listed in /sys/dev/char/ ?
>
>If not, then you have something wrong with your call to device_create().
>
>If so, then you need to look at whatever tool is creating your device
>nodes in /dev. Usually the kernel handles this with devtmpfs, but I do
>not know what your system uses for this.
Indeed it is. I am working with a fairly minimal system on a Xilinx
Microblaze soft-core CPU. I have udev installed, but I'm not sure about
devtmpfs. I'll start digging in that direction and see what I find.
>Also, why a full major? Why not just use the misc_dev api instead that
>does all of the above "housekeeping" for you automagically?
Simply because I wasn't aware of the misc_dev API :) But that does look
like a nice abstraction that will save me some boilerplate, so thanks
for pointing that out.
Thanks,
Greg
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-03-17 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 15:52 Device file not appearing Gregory Anders
2021-03-17 15:59 ` Greg KH
2021-03-17 16:13 ` Gregory Anders [this message]
2021-03-17 16:16 ` Greg KH
2021-03-17 16:56 ` Gregory Anders
2021-03-17 17:05 ` Gregory Anders
2021-03-17 17:15 ` Greg KH
2021-03-17 18:26 ` Gregory Anders
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 20:25 Gregory Anders
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=YFIqovtMkFG6/IVB@gpanders.com \
--to=greg@gpanders.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@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.