All of lore.kernel.org
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement
Date: Tue, 22 Mar 2016 21:29:26 +0100	[thread overview]
Message-ID: <56F1AB26.8050200@suse.de> (raw)
In-Reply-To: <CAOi56cXFEUZuu0bJknUYNhfR2jL=LYUTbpnX9diZw2B5JfTaEQ@mail.gmail.com>

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.

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)

WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
To: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: linux-meson <linux-meson-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	"Carlo Caione" <carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>,
	linux-arm-kernel
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"Matthias Brugger" <mbrugger-IBi9RG/b67k@public.gmane.org>,
	"Nicolas Saenz"
	<nicolassaenzj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"André Przywara" <andre.przywara-5wv7dgnIgG8@public.gmane.org>,
	"Sudeep Holla" <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Catalin Marinas" <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
	"Will Deacon" <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Mark Rutland" <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement
Date: Tue, 22 Mar 2016 21:29:26 +0100	[thread overview]
Message-ID: <56F1AB26.8050200@suse.de> (raw)
In-Reply-To: <CAOi56cXFEUZuu0bJknUYNhfR2jL=LYUTbpnX9diZw2B5JfTaEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Kevin Hilman <khilman@baylibre.com>
Cc: linux-meson <linux-meson@googlegroups.com>,
	"Carlo Caione" <carlo@caione.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"Matthias Brugger" <mbrugger@suse.com>,
	"Nicolas Saenz" <nicolassaenzj@gmail.com>,
	"André Przywara" <andre.przywara@arm.com>,
	"Sudeep Holla" <sudeep.holla@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will.deacon@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement
Date: Tue, 22 Mar 2016 21:29:26 +0100	[thread overview]
Message-ID: <56F1AB26.8050200@suse.de> (raw)
In-Reply-To: <CAOi56cXFEUZuu0bJknUYNhfR2jL=LYUTbpnX9diZw2B5JfTaEQ@mail.gmail.com>

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.

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

  reply	other threads:[~2016-03-22 20:29 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  2:34 [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement Andreas Färber
2016-03-02  2:34 ` Andreas Färber
2016-03-02  2:34 ` Andreas Färber
2016-03-02  2:34 ` [PATCH v2 1/6] ARM64: Enable Amlogic Meson GXBaby platform Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:34 ` [PATCH v2 2/6] devicetree: bindings: Add vendor prefix for Tronsmart Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:34 ` [PATCH v2 3/6] Documentation: devicetree: amlogic: Document Meson GXBaby Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-05  4:27   ` Rob Herring
2016-03-05  4:27     ` Rob Herring
2016-03-02  2:34 ` [PATCH v2 4/6] ARM64: dts: Prepare configs for Amlogic " Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:34   ` Andreas Färber
2016-03-02  2:35 ` [PATCH v2 5/6] Documentation: devicetree: amlogic: Document Tronsmart Vega S95 boards Andreas Färber
2016-03-02  2:35   ` Andreas Färber
2016-03-02  2:35   ` Andreas Färber
2016-03-05  4:27   ` Rob Herring
2016-03-05  4:27     ` Rob Herring
2016-03-02  2:35 ` [PATCH v2 6/6] ARM64: dts: amlogic: Add Tronsmart Vega S95 configs Andreas Färber
2016-03-02  2:35   ` Andreas Färber
2016-03-02  2:35   ` Andreas Färber
2016-03-02 13:52 ` [PATCH v2 0/6] ARM64: meson: GXBaby (S905) and Vega S95 enablement Mark Rutland
2016-03-02 13:52   ` Mark Rutland
2016-03-02 13:52   ` Mark Rutland
2016-03-02 14:31   ` Andreas Färber
2016-03-02 14:31     ` Andreas Färber
2016-03-02 14:31     ` Andreas Färber
2016-03-02 15:17     ` Mark Rutland
2016-03-02 15:17       ` Mark Rutland
2016-03-07  8:20 ` Carlo Caione
2016-03-07  8:20   ` Carlo Caione
2016-03-07  8:20   ` Carlo Caione
2016-03-21 22:36 ` Kevin Hilman
2016-03-21 22:36   ` Kevin Hilman
2016-03-21 22:36   ` Kevin Hilman
2016-03-22 20:29   ` Andreas Färber [this message]
2016-03-22 20:29     ` Andreas Färber
2016-03-22 20:29     ` Andreas Färber
2016-03-23  8:06     ` Carlo Caione
2016-03-23  8:06       ` Carlo Caione
2016-03-23  8:06       ` Carlo Caione
2016-03-23 18:10     ` Kevin Hilman
2016-03-23 18:10       ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56F1AB26.8050200@suse.de \
    --to=afaerber@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.