Messages in this thread | | | Date | Thu, 20 Mar 2003 22:00:48 +0100 (CET) | From | Roman Zippel <> | Subject | Re: major/minor split |
| |
Hi,
On Wed, 19 Mar 2003 Andries.Brouwer@cwi.nl wrote:
> (I hope the purpose of distinguishing arithmetic types dev_t > and kdev_t is clear. The latter is simple e.g. 13+19. > mk_kdev, major, minor are simple macros. Kernel use is fast, > no conditional involved. > The former must be backwards compatible, so MKDEV, MAJOR, MINOR > are somewhat complicated macros; for example MAJOR asks: does it fit > in 16 bits? then MAJOR is the first 8; otherwise MAJOR is > the first DEV_MAJOR_BITS. Used only when converting from userspace.)
There is a point I'd like to get clear: where should the 16bit<->32bit dev_t conversion happen? I think any software that cares about this should be safe by now. That leaves us with on-disk and on-wire formats and IMO only at these places a conversion should happen. The other problem is how can software create nodes for a specific device?
bye, Roman
- 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/
| |