From: Pavel Machek <pavel@ucw.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Arnd Bergmann <arnd@bergmann-dalldorf.de>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arndb@de.ibm.com>
Subject: Re: driverfs problem
Date: Tue, 21 May 2002 23:26:06 +0200 [thread overview]
Message-ID: <20020521212606.GB3050@elf.ucw.cz> (raw)
In-Reply-To: <200205171408.g4HE8tK65272@d12relay02.de.ibm.com> <Pine.LNX.4.33.0205200750490.820-100000@geena.pdx.osdl.net>
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
next prev parent reply other threads:[~2002-05-21 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 16:08 driverfs problems Arnd Bergmann
2002-05-20 16:39 ` driverfs problem Patrick Mochel
2002-05-21 15:52 ` Arnd Bergmann
2002-05-21 21:26 ` Pavel Machek [this message]
2002-05-21 21:24 ` driverfs problems Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020521212606.GB3050@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arnd@bergmann-dalldorf.de \
--cc=arndb@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®