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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7hoaa5qd4x.fsf@baylibre.com>
Date:	Wed, 23 Mar 2016 11:10:06 -0700
From:	Kevin Hilman <khilman@...libre.com>
To:	Andreas Färber <afaerber@...e.de>
Cc:	linux-meson <linux-meson@...glegroups.com>,
	Carlo Caione <carlo@...one.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Matthias Brugger <mbrugger@...e.com>,
	Nicolas Saenz <nicolassaenzj@...il.com>,
	André Przywara <andre.przywara@....com>,
	Sudeep Holla <sudeep.holla@....com>,
	devicetree <devicetree@...r.kernel.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	LKML <linux-kernel@...r.kernel.org>,
	Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement

Andreas Färber <afaerber@...e.de> writes:

> Am 21.03.2016 um 23:36 schrieb Kevin Hilman:
>> On Tue, Mar 1, 2016 at 6:34 PM, Andreas Färber <afaerber@...e.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.

Thanks for sharing.  I can confirm this is working for me too.

Kevin