Hello,
I just tested your kernel workflow
I have modified the em28xx-core.c file (in
kernel....drivers/media/video/em28xx/ )
after the -c compile and -c build, I see that the em28xx-core.o has not
been updated
finally, i ran the command bitbake -b linux-mainline_3.2.bb
compilation is not finished now, but as far as I see, the module (.ko)
is up to date
This solution seems to be working for what I need (module-only
recompilation)
Now, I will test your suggestions to reconfigure the kernel
Thanks to you all for your help !
Best Regards,
Chris
Le 22/05/2012 21:17, Bob Feretich a écrit :
I generally do my kernel builds in 3 steps (steps 3-5). (5 steps for
the first time)
The kernel is built when Angstrom builds, but sources are deleted. I
like the source available for examination and want to be able to
easily reconfigure the kernel.
1. bitbake -c clean virtual/kernel // ready OE to rebuild the
kernel
2. bitbake -f -c compile virtual/kernel // execute the OE build up to
the compile step
3. cd ....../git
make menuconfig // edit the kernel
configuration
4. bitbake -f -c compile virtual/kernel // force re-do of the compile
step with the new config settings
5. bitbake -c build virtual/kernel // execute the OE steps
after the compile, but don't erase
//
intermediate results (kernel sources)
With the intermediate results left intact, I can easily build driver
modules independently for testing.
bitbake -c build -b <my driver recipe .bb>
(Generates a .ko file that I can load with insmod.)
Regards,
Bob F.
On 5/22/2012 10:49 AM, Don deJuan wrote:
On 05/22/2012 10:41 AM, chrbruno wrote:
Thanks for your reply,
in fact, I use the virtual/kernel as a target
I don't know what name to provide for "YourModule"
The module I work on is driver/media/video/em28xx but "em28xx" is not
recognized as a target by bitbake
when I run a bitbake -c clean virtual/kernel, it removes all the kernel
and module sources (the source code I want to modify)
I think I will dig into the OE documentation !
or another approach would be to get the .config/patches from angstrom
tree, and compile a pure kernel using the classical "linux" method
Best Regards,
Chris
Le 22/05/2012 18:10, Don deJuan a écrit :
On 05/22/2012 06:08 AM, Gyorgy Kovesdi wrote:
On 2012 May 22 12:56:49 chrbruno wrote:
Hello (I'm new to angstrom),
I'm working on a kernel module on Beagleboard / Angstrom but I can't
find a way to modify and recompile it
I had similar problem: if you compile something like this:
$> bitbake your-module
then executing
$> bitbake your-module -c clean
theoretically would be enough for recompile it next time. But i found
this is not enough in
some cases (e.g. for kernel modules), i don't know why.
Try to clean the state cache this way:
$> rm build/sstate-cache/*your-module*
Hope this helps
K. Gy.
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
I could be wrong here but I believe if you use
bitbake -c cleansstate YourModule
Is the better way to clean the package. I was having issues just using
clean and no long do when I do the cleansstate.
HTH
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
When you are done modifying your code could you not just run
bitbake -f -c compile virtual/kernel ?
I have not messed with kernel modules other than changing the config.
By doing the -f -c compile , if I am correct should only force a
compile of virtual/kernel again leaving the modifications in place.
Hopefully a bitbake/OE master will chime in the actual proper
commands to do exactly what you wish.
HTH
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
