From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
To: Vitaliy Ivanov <vitalivanov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Driver question: multiple instances of same char device
Date: Tue, 10 Jul 2007 09:31:38 -0400 [thread overview]
Message-ID: <1184074303.31808.33.camel@microwave.infinitevideocorporation.com> (raw)
In-Reply-To: <35fbaa3e0707100613r4397bc50h16afe15b89e0bbcb@mail.gmail.com>
Thanks,
I have been using this book as a source, and it is a great one at that.
I thought I read the char device chapter enough times to get what I
needed out of it but apparently not. I just reread it and realized that
my answer was there.
Thanks again,
Jon
On Tue, 2007-07-10 at 16:13 +0300, Vitaliy Ivanov wrote:
> On 7/10/07, Jon Dufresne <jon.dufresne@infinitevideocorporation.com> wrote:
> > I am relatively new to linux device development. And want to understand
> > Linux conventions.
> >
> > Suppose I have a PCI card that is represented in the system by a
> > character device.
> >
> > If I have two of those PCI cards in the system when the driver module
> > loads, is it convention to have two different major numbers, or have one
> > major number and two different minor numbers?
> >
> > Thanks,
> > Jon
>
> You can start your kernel hacking way from ldd. It can be found at:
> http://lwn.net/Kernel/LDD3/
>
> There are a few other books by R. Love or Greg KH that you can read.
>
> Such questions are fully covered there.
>
> Best,
> Vitaliy
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-07-10 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 13:06 Jon Dufresne
2007-07-10 13:13 ` Vitaliy Ivanov
2007-07-10 13:31 ` Jon Dufresne [this message]
2007-07-13 15:32 ` Alan Cox
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=1184074303.31808.33.camel@microwave.infinitevideocorporation.com \
--to=jon.dufresne@infinitevideocorporation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vitalivanov@gmail.com \
/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®