Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:	trunk/buildroot/target/u-boot/2009.01-rc1
Date: Tue, 06 Jan 2009 17:03:32 +0100	[thread overview]
Message-ID: <1231257812.32308.156.camel@elrond.atmel.com> (raw)
In-Reply-To: <87zli4o3mj.fsf@macbook.be.48ers.dk>

tis 2009-01-06 klockan 16:28 +0100 skrev Peter Korsgaard:
> >>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
> 
>  ulf> Provide factory default command to u-boot, using Buildroot variables
>  >> 
>  ulf> Added:
>  ulf> trunk/buildroot/target/u-boot/2009.01-rc1/u-boot-2009.01-rc1-009-factory.patch
>  >> 
>  >> Do we really need this? What's the upstream status of it?
> 
>  Ulf> I find that this patch reduces maintenance A LOT.
>  Ulf> If someone calls in with a problem loading linux,
>  Ulf> then you tell them to do "factory"  and then 
>  Ulf> everything is SO much easier.
> 
> But what's the difference between this command and a factory
> environment variable which just erases your environment and resets the
> board?
> 

It sets up a number of environment variables,
depending on the buildroot configuration for u-boot.


> If you really need it for Atmel stuff, maybe you should keep it in the
> Atmel fork?
> 

I think beeing able to reset the environment to a known 
board specific default is useful for everyone.
If it is available for PCs, why is it a bad idea for U-boot?
That does not mean that there is no room for improvement
on the actual implementation.

You have to explicitly enable this in your board config,
so noone should be hurt by the patch.


The plan is to remove the Atmel specific U-Boot soon.
(It is already removed from Kconfig)

BR
Ulf Samuelsson

  reply	other threads:[~2009-01-06 16:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  0:04 [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1 ulf at uclibc.org
2009-01-06 14:39 ` Peter Korsgaard
2009-01-06 15:20   ` Ulf Samuelsson
2009-01-06 15:28     ` Peter Korsgaard
2009-01-06 16:03       ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:33 ` Peter Korsgaard
2009-01-06 16:21 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:32 ` Peter Korsgaard
2009-01-06 16:13 ulf at uclibc.org
2009-01-06 16:10 ulf at uclibc.org
2009-01-06 16:09 ulf at uclibc.org
2009-01-03  0:06 ulf at uclibc.org
2009-01-06 14:37 ` Peter Korsgaard
2009-01-06 15:16   ` Ulf Samuelsson
2009-01-06 15:26     ` Peter Korsgaard
2009-01-06 15:56       ` Ulf Samuelsson
2009-01-06 16:18         ` Peter Korsgaard
2009-01-06 17:22           ` Ulf Samuelsson
2009-01-06 18:13             ` Peter Korsgaard
2009-01-03  0:05 ulf at uclibc.org
2009-01-03  0:04 ulf at uclibc.org
2009-01-03  0:03 ulf at uclibc.org

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=1231257812.32308.156.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.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