From: plyatov@gmail.com (Igor Plyatov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] mach-at91: Support for gms board added
Date: Wed, 08 Dec 2010 22:29:28 +0300 [thread overview]
Message-ID: <1291836568.15873.58.camel@homepc> (raw)
In-Reply-To: <20101208140313.GD3429@game.jcrosoft.org>
Dear Jean-Christophe,
> > I have exactly the same feeling as Ryan. We should make sure
> > to factorize as much code as possible for maintenance reasons.
> >
> > If you need to distinguish between board features, you can
> > pass information in system_rev as implemented in this
> > board merging commit:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a6e016f19d393fbe4e040bee8155b03b840fa689
> I agree with nico not need to have a new board for just few difference
>
> and as we start with the rm9200 we will reduce the number of defconfig first per soc and then for the all sam9
I think it does not make sence to invent new machine for each new
carrier board. Better to have a kernel configuration options which will
allow to select required carrier board.
Best regards!
--
Igor Plyatov
WARNING: multiple messages have this Message-ID (diff)
From: Igor Plyatov <plyatov@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Ryan Mallon <ryan@bluewatersys.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@maxim.org.za,
linux@arm.linux.org.uk, costa.antonior@gmail.com
Subject: Re: [PATCH v2] mach-at91: Support for gms board added
Date: Wed, 08 Dec 2010 22:29:28 +0300 [thread overview]
Message-ID: <1291836568.15873.58.camel@homepc> (raw)
In-Reply-To: <20101208140313.GD3429@game.jcrosoft.org>
Dear Jean-Christophe,
> > I have exactly the same feeling as Ryan. We should make sure
> > to factorize as much code as possible for maintenance reasons.
> >
> > If you need to distinguish between board features, you can
> > pass information in system_rev as implemented in this
> > board merging commit:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a6e016f19d393fbe4e040bee8155b03b840fa689
> I agree with nico not need to have a new board for just few difference
>
> and as we start with the rm9200 we will reduce the number of defconfig first per soc and then for the all sam9
I think it does not make sence to invent new machine for each new
carrier board. Better to have a kernel configuration options which will
allow to select required carrier board.
Best regards!
--
Igor Plyatov
next prev parent reply other threads:[~2010-12-08 19:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 14:42 [PATCH v2] mach-at91: Support for gms board added Igor Plyatov
2010-12-07 14:42 ` Igor Plyatov
2010-12-07 19:53 ` Ryan Mallon
2010-12-07 19:53 ` Ryan Mallon
2010-12-08 8:53 ` Nicolas Ferre
2010-12-08 8:53 ` Nicolas Ferre
2010-12-08 14:03 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-08 14:03 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-08 19:29 ` Igor Plyatov [this message]
2010-12-08 19:29 ` Igor Plyatov
2010-12-08 14:50 ` Christian Glindkamp
2010-12-08 14:50 ` Christian Glindkamp
2010-12-08 20:08 ` Ryan Mallon
2010-12-08 20:08 ` Ryan Mallon
2010-12-09 10:15 ` [PATCH] at91: Refactor Stamp9G20 and PControl G20 board file Christian Glindkamp
2010-12-09 10:15 ` Christian Glindkamp
2010-12-10 3:38 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-10 3:38 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-10 9:03 ` Christian Glindkamp
2010-12-10 9:03 ` Christian Glindkamp
2010-12-10 6:19 ` Igor Plyatov
2010-12-10 6:19 ` Igor Plyatov
[not found] ` <1291909193.6251.32.camel@homepc>
2010-12-10 8:44 ` Christian Glindkamp
2010-12-10 8:44 ` Christian Glindkamp
2010-12-10 9:45 ` Nicolas Ferre
2010-12-10 9:45 ` Nicolas Ferre
2010-12-08 19:26 ` [PATCH v2] mach-at91: Support for gms board added Igor Plyatov
2010-12-08 19:26 ` Igor Plyatov
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=1291836568.15873.58.camel@homepc \
--to=plyatov@gmail.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.