given that the current definition of a major device number is a 12-bit value (include/linux/kdev_t.h), is there any reason that dynamic allocation of major numbers via alloc_chrdev_region() limits itself based on the value of include/linux/fs.h:#define CHRDEV_MAJOR_HASH_SIZE 255 sure, i realize there's no real danger of running out of major numbers, but i'm just curious. i'm wondering what other places in the source tree might have a hard-coded value of 255 for that. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://fsdev.net/wiki/index.php?title=Main_Page ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
