From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Elvis Dowson <elvis.dowson@mac.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
ext Tony Lindgren <tony@atomide.com>,
"Anders, David" <x0132446@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Add OMAP4 Panda support
Date: Fri, 18 Jun 2010 13:01:46 +0300 [thread overview]
Message-ID: <20100618100146.GT4237@nokia.com> (raw)
In-Reply-To: <64809C8C-FAB5-4540-A47A-B0967B5C3B7F@mac.com>
On Fri, Jun 18, 2010 at 11:56:02AM +0200, ext Elvis Dowson wrote:
>When adding support for OMAP4 Panda, and adding the necessary bits to
>omap3_defconfig, will it be possible to ensure that all OMAP3 devices
>also work the same, e.g. Gumstix Overo?
it should be possible. Ideally all omap2/3/4 boards should boot just
fine with omap3_defconfig.
>What about specifics to make Android work in the defconfigs?
I really don't think community should care about Android/MeeGo/Ubuntu
etc.
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-06-18 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 20:18 [PATCH] Add OMAP4 Panda support Anders, David
2010-05-18 3:36 ` Tony Lindgren
2010-06-18 6:58 ` Felipe Balbi
2010-06-18 8:17 ` Tony Lindgren
[not found] ` <64809C8C-FAB5-4540-A47A-B0967B5C3B7F@mac.com>
2010-06-18 10:01 ` Felipe Balbi [this message]
2010-06-18 14:32 ` Kevin Hilman
2010-06-18 14:57 ` Anders, David
2010-06-18 15:13 ` Kevin Hilman
2010-06-18 15:56 ` Anders, David
2010-06-18 16:06 ` Kevin Hilman
2010-06-18 15:26 ` Gadiyar, Anand
-- strict thread matches above, loose matches on Subject: below --
2010-06-24 19:33 [PATCH] Add OMAP4 Panda Support David Anders
2010-06-25 1:29 ` Gadiyar, Anand
2010-06-28 17:47 ` Anders, David
2010-07-05 11:51 ` Tony Lindgren
2010-07-06 16:05 ` Anders, David
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=20100618100146.GT4237@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=elvis.dowson@mac.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=x0132446@ti.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).