From: Tony Lindgren <tony@atomide.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: Jarkko Nikula <jarkko.nikula@nokia.com>,
Felipe Balbi <me@felipebalbi.com>, Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org
Subject: Re: OMAP support in mainline?
Date: Wed, 17 Sep 2008 09:53:51 -0700 [thread overview]
Message-ID: <20080917165350.GF25885@atomide.com> (raw)
In-Reply-To: <87y71rqo43.fsf@nokia.com>
* Kalle Valo <kalle.valo@nokia.com> [080916 23:32]:
> Jarkko Nikula <jarkko.nikula@nokia.com> writes:
>
> > On Tue, 16 Sep 2008 16:25:06 -0700
> > "ext Tony Lindgren" <tony@atomide.com> wrote:
> >
> >> 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.
> >>
> > I think one good measure for this whole work when one can can run
> > Beagle or Overo with mainline kernel.
>
> I really would like to run N800/N810 with mainline kernel (ie. with
> Linus' tree), at least get it booting. For example, sound and
> bluetooth are not that important for me right now. What kind of
> cleanup is needed for that?
Well here are few things that come to mind for N8X0:
- drivers/cbus needs to be cleaned and submitted via LKML
- arch/arm/mach-omap2/board-n800*.c maybe should be called board-n8x0*.c
instead?
- blizzard_enable_clocks() needs to create a virtual clock so that
drivers/video/omap/ can just call clk_enable/disable(). Other board
files may need this done too, at least nokia770*.c has the same
problem
Regards,
Tony
next prev parent reply other threads:[~2008-09-17 16:53 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
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 [this message]
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=20080917165350.GF25885@atomide.com \
--to=tony@atomide.com \
--cc=jarkko.nikula@nokia.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