All of lore.kernel.org
 help / color / mirror / Atom feed
* Using openembedded with externally built kernel
@ 2014-03-12 13:48 Carlos Rafael Giani
  2014-03-13 11:56 ` Diego Sueiro
  0 siblings, 1 reply; 3+ messages in thread
From: Carlos Rafael Giani @ 2014-03-12 13:48 UTC (permalink / raw)
  To: openembedded-devel

I have a platform with a very barebones BSP that builds and patches a 
2.6 kernel using a whole lot of shell scripts and patch files.
Integrating this build process into a .bb file is too complicated at the 
moment.

Since cross compiling all packages I need is a nightmare to do manually, 
I wonder if I can get OE to use the prebuilt kernel along with
its kernel modules and headers instead of trying to build a new kernel. 
Ideally, I would just tell it where the kernel headers are, where
the uImage is, and where the modules are. I imagine this as some kind of 
kernel .bb file setting things up to not actually build anything.

My question is: is this possible? All I could find was about external 
toolchains and external kernel modules.

Carlos


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Using openembedded with externally built kernel
  2014-03-12 13:48 Using openembedded with externally built kernel Carlos Rafael Giani
@ 2014-03-13 11:56 ` Diego Sueiro
  2014-03-13 17:36   ` Philip Balister
  0 siblings, 1 reply; 3+ messages in thread
From: Diego Sueiro @ 2014-03-13 11:56 UTC (permalink / raw)
  To: openembedded-devel

On Wed, Mar 12, 2014 at 10:48 AM, Carlos Rafael Giani <dv@pseudoterminal.org
> wrote:

> I have a platform with a very barebones BSP that builds and patches a 2.6
> kernel using a whole lot of shell scripts and patch files.
> Integrating this build process into a .bb file is too complicated at the
> moment.
>
> Since cross compiling all packages I need is a nightmare to do manually, I
> wonder if I can get OE to use the prebuilt kernel along with
> its kernel modules and headers instead of trying to build a new kernel.
> Ideally, I would just tell it where the kernel headers are, where
> the uImage is, and where the modules are. I imagine this as some kind of
> kernel .bb file setting things up to not actually build anything.
>
> My question is: is this possible? All I could find was about external
> toolchains and external kernel modules.
>

I believe that you have to wright your own recipe with custom do_compile,
do_install etc functions.



Abraços,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Using openembedded with externally built kernel
  2014-03-13 11:56 ` Diego Sueiro
@ 2014-03-13 17:36   ` Philip Balister
  0 siblings, 0 replies; 3+ messages in thread
From: Philip Balister @ 2014-03-13 17:36 UTC (permalink / raw)
  To: openembedded-devel

On 03/13/2014 12:56 PM, Diego Sueiro wrote:
> On Wed, Mar 12, 2014 at 10:48 AM, Carlos Rafael Giani <dv@pseudoterminal.org
>> wrote:
> 
>> I have a platform with a very barebones BSP that builds and patches a 2.6
>> kernel using a whole lot of shell scripts and patch files.
>> Integrating this build process into a .bb file is too complicated at the
>> moment.
>>
>> Since cross compiling all packages I need is a nightmare to do manually, I
>> wonder if I can get OE to use the prebuilt kernel along with
>> its kernel modules and headers instead of trying to build a new kernel.
>> Ideally, I would just tell it where the kernel headers are, where
>> the uImage is, and where the modules are. I imagine this as some kind of
>> kernel .bb file setting things up to not actually build anything.
>>
>> My question is: is this possible? All I could find was about external
>> toolchains and external kernel modules.
>>
> 
> I believe that you have to wright your own recipe with custom do_compile,
> do_install etc functions.

Write a recipe that "installs" the pre-built kernel and a tarball of
modules and commit the binary kernel and modules into the bsp layer.
Yeah, this is hacky, but does give you some repeatibility.

Philip

> 
> 
> 
> Abraços,
> 
> --
> *dS
> Diego Sueiro
> 
> Administrador do Embarcados
> www.embarcados.com.br<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
> 
> /*long live rock 'n roll*/
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-03-13 17:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-12 13:48 Using openembedded with externally built kernel Carlos Rafael Giani
2014-03-13 11:56 ` Diego Sueiro
2014-03-13 17:36   ` Philip Balister

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.