Hi Brendan,
I may be way of the mark with my suggestions as I am not that familiar
with ARM, but here goes:
On Wed, Mar 27, 2013 at 10:39 AM, Brendan Conoboy <blc(a)redhat.com> wrote:
The trouble is, there is no unified $ubootAddress available. The
pandaboard
uses 0x80008000, highbank and tegra use 0x00008000, a10 and exynos5 use
0x40008000, and so forth. Not sure about beaglebone. If we want to realize
the dream of having a unified F19 release we need a solution to this
problem. I see three options:
1. Use the 0x00008000 address for highbank/tegra, demand bootz support for
everybody else. Since we control the panda/beagle/beaglebone uboots they
would be covered. Not clear on what this means for exynos5, but exynos5
will use an LPAE kernel so that's a separate uimage already.
2. Generate multiple uImage files from a single kernel, then load the
appropriate uImage on boot.
3. Split up images to cope.
All 3 are viable, none are desirable. Is there a 4th option? If not, what
do want to go with?
4. Relocatable kernel (like x86)
5. Have U-Boot process uImage to adjust for load location (U-Boot
already does a similar thing for itself)
Regards,
Graeme