bogus vscsi dt node on iseries
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.
Quoted 4 lines · On Wed, 22 Aug 2007 19:51:21 +0200 Olaf Hering <[email protected]> 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.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Quoted 7 lines · Stephen Rothwell
Quoted 4 lines · On Wed, 22 Aug 2007 19:51:21 +0200 Olaf Hering <[email protected]> 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?
Quoted 6 lines · On Thu, 23 Aug 2007 07:42:39 +0200 Olaf Hering <[email protected]> wrote:
Quoted 3 lines · Stephen Rothwell
Quoted 2 lines · On Wed, 22 Aug 2007 19:51:21 +0200 Olaf Hering <[email protected]> wrote:
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
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?
I'll have a look, but that would require interacting with the hypervisor very early in the boot sequence ...
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/