Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] target/ cleanup status
Date: Sun, 4 Apr 2010 17:30:35 +0200	[thread overview]
Message-ID: <20100404173035.44e611d0@surf> (raw)

Hello,

I've made some progress in the cleanup of the target/ directory. Not
everything is completed, but I thought it might be good to try to merge
what's already been done before going on with the remaining work. I
already have 83 patches and I don't think it's good to keep more
patches unmerged.

So far, what I've done is :

 * Cleanup all the root filesystem generation code
   ===============================================

   All the details have been given in
   http://lists.busybox.net/pipermail/buildroot/2010-March/032841.html.
   No major change has been made here, except a few minor fixes here
   and there. The latest version is available at
   http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=fs-cleanup.

 * Cleanup all the bootloader compilation code
   ===========================================

   The code is available at
   http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=bootloaders-cleanup.
   This branch is based on the previous fs-cleanup branch.

    - Instead of spreading all bootloader's code in various directories
      in target/, it is now gathered in a boot/ directory

    - In terms of configuration, a new top-level configuration item is
      available to configure bootloaders, instead of hiding them in
      "Target filesystem support"

    - Support for yaboot has been removed.

    - Support for U-Boot has been considerably simplified, with much
      fewer configuration options. I'd appreciate if people using the
      removed options could tell us why they are useful in their
      projects.

    - Support for grub, grub2 and syslinux has been slightly
      cleaned-up. More work is needed on grub2 to make it really useful.

 * Cleanup the makedevs compilation code
   =====================================

   The code is available at
   http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=makedevs-cleanup.
   This branch is based on the previous bootloaders-cleanup branch.

   This tool was compiled in target/makedevs/, it is now moved to
   package/makedevs/. Unfortunately, since the source is directly
   included into Buildroot, we cannot use the generic package
   infrastructure, so we still rely on a manual Makefile.

 * Cleanup the Linux kernel building code
   ======================================

   The code is available at
   http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=linux-cleanup.
   This branch is based on the previous makedevs-cleanup branch.

   We introduce a totally new and very simplified infrastructure for
   building the Linux kernel. We just allow configuration for:

    - kernel version : either latest stable, custom stable or custom
      tarball URL
    - kernel patch : location of local patch file, local patch
      directory or remote (http/ftp) patch file
    - kernel configuration : either a defconfig, or a custom .config
    - kernel image: either uImage, zImage, bzImage or vmlinux

There are for sure many remaining issues, but I can't test all cases
and I don't know which configurations are being used today by users.
Considering the fact that we are two months from the release (leaving
some time to fix issues), I'd like these patches to be considered for
inclusion. If so, I'll gladly send an official pull request, with all
patches sent to the list.

I'm of course ready to rework the patch set with your comments,
feedback and bug reports.

Thanks!

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

                 reply	other threads:[~2010-04-04 15:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100404173035.44e611d0@surf \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox