From: Felipe Balbi <me@felipebalbi.com>
To: twebb <taliaferro62@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>,
david-b@pacbell.net
Subject: Re: [PATCH 0/0] Add minimal omap34xx support
Date: Sat, 4 Oct 2008 23:37:03 +0300 [thread overview]
Message-ID: <20081004203700.GK10743@frodo> (raw)
In-Reply-To: <dbdb2ea60810040542n377bafc9sabec371c294e4151@mail.gmail.com>
On Sat, Oct 04, 2008 at 08:42:18AM -0400, twebb wrote:
> >
> > Yeah there is active development going on in linux-omap mailing list
> > for the EVMs too. And Mistral's older 5912OSK is probably the best
> > supported omap board in the mainline kernel.
> >
> > Basically adding new boards is just a question of adding the board-*.c
> > file, and .config for the drivers to include. Some board of course
> > have custom devices too.
> >
> > Anyways, we'll add more boards to the mainline kernel later on, but
> > first we have to get the the minimal omap3 support working with
> > mainline kernel.
> >
>
> I'm not really looking for OMAP35x EVM support in mainline, but in l-o
> git. And it seems like that's where it's not often mentioned/tested
> against - but beagle, zoom, overo are. In looking for 35x support, is
> it wrong to focus on l-o git instead of mainline? Won't support
> always be in l-o first?
beagle and overo runs with 35x processors. And evm development is going
just fine. git log arch/arm/mach-omap2/board-omap?evm.c will give you
only the board-file changes (not counting drivers).
--
balbi
next prev parent reply other threads:[~2008-10-04 20:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 12:09 [PATCH 0/0] Add minimal omap34xx support Tony Lindgren
2008-10-03 12:09 ` [PATCH 01/05] ARM: OMAP2: Add minimal omap3430 support Tony Lindgren
2008-10-03 12:09 ` [PATCH 02/05] ARM: OMAP3: Add minimal Beagle board support Tony Lindgren
2008-10-03 12:09 ` [PATCH 03/05] ARM: OMAP3: Add Beagle defconfig Tony Lindgren
2008-10-03 12:09 ` [PATCH 04/05] ARM: OMAP2: Add support for the Gumstix Overo board (rev 3) Tony Lindgren
2008-10-03 12:09 ` [PATCH 05/05] ARM: OMAP2: defconfig " Tony Lindgren
2008-10-03 12:50 ` [PATCH 04/05] ARM: OMAP2: Add support " Tony Lindgren
2008-10-06 14:38 ` Tony Lindgren
2008-10-08 8:21 ` [PATCH 03/05] ARM: OMAP3: Add Beagle defconfig, v2 Tony Lindgren
2008-10-09 14:51 ` [PATCH 02/05] ARM: OMAP3: Add minimal Beagle board support Russell King - ARM Linux
2008-10-10 8:51 ` Tony Lindgren
2008-10-05 8:01 ` [PATCH 01/05] ARM: OMAP2: Add minimal omap3430 support Tony Lindgren
2008-10-06 14:35 ` Tony Lindgren
2008-10-08 8:19 ` [PATCH 01/05] ARM: OMAP2: Add minimal omap3430 support, v2 Tony Lindgren
2008-10-09 14:47 ` [PATCH 01/05] ARM: OMAP2: Add minimal omap3430 support Russell King - ARM Linux
2008-10-09 15:09 ` Tony Lindgren
2008-10-03 15:52 ` [PATCH 0/0] Add minimal omap34xx support twebb
2008-10-04 7:05 ` Tony Lindgren
2008-10-04 12:42 ` twebb
2008-10-04 20:37 ` Felipe Balbi [this message]
2008-10-09 14:54 ` Russell King - ARM Linux
2008-10-09 15:17 ` Tony Lindgren
2008-10-10 7:32 ` Russell King - ARM Linux
2008-10-10 9:15 ` [PATCH] ARM: OMAP3: Add basic board support for OMAP LDP (Re: [PATCH 0/0] Add minimal omap34xx support) Tony Lindgren
2008-10-10 9:25 ` [PATCH] ARM: OMAP3: Add default kernel config " Tony Lindgren
2008-10-10 11:35 ` git pull request for minimal omap3 support one more time Tony Lindgren
2008-10-13 13:32 ` Russell King - ARM Linux
2008-10-14 17:19 ` Tony Lindgren
2008-10-14 18:51 ` Russell King - ARM Linux
2008-10-14 20:35 ` Tony Lindgren
2008-10-14 20:55 ` Tony Lindgren
2008-10-15 6:02 ` Jarkko Nikula
2008-10-15 18:34 ` Tony Lindgren
2008-10-08 7:50 ` git pull request for minimal omap3 support (Re: [PATCH 0/0] Add minimal omap34xx support) Tony Lindgren
2008-10-08 8:12 ` Tony Lindgren
2008-10-08 14:58 ` Tony Lindgren
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=20081004203700.GK10743@frodo \
--to=me@felipebalbi.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=taliaferro62@gmail.com \
--cc=tony@atomide.com \
/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).