From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] omap3/powervr-drivers: Cleanups & fixes
Date: Tue, 20 Jul 2010 20:46:31 +0200 [thread overview]
Message-ID: <i24qu7$qc6$2@dough.gmane.org> (raw)
In-Reply-To: <201007201944.05812.schnitzeltony@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20-07-10 19:44, Andreas Mueller wrote:
>> It's not missing, it's present in all omap3 kernels in .dev that are
>> supported. This incarnation of the test wasn't accepted upstream, but
>> it's easy enough to patch in.
> All the guys sitting on the gumstix tree like me are missing it. The latest driver is simply diabled with a commit msg. like 'does not build for kernel > 2.6.32'
And there's your problem, you're using some unsupported crazy vendor
branch. If you build from .dev, you'll get a perfectly working 2.6.32
kernel with support for cpufreq, cpuidle, latest sgx drivers, dsp
support, etc. I use it on all my overos daily.
I see zero gain in uglifying the current recipe to support crazy vendor
branches that will never get merged. Time is better spent on getting
those vender changes upstream first.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMRe8HMkyGM64RGpERAgyQAJoD6BrNE/GXQTBnRqOnTuNgIPwOwQCfcwgW
3HgBIj7R8MngEviSwoK5IV4=
=Afz0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-20 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 14:54 [PATCH] omap3/powervr-drivers: Cleanups & fixes Andreas Mueller
2010-07-20 17:04 ` Koen Kooi
2010-07-20 17:44 ` Andreas Mueller
2010-07-20 18:46 ` Koen Kooi [this message]
2010-07-20 20:53 ` Frans Meulenbroeks
2010-07-20 22:33 ` Andreas Mueller
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='i24qu7$qc6$2@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/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