From: Eugene Surovegin <ebs@ebshome.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: 85xx FDT updates?
Date: Tue, 25 Apr 2006 10:08:57 -0700 [thread overview]
Message-ID: <20060425170857.GE20228@gate.ebshome.net> (raw)
In-Reply-To: <853005AF-8F43-454D-80E6-F39308F89A47@kernel.crashing.org>
On Tue, Apr 25, 2006 at 11:55:49AM -0500, Kumar Gala wrote:
>
> On Apr 25, 2006, at 11:49 AM, Dan Malek wrote:
>
> >
> >On Apr 25, 2006, at 3:49 AM, Eugene Surovegin wrote:
> >
> >>It seems some people here lost touch with reality - embedded Linux is
> >>mostly run on custom hardware, not on evaluation boards.
> >
> >This is the reason I usually mention such things. While we all
> >want to see the new features, we have to be sensitive to the
> >real world product deployment of Linux. While your world
> >may be a few evaluation boards that allow you to update
> >software many times a day, the real world products can't
> >afford to do that. From my own experience, I can tell you
> >that none of the deployed systems I've worked on will
> >ever update U-Boot. They consider this a sacred piece of
> >software such that is all else fails they can recover a
> >system remotely using U-Boot commands. They won't
> >risk updating U-Boot in case it fails. Making Linux dependent
> >on a particular, updated, version of U-Boot just isn't going
> >to work in most deployed systems. Or worse, making
> >Linux dependent on U-Boot isn't necessarily popular
> >either. For various reasons, especially when replacing
> >legacy software, some custom boot rom is often the
> >only choice.
>
> I understand this, however these systems are not in the kernel tree
> and thus we can only do so much for them. I agree a shim between a
> non-flat dev tree aware u-boot and kernel would be a good thing.
> However, I don't see that as something I have to produce as a board
> maintainer if I can give you and updated u-boot to use.
Kumar, you are missing our point. Let's say I packaged Motorola eval
board and sold it as my product. So, you have this board in the tree
but I cannot update firmware on this board. What you suggest I have to
do so my customer can run new kernel on it? Recall the board or fly
to the customer site with Abatron? This is just ridiculous.
--
Eugene
next prev parent reply other threads:[~2006-04-25 17:08 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 17:41 85xx FDT updates? Jon Loeliger
2006-04-24 19:04 ` Vitaly Bordug
2006-04-24 21:43 ` Kumar Gala
2006-04-24 22:31 ` Dan Malek
2006-04-25 6:08 ` Kumar Gala
2006-04-25 7:49 ` Eugene Surovegin
2006-04-25 14:05 ` Kumar Gala
2006-04-25 16:12 ` Eugene Surovegin
2006-04-25 16:25 ` Kumar Gala
2006-04-25 16:31 ` Eugene Surovegin
2006-04-25 16:51 ` Kumar Gala
2006-04-25 21:16 ` Wolfgang Denk
2006-04-25 21:19 ` Kumar Gala
2006-04-25 21:34 ` Wolfgang Denk
2006-04-25 16:49 ` Dan Malek
2006-04-25 16:55 ` Kumar Gala
2006-04-25 17:08 ` Eugene Surovegin [this message]
2006-04-25 17:39 ` Kumar Gala
2006-04-25 18:01 ` Eugene Surovegin
2006-04-25 18:14 ` Kumar Gala
2006-04-25 18:24 ` Eugene Surovegin
2006-04-25 18:29 ` Brent Cook
2006-04-25 18:33 ` Kumar Gala
2006-04-25 18:53 ` Eugene Surovegin
2006-04-25 19:20 ` Kumar Gala
2006-04-25 19:31 ` Eugene Surovegin
2006-04-25 19:41 ` Kumar Gala
2006-04-25 20:00 ` FT u-boot shim Kumar Gala
2006-04-25 21:30 ` Wolfgang Denk
2006-04-25 21:33 ` Kumar Gala
2006-04-25 21:39 ` Wolfgang Denk
2006-04-25 21:42 ` Kumar Gala
2006-04-25 22:28 ` Wolfgang Denk
2006-04-26 14:37 ` Kumar Gala
2006-04-26 19:19 ` Wolfgang Denk
2006-04-26 19:46 ` Geert Uytterhoeven
2006-04-27 18:18 ` Kumar Gala
2006-04-27 19:05 ` Wolfgang Denk
2006-04-27 19:20 ` Kumar Gala
2006-04-27 19:33 ` Jerry Van Baren
2006-04-27 19:42 ` [U-Boot-Users] " Kumar Gala
2006-04-27 19:43 ` Wolfgang Denk
2006-04-27 20:40 ` Jerry Van Baren
2006-04-27 21:25 ` Pantelis Antoniou
2006-04-27 19:40 ` Wolfgang Denk
2006-04-27 19:46 ` Kumar Gala
2006-04-27 19:59 ` Kumar Gala
2006-04-27 21:36 ` Wolfgang Denk
2006-04-27 21:55 ` [U-Boot-Users] " Tolunay Orkun
2006-04-25 21:33 ` Mark A. Greer
2006-04-25 21:38 ` Eugene Surovegin
2006-04-28 11:28 ` Paul Mackerras
2006-04-28 16:01 ` Kumar Gala
2006-04-28 19:11 ` Wolfgang Denk
2006-04-28 19:44 ` Tom Rini
2006-04-28 23:07 ` Wolfgang Denk
2006-04-28 23:22 ` Tom Rini
2006-04-29 0:32 ` Wolfgang Denk
2006-04-29 0:52 ` Tom Rini
2006-04-29 8:37 ` Wolfgang Denk
2006-04-29 15:33 ` Kumar Gala
2006-04-28 23:35 ` Paul Mackerras
2006-04-28 23:55 ` Wolfgang Denk
2006-04-28 19:52 ` Tom Rini
2006-04-25 18:48 ` 85xx FDT updates? Eugene Surovegin
2006-04-25 19:14 ` Andy Fleming
2006-04-25 19:22 ` Kumar Gala
2006-04-25 19:27 ` Eugene Surovegin
2006-04-25 19:58 ` Andy Fleming
2006-04-25 20:04 ` Eugene Surovegin
2006-04-25 21:29 ` Wolfgang Denk
2006-04-25 21:25 ` Wolfgang Denk
2006-04-25 18:31 ` Kumar Gala
2006-04-25 21:24 ` Wolfgang Denk
2006-04-25 21:32 ` Kumar Gala
2006-04-25 21:38 ` Wolfgang Denk
2006-04-25 21:22 ` Wolfgang Denk
2006-04-25 21:29 ` Kumar Gala
2006-04-25 21:36 ` Wolfgang Denk
2006-04-25 21:38 ` Kumar Gala
2006-04-25 22:22 ` Wolfgang Denk
2006-04-26 23:27 ` Dan Malek
2006-04-25 21:09 ` Wolfgang Denk
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=20060425170857.GE20228@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).