From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <me@felipebalbi.com>
Cc: 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 16:25:06 -0700 [thread overview]
Message-ID: <20080916232505.GC25885@atomide.com> (raw)
In-Reply-To: <20080916184110.GA10733@frodo>
* Felipe Balbi <me@felipebalbi.com> [080916 11:42]:
> On Tue, Sep 16, 2008 at 09:13:21AM -0600, Paul Walmsley wrote:
> > On Tue, 16 Sep 2008, Kalle Valo wrote:
> >
> > > Hello Linux OMAP community,
> > >
> > > I have seen a lot of patches going to Russell and general talk about
> > > mainline support. What is actually the current situation? Is there
> > > hope to have good support in mainline soon? If yes, when?
> > >
> > > Unsurprisingly I'm especially interested about N800/N810 support :)
> >
> > Parts of N800/N810 are still broken in linux-omap tree. At least sound
> > did not work as of early September, and MMC still emits errors as
> > described in:
> >
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg02499.html
> >
> > Don't recall what the current LM8323 status is.
>
> Bluetooth is also missing on mainline, but the driver needs some rework.
Hopefully we'll get all core 24xx and 34xx files integrated soon. But
then there are tons of board-*.c files missing from mainline that
probably need to be cleaned up a bit.
Tony
next prev parent reply other threads:[~2008-09-16 23:25 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 [this message]
2008-09-17 5:20 ` Jarkko Nikula
2008-09-17 5:55 ` David Brownell
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=20080916232505.GC25885@atomide.com \
--to=tony@atomide.com \
--cc=kalle.valo@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=paul@pwsan.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