<div dir="ltr">Got ~<br><br>I'm testing the spi_s3c24xx_dma driver (from Ben Dooks)<br>Anyone doing the same thing?<br><br><div class="gmail_quote">2008/9/23 Andy Green <span dir="ltr"><<a href="mailto:andy@openmoko.com">andy@openmoko.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Somebody in the thread at some point said:<br>
</div><div class="Ih2E3d">| Another similar question，compile kernel with OE<br>
|<br>
| I want to try the recent kernel-2.6 (andy's branch), and apply my own<br>
| patches<br>
| so write a recipe, and put it on my own overlay repository, build with OE<br>
|<br>
| all I want to to test is a kernel module, while using OE, seems that It<br>
| will build all<br>
| kernel tree, every time it will untar, compile .... and this is really<br>
| time-consuming,<br>
| is it possible to compile the only module I want.<br>
|<br>
| Or should I use "the old fashioned way",<br>
|<br>
| Guess OE is more suitable for distro release<br>
<br>
</div>This is normal for packaging, it will cook the whole thing that way.<br>
It's generally what you want for packages and it proves that the set of<br>
sources is complete as well.<br>
<br>
If it doesn't make sense to add your module to the dist config (what's<br>
the module?) you best bet is build from git, that way most of the .o<br>
files won't need recooking between git pulls and it will be way faster<br>
for you.<br>
<div class="Ih2E3d"><br>
- -Andy<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: Using GnuPG with Fedora - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br>
</div>iEYEARECAAYFAkjYwFUACgkQOjLpvpq7dMqs/wCdEWN0rfx8XDUxfj/k09ymcIc5<br>
fHkAnjrKPqemb94kBAn4zhHU6p5FAahh<br>
=Mwoq<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div>