From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: config ARCH_AT91SAM9X5
Date: Mon, 31 Oct 2011 14:16:11 +0100 [thread overview]
Message-ID: <4EAE9F9B.4040201@pengutronix.de> (raw)
In-Reply-To: <1320062362.14409.58.camel@x61.thuisdomein>
On 10/31/2011 12:59 PM, Paul Bolle wrote:
> 0) Since the commits
> 9baeb7e4 ("at91: Add ARCH_ID and basic cpu macros [...]"),
> b9e379bc ("net/can: allow CAN_AT91 on AT91SAM9X5"), and
> 8c3583b6 ("at91: use structure to store the current soc")
>
> the mainline kernel tree uses the Kconfig symbol ARCH_AT91SAM9X5 and the
> preprocessor macro CONFIG_ARCH_AT91SAM9X5.
>
> 1) But there's currently no Kconfig entry ARCH_AT91SAM9X5. (Neither is
> there a direct definition of the macro CONFIG_ARCH_AT91SAM9X5.)
> Shouldn't a Kconfig entry for ARCH_AT91SAM9X5 be added (to
> arch/arm/mach-at91/Kconfig)?
Talking for the at91_can driver (which has been done by me):
The driver and Kconfig have been prepared for the upcoming 5series AT91
SOCs.
Basically the same applies to the commit 9baeb7e4 ("at91: Add ARCH_ID
and basic cpu macros [...]").
But the 5series hasn't bee merged yet. Nicolas and Jean-Christophe can
probably tell you more.
regards, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111031/7e70a2cc/attachment.sig>
next prev parent reply other threads:[~2011-10-31 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 11:59 config ARCH_AT91SAM9X5 Paul Bolle
2011-10-31 13:16 ` Marc Kleine-Budde [this message]
2011-11-04 10:27 ` Nicolas Ferre
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=4EAE9F9B.4040201@pengutronix.de \
--to=mkl@pengutronix.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 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).