From: Olaf Hering <olaf@aepfle.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: bogus vscsi dt node on iseries
Date: Thu, 23 Aug 2007 07:42:39 +0200 [thread overview]
Message-ID: <20070823054239.GA24251@aepfle.de> (raw)
In-Reply-To: <20070823133621.830245c4.sfr@canb.auug.org.au>
On Thu, Aug 23, Stephen Rothwell wrote:
> On Wed, 22 Aug 2007 19:51:21 +0200 Olaf Hering <olaf@aepfle.de> wrote:
> >
> >
> > Does anyone know why dt_vdevices() creates a vscsi node on legacy iseries?
> > I'm sure only viodasd and viocd is required as blockdevice type.
>
> Because the IBM vscsi client (in theory) works on legacy iSeries.
I'm asking because there are many unneeded nodes.
Have you tried to create only the nodes for disks/cds that are really
present and modify viodasd to use only device-tree data?
next prev parent reply other threads:[~2007-08-23 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 17:51 bogus vscsi dt node on iseries Olaf Hering
2007-08-23 3:36 ` Stephen Rothwell
2007-08-23 5:42 ` Olaf Hering [this message]
2007-08-23 5:59 ` 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=20070823054239.GA24251@aepfle.de \
--to=olaf@aepfle.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).