From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Linus <torvalds@osdl.org>, LKML <linux-kernel@vger.kernel.org>,
boutcher@us.ibm.com, katzj@redhat.com, ipseries-list@redhat.com,
linuxppc64-dev@lists.linuxppc.org
Subject: [PATCH] 0/5 PPC64 - make iSeries virtual devices/drivers appear in sysfs
Date: Tue, 29 Jun 2004 02:28:06 +1000 [thread overview]
Message-ID: <20040629022806.4fda7605.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
Hi Andrew, Linus,
This is the patch I submitted for comment last week broken up a bit.
The purpose of the patch set is to integrate the iSeries virtual device
drivers in the driver infrastructure to allow for fairly reasonable user
mode probing for devices.
For each possible virtual device, there is an entry in /sys/devices/vio
and /sys/bus/vio/devices with the exception of the virtual ethernets where
there is an entry for each virtual lan that is actually configured. When
the appropriate device driver is loaded (if it is a module), then entries
for actually configured devices appear in
/sys/bus/vio/drivers/<drivername>. To only create entries for configured
devices in /sys/devices/vio (etc) would require some rework and moving of
the device probing code for each driver. This may be done in the future.
This patch set is meant to be fairly minimal in order to get user mode
device enumeration.
The patches following are:
1) update the vio infrastructure so that iSeries can use it. This
patch has only very small changes to the way pSeries works - and then only
internally to vio.c (apart from the renaminf of one routine).
2) integrate iseries_veth
3) viodasd
4) viocd
5) viotape
arch/ppc64/kernel/vio.c | 189 +++++++++++++++++++++++++-----------
drivers/block/viodasd.c | 87 ++++++++++------
drivers/cdrom/viocd.c | 185 +++++++++++++++++++++--------------
drivers/char/viotape.c | 119 ++++++++++++++--------
drivers/net/iseries_veth.c | 104 ++++++++++++-------
drivers/net/iseries_veth.h | 2
drivers/pci/hotplug/rpaphp_vio.c | 4
include/asm-ppc64/iSeries/HvTypes.h | 4
include/asm-ppc64/vio.h | 8 +
9 files changed, 456 insertions(+), 246 deletions(-)
As I said, I posted this patch set as a single patch last week.
Unless we have objections, please apply.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-06-28 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 16:28 Stephen Rothwell [this message]
2004-06-28 16:33 ` [PATCH] 1/5 PPC64 - vio infrastructure modifications Stephen Rothwell
2004-06-28 16:35 ` [PATCH] 2/5 PPC64 - iseries_veth integration Stephen Rothwell
2004-06-28 16:38 ` [PATCH] 3/5 PPC64 - viodasd integration Stephen Rothwell
2004-06-28 16:39 ` [PATCH] 4/5 PPC64 - viocd integration Stephen Rothwell
2004-06-28 16:41 ` [PATCH] 5/5 PPC64 - viotape integration Stephen Rothwell
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=20040629022806.4fda7605.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@osdl.org \
--cc=boutcher@us.ibm.com \
--cc=ipseries-list@redhat.com \
--cc=katzj@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=torvalds@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®