From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: sunxi: Change device tree naming scheme for sunxi
Date: Fri, 14 Dec 2012 18:10:43 +0100 [thread overview]
Message-ID: <50CB5D93.7080405@free-electrons.com> (raw)
In-Reply-To: <201212131200.48413.arnd@arndb.de>
Hi Arnd,
Le 13/12/2012 13:00, Arnd Bergmann a ?crit :
> On Wednesday 12 December 2012, Maxime Ripard wrote:
>> There is several different SoCs sharing the sun5i codename: A10s, A12
>> and A13. Since there is enough differences to not consider those the
>> same SoCs, change a bit the naming scheme to reflect this.
>>
>> Moreover, some boards like the olinuxino come in A10s and A13 variants,
>> which also share the same SoC codename.
>>
>> So change the naming scheme to reflect both the codename and the market
>> name of the SoCs used in the dtsi and in the board files
>>
>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Will you take it directly, or do you want a pull request?
> Side note:
> I just read about the A20 and A31, is there any information and/or
> source code available for those already, or are they again kept
> hidden by Allwinner?
There's been a tablet announced with an A31 running Android (the Onda
V972), so I guess we can expect a source drop sometime soon, but for the
A20, I don't know. It looks like Allwinner even removed all references
to that SoC on their website, so...
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-14 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 16:08 [PATCHv2] ARM: sunxi: Change device tree naming scheme for sunxi Maxime Ripard
2012-12-13 12:00 ` Arnd Bergmann
2012-12-14 17:10 ` Maxime Ripard [this message]
2012-12-14 18:06 ` Olof Johansson
2012-12-14 23:34 ` Alejandro Mery
2012-12-15 10:45 ` Russell King - ARM Linux
2012-12-16 6:53 ` Olof Johansson
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=50CB5D93.7080405@free-electrons.com \
--to=maxime.ripard@free-electrons.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 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.