On Thu, Oct 04, 2012 at 02:37:22PM +0200, Alexander Graf wrote: > > On 04.10.2012, at 14:35, Avik Sil wrote: > > >>>>>> So you want to hack around the problem. If -boot is specified what > >>>>>> device are you going to boot from? > >>>>> > >>>>> It is going to boot from the device specified in -boot as > >>>>> default_boot_order is set to 0 in that case. > >>>> > >>>> Imagine you have 2 controllers: > >>>> > >>>> * vio > >>>> * virtio > >>>> > >>>> and you specify -boot c. Which device are you going to boot from? > >>> > >>> Currently, by default SLOF boots from the first disk it discovers in the > >>> device tree. > >> > >> So you want to replace one broken scheme with another broken scheme? :) > > > > Ha ha, actually we hit this issue in some different context with respect to > > nvram boot-device which I mentioned in [1]. The patch is a workaround for > > that issue only. > > Seriously, just ignore -boot for now. It'd be a lot more useful to get > bootindex working. > +1
-- Gleb.