From: David Brownell <david-b@pacbell.net>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: ext Tony Lindgren <tony@atomide.com>,
Felipe Balbi <me@felipebalbi.com>, Paul Walmsley <paul@pwsan.com>,
Kalle Valo <kalle.valo@nokia.com>,
linux-omap@vger.kernel.org
Subject: Re: OMAP support in mainline?
Date: Tue, 16 Sep 2008 22:55:00 -0700 [thread overview]
Message-ID: <200809162255.00918.david-b@pacbell.net> (raw)
In-Reply-To: <20080917082043.04c94e2d.jarkko.nikula@nokia.com>
On Tuesday 16 September 2008, Jarkko Nikula wrote:
>
> I think one good measure for this whole work when one can can run
> Beagle or Overo with mainline kernel.
Yes ... ideally for 2.6.28 for both. The Overo boards handed
out at the kernel summit are a bit visible right now as not
yet booting with mainline code. :)
> That would require some "spring-cleaning" effort and getting core,
> TWL4030, etc. patches out but then it is much more easier to send
> remaining board files and other drivers to their relevant lists.
My quick audit:
- core updates
- board files
- twl4030 ... converted to new-style, gpiolib, drivers/mfd
- hsmmc
- omap2 nand
- various pending musb updates
FB support would be nice too, but IMO not if that means rushing
the updates discussed lately. Not all the TWL components would
need to go upstream at once.
- Dave
next prev parent reply other threads:[~2008-09-17 5:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 14:56 OMAP support in mainline? Kalle Valo
2008-09-16 15:13 ` Paul Walmsley
2008-09-16 18:41 ` Felipe Balbi
2008-09-16 23:25 ` Tony Lindgren
2008-09-17 5:20 ` Jarkko Nikula
2008-09-17 5:55 ` David Brownell [this message]
2008-09-17 7:16 ` Koen Kooi
2008-09-17 12:24 ` Steve Sakoman
2008-09-17 13:23 ` Koen Kooi
2008-09-18 9:55 ` Felipe Balbi
2008-09-18 10:00 ` Pandita, Vikram
2008-09-18 11:16 ` Koen Kooi
2008-09-18 11:24 ` Felipe Balbi
2008-09-18 11:51 ` Pandita, Vikram
2008-09-18 11:53 ` Igor Stoppa
2008-09-18 12:01 ` Pandita, Vikram
2008-09-18 13:36 ` Woodruff, Richard
2008-09-18 16:46 ` David Brownell
2008-09-19 8:49 ` Igor Stoppa
2008-09-19 13:50 ` Woodruff, Richard
2008-09-21 15:02 ` Felipe Contreras
2008-09-21 16:34 ` Woodruff, Richard
2008-09-18 16:31 ` David Brownell
2008-09-19 14:07 ` Koen Kooi
2008-09-19 16:09 ` MUSB not workin in .27rc6, was: " Koen Kooi
2008-09-19 21:24 ` Felipe Balbi
2008-09-19 21:34 ` Koen Kooi
2008-09-19 21:47 ` Felipe Balbi
2008-09-20 0:49 ` David Brownell
2008-09-20 1:12 ` Felipe Balbi
2008-09-20 1:48 ` Måns Rullgård
2008-09-19 19:10 ` Philip Balister
2008-09-19 20:57 ` Ashwin Bihari
2008-09-19 21:02 ` Koen Kooi
2008-09-17 6:32 ` Kalle Valo
2008-09-17 16:53 ` Tony Lindgren
2008-09-17 16:57 ` Tony Lindgren
2008-09-17 20:32 ` Russell King - ARM Linux
2008-09-21 18:42 ` Tony Lindgren
2008-09-21 18:51 ` Russell King - ARM Linux
2008-09-21 19:04 ` Tony Lindgren
2008-09-17 6:18 ` Budhee Jamaich
-- strict thread matches above, loose matches on Subject: below --
2008-10-03 7:20 Nathan Monson
2008-10-03 7:52 ` Felipe Balbi
2008-10-03 8:36 ` David Brownell
2008-10-04 1:23 ` Nathan Monson
2008-10-04 1:40 ` David Brownell
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=200809162255.00918.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=jarkko.nikula@nokia.com \
--cc=kalle.valo@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=paul@pwsan.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