[U-Boot] [PATCH] wandboard: add pxe support, set default boot command like highbank

[Dennis Gilmore]

Resending unsigned

Hi Wolfgang,

On Sun, 04 Aug 2013 22:00:04 +0200
Wolfgang Denk <wd at denx.de> wrote:

> Dear Dennis,
> 
> In message <20130801120603.1683f7a6 at adria.ausil.us> you wrote:
> >
> > ultimately I want to have a standard way to boot any system that
> > just works and does not need the installer to know or care what the
> > target system is. using boot.scr and uEnv.txt does not work for my
> > goals.
> 
> But your requirement is just one out of a number of such requirements,
> and I see no indication that an "one size fits all" approach would be
> possible.
It should be possible for those systems that want a generic linux
distro to run on them. AFAIK the wandboard systems are one of those
that do. It's also a system that doesn't ship with any onboard storage
so distros are forced to build u-boot for it.

> > ultimately for Fedora we do not want to use uEnv.txt or boot.scr at
> > all we want to use a extlinux.conf file and sysboot provided by
> > cmd_pxe the rest is to provide flexibility and options to users to
> > choose different ways to boot. the above is not at all suitable. 
> 
> Just stating what you don't want, and what you want, is not exactly a
> constructive process.  It's like saying: "I'm right, you all are
> wrong."
its not at all, if there is some way to achieve much the same thing
using some other method please let me know. I don't want to force some
solution everywhere. but i want the same solution to be in place for
boards that want to have a generic linux distro be supported on it.

I didn't take out the features we do not want because I understand that
not everyone wants things to be the same, that other ways to do things
is perfectly valid.

> The thing is, that the overwhelming majority of systems are not
> running a standard distro like Fedora, and don't have any such
> features as boot extlinux.conf files or sysboot or whatever -they
> don;t have it, and they cannot afford it because they have totally
> different requirements to meet.  Please try and keep this in mind.
> Yourrequiremetns are but a special case here - one which we will try
> to support in the best possible way, of course, but it's just one out
> of many.

and those systems are free to continue as they do today. they are
likely systems where a generic linux distro just wont run even if you
really try.

Dennis