Minors remaining in Major 10 ??
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · H. Peter Anvin
Quoted 6 lines · Andre Hedrick
Quoted 5 lines
No, I think I understood perfectly well. I said that if it's going to be bound to each block device subsystem it would make more sense to establish that tie explicitly -- if that isn't possible I'm a bit confused.
Quoted 7 lines
Quoted 3 lines
Okay, I am definitely not clear because I am leading the wrong direction. A single char-device would access all of ATA or all of SCSI.
That's fine. ATA and SCSI are a bit special because they have multiple majors -- something that I hope we can get rid of with the
dev_texpansion anyway, but I think the principle still holds.
Hi Peter,
Regardless if we rip out the entire rule of majors for dev_t, will there be a service dummy driver to various block-devices? There is a real need for this if we are going to get full control of the hardware by indirect access obtain the functionality that I see and need in the near future.
I want to use KMOD to an advantage.
Assume removable device bays such that you can swap in any and every kind of ata-atapi device and/or all scsi-devices, one needs to have a way to tell the driver to do things that are not native to its general mode of operations as of today.
Cheers,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Andre Hedrick
Hi Peter,
Regardless if we rip out the entire rule of majors for
dev_t, will there be a service dummy driver to various block-devices? There is a real need for this if we are going to get full control of the hardware by indirect access obtain the functionality that I see and need in the near future.
At this point, I'll allocate a device number when someone is ready to release a driver - no sooner. There simply is not a whole lot of choice because of the extreme shortage of device numbers that's going to last us until dev_t gets expanded.
-hpad
Signature · 7 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 10 lines · H. Peter Anvin
Quoted 8 lines · Andre Hedrick
Hi Peter,
Regardless if we rip out the entire rule of majors for
dev_t, will there be a service dummy driver to various block-devices? There is a real need for this if we are going to get full control of the hardware by indirect access obtain the functionality that I see and need in the near future.
Quoted 4 lines
At this point, I'll allocate a device number when someone is ready to release a driver - no sooner. There simply is not a whole lot of choice because of the extreme shortage of device numbers that's going to last us until
dev_tgets expanded.
Cool Peter!
Will finish the code hack and clean it up in the next three days or so... It is only an idea to test and you can see it in action first.
Cheers,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/