From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: use of dev->dev_t
Date: Tue, 17 Mar 2015 22:13:43 +0100 [thread overview]
Message-ID: <20150317211343.GA8441@kroah.com> (raw)
In-Reply-To: <550891FA.1020007@postgrad.manchester.ac.uk>
On Tue, Mar 17, 2015 at 08:43:38PM +0000, Malte Vesper wrote:
> Hi,
> I am trying to write a driver that uses the MINOR(dev_t) to identify
> cards. Since it is a PCI driver and I get pcidev->dev.dev_t anyway. I
> thought about not bothering to store the minor number of the device.
> However if I look at pcidev->dev.dev_t in the remove function (the
> driver frameworks remove), I always get pcidev->dev.dev_t == 0.
That dev_t is not for your use, sorry, it is for the driver core to use,
if it needs/wants to for a class device. A PCI driver should never need
to be a char device, but if it does, you have to make your own calls to
the character device core.
What type of PCI device is this? Why do you want to have a character
device node for it?
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-17 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:43 use of dev->dev_t Malte Vesper
2015-03-17 21:13 ` Greg KH [this message]
2015-03-17 21:46 ` Malte Vesper
2015-03-17 21:53 ` Greg KH
2015-03-17 22:25 ` Malte Vesper
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=20150317211343.GA8441@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).