All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Krebs <Markus.Krebs@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug#897671: u-boot does not work on sheevaplug
Date: Wed, 9 May 2018 10:19:40 +0200	[thread overview]
Message-ID: <1d3d10ca-9256-6f36-2ba4-3c668a245a17@web.de> (raw)
In-Reply-To: <87efilookl.fsf@aikidev.net>

Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian:
> On 2018-05-08, Vagrant Cascadian wrote:
>> On 2018-05-05, Tom Rini wrote:
>>> On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote:
>>>> Markus Krebs discovered that the sheevaplug target has again grown and
>>>> installation overlaps where the u-boot env is saved since u-boot
>>>> ~2017.09. Running saveenv overwrites u-boot, and installing u-boot
>>>> overwrites any prior environment settings.
> ...
>>> I've added the maintainer to the list as well.  I would suggest looking
>>> for things to trim out, perhaps CMD_MEMTEST ?
>>
>> Thanks for the suggestsions. CMD_MEMTEST wasn't present, but disabling
>> EFI_LOADER made u-boot 2018.05 go from 592k down to 548k. There's not a
>> *lot* left to disable in the config, but that's a significant start...
> 
> And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it
> down to 432k! Thanks to beeble for the suggestion.
> 
> Anyone who has a sheevaplug can test that it actually boots with
> CONFIG_SYS_THUMB_BUILD=y enabled?

I could test it, but I don't know the config-file where I can change 
those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD).

  reply	other threads:[~2018-05-09  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <152540843251.13599.4428160353240912722.reportbug@server2.notar-krebs.de>
     [not found] ` <20180504104336.2n53z6or65rrjzrw@jirafa.cyrius.com>
     [not found]   ` <87muxfpgyq.fsf@aikidev.net>
     [not found]     ` <20180504171113.rsc4dzcnfnuesall@jirafa.cyrius.com>
     [not found]       ` <5411eb5c-e400-5bea-80bc-e231560ca76d@web.de>
     [not found]         ` <73c25c9a-faba-a7ea-4d3d-7e1fe932eda6@web.de>
     [not found]           ` <352dbeca-a872-de5f-60bf-d7a409cbecb8@web.de>
     [not found]             ` <20180505091354.abo3khggep6sa7jm@jirafa.cyrius.com>
     [not found]               ` <8afc29d1-8ae3-18e3-8bb9-22d13814efe4@web.de>
     [not found]                 ` <84c2c623-5d6d-e6fa-bc2b-b4082dca5dc2@web.de>
     [not found]                   ` <20180505183529.auxstq2qilg43ttm@jirafa.cyrius.com>
     [not found]                     ` <57d24e3c-aff7-ab81-c08a-a1362bc42ce2@web.de>
     [not found]                       ` <3ef09240-8cbe-3ad1-e070-9c4afd4cb1c0@web.de>
2018-05-05 23:04                         ` [U-Boot] Bug#897671: u-boot does not work on sheevaplug Vagrant Cascadian
2018-05-06  0:13                           ` Tom Rini
2018-05-06  7:00                             ` drEagle
2018-05-08 20:22                             ` Vagrant Cascadian
2018-05-08 20:54                               ` Vagrant Cascadian
2018-05-09  8:19                                 ` Markus Krebs [this message]
2018-05-09 12:33                                   ` klaus.goger at theobroma-systems.com
2018-05-09 15:35                                     ` Markus Krebs
2018-05-10 18:10                                       ` Vagrant Cascadian
2018-05-10 19:05                                         ` Markus Krebs

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=1d3d10ca-9256-6f36-2ba4-3c668a245a17@web.de \
    --to=markus.krebs@web.de \
    --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 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.