From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/ppc/spapr: Fix boot path of usb-host storage devices
Date: Wed, 14 Dec 2016 10:36:05 +0100 [thread overview]
Message-ID: <1481708165.8440.19.camel@redhat.com> (raw)
In-Reply-To: <282345c0-fad3-eb66-63c5-3d1d24ab6d6d@redhat.com>
Hi,
> >> in the /chosen/qemu,boot-list property. SLOF, however, probes the
> >> USB device, recognizes that it is a storage device and thus changes
> >> its name to "storage", and additionally adds a child node for the
> >> SCSI LUN, so the correct boot path in SLOF is something like
> >> "/pci@800000020000000/usb@0/storage@1/disk@101000000000000" instead.
Sure this is correct?
usb-storage (aka virtual usb stick) creates paths like this:
/pci@i0cf8/usb@1,2/storage@1/channel@0/disk@0,0
i.e. there is a extra channel element (probably for host adapters with
multiple scsi busses).
> >> So when we detect an USB mass storage device with SCSI interface,
> >> we've got to adjust the firmware boot-device path properly, so that
> >> SLOF can automatically boot from the device.
> > Any reason why this is hidden in ppc/spapr?
> >
> > usb-host could implement the ->fw_name callback instead to create a name
> > depending on the device type ...
> The naming is specific to SLOF ... not sure what happens with other
> firmware implementations, so spapr.c sounds like the better place to me
> right now.
If usb-host (and usb-redir too btw) create paths identical to the ones
created by usb-storage. Existing firmware should cope just fine
(assuming bootindex for usb-storage works).
cheers,
Gerd
next prev parent reply other threads:[~2016-12-14 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 12:44 [Qemu-devel] [PATCH] hw/ppc/spapr: Fix boot path of usb-host storage devices Thomas Huth
2016-12-13 13:52 ` Gerd Hoffmann
2016-12-13 14:29 ` Thomas Huth
2016-12-14 9:36 ` Gerd Hoffmann [this message]
2016-12-14 21:33 ` Thomas Huth
2016-12-15 9:28 ` Gerd Hoffmann
2016-12-15 11:47 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2016-12-14 0:14 ` [Qemu-devel] " David Gibson
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=1481708165.8440.19.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).