David Laight wrote:
> This isn't really an ideal solution, I've have to fight membar
> instructions embedded into byteswapping accesses on ppc linux.
> Drivers may want to do several accesses that can be reordered
> before/after one that matters - so need greater control than
> enforcing specific
On Sun, Oct 30, 2011 at 09:08:33PM +, Frank Wille wrote:
> Module Name: src
> Committed By: phx
> Date: Sun Oct 30 21:08:33 UTC 2011
>
> Modified Files:
> src/sys/arch/sandpoint/stand/altboot: brdsetup.c dsk.c entry.S fxp.c
> globals.h nvt.c rge.c skg.c stg.c vge.c
>
David Laight wrote:
> Can anything be done with the 'initrd' image - either as an image file
> or something in the tar archive (IIRC it is likely to be one these days)?
Altboot could theoretically use information from the initrd image. For
example I thought about passing the bootargs in it.
But
On Sun, Mar 20, 2011 at 02:07:05AM +, Frank Wille wrote:
>
> Log Message:
> The DSM-G600 U-Boot is so restricted that there is no possibility to pass
> any bootargs. So we will just do the default multiuser boot from wd0: when
> altboot was started together with a Linux initrd image.
Can anyt
