From: Teresa Gamez <T.Gamez@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: add board support for Phytec phyCARD-M aka pca101
Date: Wed, 21 Dec 2011 16:19:36 +0100 [thread overview]
Message-ID: <1324480776.18539.107.camel@lws-gamez> (raw)
In-Reply-To: <20111221134958.GV27267@pengutronix.de>
Am Mittwoch, den 21.12.2011, 14:49 +0100 schrieb Sascha Hauer:
> On Wed, Dec 21, 2011 at 02:05:48PM +0100, Teresa Gamez wrote:
> > Hello Sascha,
> >
> > we want to use a different name convention for all the phyCARDs since it
> > is quite chaotic atm.
>
> Indeed.
>
> > Christian is working on patches for the phyCARD-M1
> > with the new name convention.
>
> How will the new name convention look like?
The board name looks like this:
phyCARD-<generation>-<type><revision>
The phyCARD-M is called correctly phyCARD-A-M1.
The Kconfig suppose look like this:
@@ -356,6 +358,13 @@ config MACH_PCM043
Say Y here if you are using Phytec's phyCORE-i.MX35 (pcm043)
equipped
with a Freescale i.MX35 Processor
+config MACH_PCAAM1
+ bool "phyCARD-A-M1"
+ select MACH_HAS_LOWLEVEL_INIT
+ help
+ Say Y here if you are using Phytec's phyCARD-A-M1 (pca-a-m1)
equipped
+ with a Freescale i.MX35 Processor
+
config MACH_GUF_CUPID
bool "Garz+Fricke Cupid"
select MACH_HAS_LOWLEVEL_INIT
Board code name:
a/arch/arm/boards/phycard-a-m1/pca-a-m1.c
Function names (example):
static int pcaam1_init_devices(void)
defconfig:
arch/arm/configs/phycard_a_m1_defconfig
Teresa
>
> Sascha
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-12-21 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:36 Sascha Hauer
2011-12-21 13:05 ` Teresa Gamez
2011-12-21 13:49 ` Sascha Hauer
2011-12-21 15:19 ` Teresa Gamez [this message]
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=1324480776.18539.107.camel@lws-gamez \
--to=t.gamez@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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