All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Martel <SingerIsland@gmx.com>
To: buildroot@busybox.net
Subject: [Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot?
Date: Mon, 22 Nov 2010 10:28:40 -0500	[thread overview]
Message-ID: <20101122152841.117090@gmx.com> (raw)

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>

             reply	other threads:[~2010-11-22 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 15:28 Charles Martel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-08 16:28 [Buildroot] What is procedure for building custom Linux-2.6.36 from BuildRoot? Charles Martel
2010-11-09 16:45 ` Lionel Landwerlin
2010-11-09 17:40   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101122152841.117090@gmx.com \
    --to=singerisland@gmx.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.