Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement

From	Carlo Caione <carlo@caione.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement
Date	2016-03-23 09:10 +0100
Message-ID	<rfM1A-ze-11@gated-at.bofh.it> (permalink)
References	<r84RH-1dc-11@gated-at.bofh.it> <rfgEq-3EB-37@gated-at.bofh.it> <rfB6b-1hK-43@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Mar 22, 2016 at 9:29 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 21.03.2016 um 23:36 schrieb Kevin Hilman:
>> On Tue, Mar 1, 2016 at 6:34 PM, Andreas Färber <afaerber@suse.de> wrote:
>>
>>> Note: On the Vega S95 I need to change TEXT_OFFSET as follows,
>>> in order to avoid the vendor U-Boot overwriting itself (fwiu);
>>> for the Mini Mx that's reportedly not necessary.
>>
>> FYI, the Amlogic P200 dev board also needs this hack with the factory u-boot.
>
> I have meanwhile found that
>
> mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 \
> -n linux-next -d arch/arm64/boot/Image ../uImage
>
> and then using bootm instead of booti works even without the above hack
> on the Vega S95. Not a satisfactory solution yet, but better than
> patching the kernel in a distro-incompatible way.

I wonder if we can add this kind of information in Documentation/arm/meson/.
Probably it could be handy until we have a proper u-boot porting.

-- 
Carlo Caione

Thread

Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement Kevin Hilman <khilman@baylibre.com> - 2016-03-21 23:40 +0100
  Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95  enablement Andreas Färber <afaerber@suse.de> - 2016-03-22 21:30 +0100
    Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement Carlo Caione <carlo@caione.org> - 2016-03-23 09:10 +0100
    Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement Kevin Hilman <khilman@baylibre.com> - 2016-03-23 19:20 +0100

csiph-web