From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/2] AT91: Update board-cpu9krea to support the 9260/9G20 variants in a single image
Date: Mon, 17 Jan 2011 10:02:26 +0100 [thread overview]
Message-ID: <4D3405A2.70401@eukrea.com> (raw)
In-Reply-To: <20110117075002.GH14798@game.jcrosoft.org>
Hi Jean-Christophe,
On 17/01/2011 08:50, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 18:50 Sat 15 Jan , Albin Tonnerre wrote:
>> Since patch "Support SAM9260 and SAM9G20-based boards in the same kernel
>> image" makes it possible to support both types of SoCs, cpu9krea must be
>> updated to cope with that. Otherwise, selecting both the 9260 and 9G20
>> variants will result in only the 9260 variant being supported.
>>
>> Signed-off-by: Albin Tonnerre<albin.tonnerre@free-electrons.com>
>> ---
> do you really need 2 machine id?
>
this was needed when 9260 & 9G20 were not merged.
Please if you change our platform files keep the 2 machine ID else that will
break upgrade path on existing machines.
Thanks,
Eric
next prev parent reply other threads:[~2011-01-17 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 17:50 [RFC 1/2] AT91: Support SAM9260 and SAM9G20-based boards in the same kernel image Albin Tonnerre
2011-01-15 17:50 ` [RFC 2/2] AT91: Update board-cpu9krea to support the 9260/9G20 variants in a single image Albin Tonnerre
2011-01-17 7:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-17 9:02 ` Eric Bénard [this message]
2011-01-17 7:57 ` [RFC 1/2] AT91: Support SAM9260 and SAM9G20-based boards in the same kernel image Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 7:00 ` Albin Tonnerre
2011-01-18 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 15:32 ` Russell King - ARM Linux
2011-01-18 17:18 ` Gilles Chanteperdrix
2011-01-18 17:43 ` Russell King - ARM Linux
2011-01-18 18:52 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 19:35 ` Russell King - ARM Linux
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=4D3405A2.70401@eukrea.com \
--to=eric@eukrea.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).