From: David Brownell <david-b@pacbell.net>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: Trilok Soni <soni.trilok@gmail.com>,
"Smith, Stephen" <smsmith@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP Zoom kernel ALSA build problem
Date: Thu, 4 Dec 2008 11:03:08 -0800 [thread overview]
Message-ID: <200812041103.09366.david-b@pacbell.net> (raw)
In-Reply-To: <BD771A35-18A7-41C7-80F5-0BC59D77597C@student.utwente.nl>
On Thursday 04 December 2008, Koen Kooi wrote:
> >>> Perhaps that kernel should sync with newer code?
>
> The rest
> of the beagleboards peeps wants to get things as fast as possible into
> mainline instead of wanting awesomely good powermanagement.
Bull hockey ... they want *BOTH* mainline support and good PM. :)
PM support is still cooking. Support for other OMAP goodness
can -- and does! -- evolve in parallel.
Having a ZOOM fork to help roll goodies out of TI-internal trees
into mainline is fine -- TI has OMAP hardware for a long time before
the chips go public -- but the goal should be to *help* and that means
both (a) tracking mainline, probably via linux-omap, and (b) pushing
goodies out of that ZOOM fork so they're more broadly available.
So for example the NAND acceleration stuff seems to have gone
nowhere ... while that ZOOM fork may have some updates, they've not
gotten into the main OMAP tree, or into mainline.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-04 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 15:38 OMAP Zoom kernel ALSA build problem Smith, Stephen
2008-12-04 17:40 ` David Brownell
2008-12-04 17:51 ` Trilok Soni
2008-12-04 18:25 ` Koen Kooi
2008-12-04 18:30 ` Koen Kooi
2008-12-04 19:03 ` David Brownell [this message]
2008-12-04 22:38 ` Tony Lindgren
2008-12-05 23:35 ` David Brownell
2008-12-06 1:26 ` 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=200812041103.09366.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
--cc=smsmith@ti.com \
--cc=soni.trilok@gmail.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