Messages in this thread | | | Date | Tue, 21 May 2002 23:26:06 +0200 | From | Pavel Machek <> | Subject | Re: driverfs problem |
| |
Hi!
> > - I'm not sure about how to name the device directories. I don't have anything > > like a hierarchical structure (except for something like scsi devices behind > > a channel device) but rather a flat list of up to 65536 devices that are > > accessed by a device number that was defined by the system administrator. > > Each device also has a control unit type, comparable to a PCI ID, and in the > > general case each device driver knows about one control unit type. A > > hypothetical system might have > > - one console, control unit type 0x3215, device number 0x0000 > > - three network devices, control unit type 0x1732, devno 0x0100 to 0x0102 > > - 1024 storage devices, control unit type 0x3390, devno 0x1000 to 0x13ff > > The control unit types are irrelevant at this point, as they dictate the > type of device. You want to accurately represent the physical layout of > the system.
s390 is linux on the top of vm. Linux runs under vmware-kind of machine.... Its difficult to talk about "physical". Pavel -- (about SSSCA) "I don't say this lightly. However, I really think that the U.S. no longer is classifiable as a democracy, but rather as a plutocracy." --hpa - 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/
| |