> > I have been writing a device driver for a specialty board we use here at my
> > workplace. I am writing it as a module. Because of the possibility of a
> > conflict with a MAJOR number, I want have the module ask for the next
> > available MAJOR number. This causes problems because I have to provide a
> > script which creates the device inode files in /dev.
>
> This doesnt help you at all. Suppose you ask for the next number and take
> the one a later module will need. There are a set of major numbers for
> private/experimental use. Nobody should be shipping any actual production
> drivers using these numbers.
>
> Alan
I was taking the advice of Alessandro Rubini in his book Linux Device Drivers. He
suggested using dynamic allocation of major numbers by setting the major to zero
in
the request_chrdev. Is this *not* the preferred method?
Kevin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/