Greg KH wrote:
Because "struct device" generally is not related to a major:minor pair
at all. That is what a struct class_device is for. Lots of struct
device users have nothing to do with a char device, and some have
multiple char devices associated with a single struct device.
Well, OK, but AFAIK, your long-term plan is to merge class_device and
device, so in the long-term perspective it does not matter. And those
who do not need a character device support may have a possibility to
disable it.
All that being said, yes, there is a disconnect between the driver model
parts and the char subsystem. It's been something that I've wanted to
fix for a number of years, but never had the time to do so. If you want
to work toward doing this, I'd be glad to review any patches.
Will see. At this point my knowledge and understanding is not so deep,
so I don't think I'm able to provide decent patches. May be in future.
For now I'm only wondering.
Thanks.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
