public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Newbie help] Motorola Board with GT64260
Date: Mon, 03 May 2004 11:46:14 +0200	[thread overview]
Message-ID: <409614E6.6050602@fh-landshut.de> (raw)
In-Reply-To: <5.1.0.14.2.20040502213935.0129c038@pop3.ttlc.net>

Mike McCullough wrote:
>>
>> BTW: MCC Systems sells a "Linux SDK" which includes a port of U-Boot
>> to the MVME5500 board (see http://www.mccengineering.com/linuxsdks.htm)
> 
> 
> Actually, MCC does NOT have a port of U-boot to the Motorola 5500 board 
> as we used the onboard MOTload software instead. Since MOTLoad worked 
> just fine for us (once we figured it out) we didn't do the U-Boot port.
> 

MotLoad actually netboots fine, but AFAIK it doesn't boot from flash (a 
capability I already have gladly exploited with the MVME2100 and the 
PPCbug). While it seems that a lot of setups often seem to be perfectly 
ok with a netboot (which seems to be very popular with VxWorks as well), 
for my setup a flash boot setup would really be the better choice - 
especially since on the MVME5500 flash is an abundant resource: 32-40MB 
are more than enough for a really nice root filesystem, don't you think? 
(I've not even ran out of the 4MB on the MVME2100 by now - thanks, 
uClibc and BusyBox!!!)

>> Maybe we should start a "black list"  of  companies  who  don't  give
>> their patches back to the public source tree.
> 
> Well, everything that we list on our Web site is freely available. You 
> just have to do the same amount of hunting (and integration!) that MCC did.
> 
> I'm not fond of black-listing myself. Isn't that what big companies do??
> 

Well, as long as the Linux vendors either hide their Linux kernels, or 
release only trimmed down versions of them (and no patchset), I guess 
the bootloader is not the worst problem - ok, ok, of course to people on 
this list this is actually an issue at heart!! But with all the closed 
mailing lists, and proprietary patchsets for customers only, open-source 
projects seem to be pretty much to be on the exploited side of the deal 
to me. :(

This is of course a general comment, and not about your special SDK 
vendor, which I have no experience with yet!

Thanks, and with kind regards,
Oliver Korpilla

  reply	other threads:[~2004-05-03  9:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 21:17 [U-Boot-Users] Configuration System Jon Loeliger
2004-04-29 22:14 ` Wolfgang Denk
2004-04-30  5:31   ` Robert Schwebel
2004-04-30 15:07     ` Sam Ravnborg
2004-04-30 15:39       ` Wolfgang Denk
2004-04-30 16:00         ` Sam Ravnborg
2004-04-30 16:18           ` Wolfgang Denk
2004-04-30 16:05         ` Jon Loeliger
2004-04-30 16:31           ` Wolfgang Denk
2004-04-30 22:24             ` Jon Loeliger
2004-04-30 23:19               ` Wolfgang Denk
2004-05-03 11:05                 ` Brian Waite
2004-05-03 20:12                   ` Wolfgang Denk
2004-04-30 21:46           ` Sam Ravnborg
2004-05-03 11:18         ` [U-Boot-Users] [Newbie help] Motorola Board with GT64260 Oliver Korpilla
2004-05-02 10:45           ` Wolfgang Denk
2004-05-03  1:46             ` Mike McCullough
2004-05-03  9:46               ` Oliver Korpilla [this message]
2004-05-03 10:23               ` 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=409614E6.6050602@fh-landshut.de \
    --to=okorpil@fh-landshut.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox