Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Tom Rini <trini@konsulko.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: add devmem
Date: Thu, 31 Jan 2019 21:04:53 +0200	[thread overview]
Message-ID: <20190131190453.GD28875@localhost> (raw)
In-Reply-To: <20190130224703.GO30838@bill-the-cat>

On Wed, Jan 30, 2019 at 05:47:03PM -0500, Tom Rini wrote:
> 
> I would also ask if we should be enabling more stuff in busybox, period.

I don't think the current status quo would be a good starting point for that.

Before submitting I saw CONFIG_PATCH=y, which is a lot more of a
"Why would I ever need this on an embedded device?".

Not saying that you are wrong, but the starting point should be a review
of the current config.

> Customizing busybox for what you're trying to _do_ with a custom setup
> is one of those top 5 TODO items with making a cut down image and
> customizing the kernel config.  Outside of -tiny and initramfs/similar
> cases, there's not a great reason to use
> almost-but-not-quite-complete-busybox-applet compared with the regular
> app.

I frequently end up in projects where I do have great reason for that:

For root filesystems of the 32-64 MB size it is not necessary to use a 
different libc or use -Os, but using the busybox applets when they are 
sufficient saves > 10% filesystem size compared to the full versions.

E.g. 0.45 MB for a standalone tar is much when the little functionality 
you actually need is also provided by the busybox applet.

Plus there is also the convenience point that most of the tools you need 
are already installed just by adding busybox with the default config.

> Tom

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-01-31 19:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  9:34 [PATCH] busybox: add devmem Adrian Bunk
2019-01-30 16:50 ` Khem Raj
2019-01-30 19:47   ` Andre McCurdy
2019-01-30 20:01     ` Khem Raj
2019-01-30 20:09     ` Scott Ellis
2019-01-31 10:09       ` Philip Balister
2019-01-31 12:14         ` Leon Woestenberg
2019-01-30 20:31   ` Adrian Bunk
2019-01-30 22:18     ` Khem Raj
2019-01-30 22:31       ` Richard Purdie
2019-01-30 22:44         ` Leon Woestenberg
2019-01-30 22:47         ` Tom Rini
2019-01-31 19:04           ` Adrian Bunk [this message]
2019-01-31 19:58             ` Tom Rini
2019-01-31 18:26       ` Adrian Bunk
2019-01-31 10:06   ` Philip Balister
2019-01-31 18:14     ` Adrian Bunk

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=20190131190453.GD28875@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=trini@konsulko.com \
    /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