[Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

[Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

[Charles Martel]

I noticed that BuildRoot will build a linux-2.6.36 kernel using default values. What is the procedure for building a custom build of the Linux kernel?
Specifically, BuildRoot builds SPI Drivers as modules (.ko) by default. I'd like to have the SPI Drivers built-in (Y instead of M) and also have the UserSpace SPIDEV built.
Can this be done from BuildRoot or must I rebuild the Linux kernel after building the BuildRoot filesystem?

Also, I had to modify the Makefile to not wipe out the Linux .config file when I execute "make clean". Is there a better way to store the customized values in Linux .config as part of the BuildRoot build configuration?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101108/fc65055d/attachment.html>

[Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

[Lionel Landwerlin]

Hello Charles,

From the buildroot configuration tool, in the kernel submenu, you can
select a "custom tarball" kernel (which might be a 2.6.36 in your
case) and also a "custom config file".

But if you're going to hack on your kernel, it make sense to make a
separate build.

Regards,

--
Lionel Landwerlin

On Mon, Nov 8, 2010 at 5:28 PM, Charles Martel <SingerIsland@gmx.com> wrote:
> I noticed that BuildRoot will build a linux-2.6.36 kernel using default
> values.? What is the procedure for building a custom build of the Linux
> kernel?
>
> Specifically, BuildRoot builds SPI Drivers as modules (.ko) by default.? I'd
> like to have the SPI Drivers built-in (Y instead of M) and also have the
> UserSpace SPIDEV built.
>
> Can this be done from BuildRoot or must I rebuild the Linux kernel after
> building the BuildRoot filesystem?
>
> Also, I had to modify the Makefile to not wipe out the Linux .config file
> when I execute "make clean".? Is there a better way to store the customized
> values in Linux .config as part of the BuildRoot build configuration?
>
> Thanks.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

[Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

[Thomas Petazzoni]

On Tue, 9 Nov 2010 17:45:40 +0100
Lionel Landwerlin <llandwerlin@gmail.com> wrote:

> From the buildroot configuration tool, in the kernel submenu, you can
> select a "custom tarball" kernel (which might be a 2.6.36 in your
> case) and also a "custom config file".

And to adjust the kernel configuration, you can do:

 make linux26-menuconfig

or

 make linux26-xconfig

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

[Charles Martel]

Thanks Thomas and Lionel.


----- Original Message -----
From: Thomas Petazzoni
Sent: 11/09/10 12:40 PM
To: buildroot at busybox.net
Subject: Re: [Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?

On Tue, 9 Nov 2010 17:45:40 +0100 Lionel Landwerlin <llandwerlin@gmail.com> wrote: > From the buildroot configuration tool, in the kernel submenu, you can > select a "custom tarball" kernel (which might be a 2.6.36 in your > case) and also a "custom config file". And to adjust the kernel configuration, you can do: make linux26-menuconfig or make linux26-xconfig Regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101122/e1d7199f/attachment.html>