From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [V2 1/3] mxc: Add support for the imx51 3-stack board
Date: Fri, 4 Jun 2010 17:22:58 +0200 [thread overview]
Message-ID: <20100604152258.GC25357@pengutronix.de> (raw)
In-Reply-To: <1275644934.3210.46.camel@realization>
On Fri, Jun 04, 2010 at 11:48:54AM +0200, Alberto Panizzo wrote:
> On ven, 2010-06-04 at 10:53 +0200, Sascha Hauer wrote:
> > I'm not willing to accept another 3ds_debug board support in the
> > kernel
> > given that it's no rocket science to seperate this into another file
> > and
> > we still have plenty of time before the next merge window.
> > Jason, can you please move this to plat-mxc? I think we could find
> > someone else to switch the mx31_3ds support to the generic debug board
> > support then.
>
> Sascha, what do you mean with: switch the mx31_3ds support to the generic
> one in plat-mxc?
Only the 3ds debug board, not the mx31_3ds board as a whole.
> We are going to have a single machine file for all imx(2-3-5) based debug boards?
> I think it will look so messy..
Look at Jasons next patch, this is what I meant. We can reuse the 3ds
debug board stuff in the mx31_3ds.
>
> I read the Linus concerns about ARM stuffs and RMK answer to your ask for pull..
> May we need to start a thread to discuss how we can restructure the imx support?
Well, the ultimate goal is to support all i.MX ports in one kernel, but
this is still a long way to go. We made quite some progress with Uwes
patches to avoid namespace collisions in the different register defines,
but there is still enough left to do. Try to tweak Kconfig to enable for
example i.MX27 and i.MX25 support and see what happens...
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2010-06-04 15:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 12:05 [V2 0/3]Add i.MX51 3-stack board support Jason Wang
2010-06-03 12:05 ` [V2 1/3] mxc: Add support for the imx51 3-stack board Jason Wang
2010-06-03 12:05 ` [V2 2/3] mxc/iomux: add GPIO bank offset for iomux v3 platforms Jason Wang
2010-06-03 12:05 ` [V2 3/3] mx51/keypad: add keypad support for i.MX51 platforms Jason Wang
2010-06-05 9:35 ` Alberto Panizzo
2010-06-05 14:13 ` jason
2010-06-06 18:11 ` Alberto Panizzo
2010-06-07 23:22 ` jason
2010-06-03 12:39 ` [V2 1/3] mxc: Add support for the imx51 3-stack board Amit Kucheria
2010-06-03 13:57 ` Sascha Hauer
2010-06-03 14:35 ` Amit Kucheria
2010-06-03 14:36 ` jason
2010-06-03 14:39 ` jason
2010-06-04 8:53 ` Sascha Hauer
2010-06-04 9:48 ` Alberto Panizzo
2010-06-04 15:22 ` Sascha Hauer [this message]
2010-06-04 10:53 ` Amit Kucheria
2010-06-04 14:09 ` [PATCH] mxc: Fix pad names for imx51 Amit Kucheria
2010-06-07 20:41 ` Troy Kisky
2010-06-07 21:04 ` Amit Kucheria
2010-06-07 21:15 ` Troy Kisky
2010-06-08 6:30 ` Sascha Hauer
2010-06-09 13:09 ` Amit Kucheria
2010-06-10 11:49 ` Sascha Hauer
2010-06-10 13:04 ` jason
2010-06-10 13:59 ` Sascha Hauer
2010-06-10 19:24 ` Amit Kucheria
2010-06-04 12:50 ` [V2 1/3] mxc: Add support for the imx51 3-stack board jason
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=20100604152258.GC25357@pengutronix.de \
--to=s.hauer@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).