public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] openrd: Once again shrink binary size
Date: Wed, 1 Aug 2018 07:18:50 -0400	[thread overview]
Message-ID: <20180801111850.GS32145@bill-the-cat> (raw)
In-Reply-To: <CAFOYHZC=HWgrJTys9cBNpUO5eac6ife=5BvHh47KRvUaRR=Pbg@mail.gmail.com>

On Wed, Aug 01, 2018 at 08:40:18PM +1200, Chris Packham wrote:

> On Fri, Jul 27, 2018 at 11:59 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > With some recent changes to relevant drivers here the openrd board
> > (openrd_client in this case) does not fit within its size constraint.
> > We can however drop the slightly extended baudrate table and then the
> > duplication of mtdparts/mtdids in the default environment.  These
> > defaults are set in the environment by the 'mtdparts' command and
> > otherwise referenced throughout the code.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> 
> We could probably shrink things further by disabling jffs2 and only
> supporting ubifs. Similarly having support for both fat and ext4 is
> taking up much of the image although it may be less desirable to pick
> only one of these since either of those file systems could be on
> removable media.

Ah, so, did you also see my email marking the platforms as orphaned?  If
so, please feel free to pick them up and trim the config down :)
Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180801/bdf91f23/attachment.sig>

  reply	other threads:[~2018-08-01 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 11:59 [U-Boot] [PATCH] openrd: Once again shrink binary size Tom Rini
2018-07-27 17:09 ` Tom Rini
2018-08-01  8:40 ` Chris Packham
2018-08-01 11:18   ` Tom Rini [this message]
2018-08-02  8:59     ` Chris Packham

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=20180801111850.GS32145@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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