Oops, maybe this link is better:
http://pokylinux.org/doc/poky-handbook.html#ref-bitbake-providers
/d
________________________________________________________________________
Daniel Packard
RoadNarrows Robotics
daniel@...
http://www.roadnarrows.com
On Tue, 2011-11-08 at 10:05 -0700, Daniel Packard wrote:
> Hi Giovanni,
>
> We discovered a way to do this (i.e. compile our omap3-console-image
> against a custom kernel version) just a couple weeks ago.
>
> If several bitbake recipes provide the same item (e.g. virtual/kernel),
> there are a couple ways to influence which recipe is actually used by
> bitbake whenever that item is used (e.g. when compiling the kernel
> modules or omap3-console-image)
>
> In your configuration files (overo.conf, local.conf, etc.), you can set:
> PREFERRED_PROVIDER_virtual/kernel
> and PREFERRED_VERSION_virtual/kernel
>
> for example, setting
> PREFERRED_PROVIDER_virtual/kernel = "linux-omap3"
> PREFERRED_VERSION_virtual/kernel = "2.6.34"
>
> would force bitbake to use "linux-omap3_2.6.34.bb" as the default kernel
> recipe when running `bitake omap3-console-image`
>
> If you have a kernel recipe that doesn't fit this naming convention, you
> can force bitbake to use it as the default provider of virtual/kernel.
> Instead of setting "PREFERRED_VERSION_virtual/kernel" in your
> configuration files, define a Default Preference (DP) variable inside
> your preferred kernel recipe, and set it to some positive value.
>
> e.g. inside "linux-omap3_2.6.34-my_custom_kernel.bb", set:
> DP=1
>
> Bitbake will use the recipe with the highest DP (which is 0 by default)
>
> There's some more info in the poky-handbook:
> http://pokylinux.org/doc/poky-handbook.html#var-DEFAULT_PREFERENCE
>
> Best luck!
>
> /d
>
> ________________________________________________________________________
> Daniel Packard
> RoadNarrows Robotics
> daniel@...
> http://www.roadnarrows.com
>
>
> On Mon, 2011-11-07 at 00:37 -0800, Giovanni C wrote:
> > Hi,
> > by following the procedures described on Scott Ellis' Web Site, I was able
> > to manual compile
> > kernel and U-boot.
> >
> > So now I have three kind of files:
> >
> > 1) uImage
> > 2) kernel modules
> > 3) uboot
> >
> > While I know how to install uImage and uboot, I do not know ho to prepare a
> > omap3-console-image
> > containing the manual compiled kernel modules.
> >
> > Could you please tell me where to place the manual compiled kernel files,
> > inside the openembedded three
> > in order to make them included in the bitbake omap3-console-image process?
> >
> > Otherwise, how can I manual install those kernel modules?
> >
> > Thanks in advance.
> > -g
> >
>
>
|