From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: AMCC 440EP phy detection
Date: Wed, 08 Apr 2009 11:35:23 -0700 [thread overview]
Message-ID: <49DCEE6B.7010704@embeddedarm.com> (raw)
In-Reply-To: <200904082019.06889.sr@denx.de>
Stefan,
> Ack. We usually do all this setup in U-Boot. But as I understand Eddie, he is
> using a custom bootloader.
Correct, I'll put this code in the platform initialization. Thanks for the
suggestions everyone.
> Eddie, btw: Why are you not using U-Boot?
At Technologic Systems, one of our design goals for all of our products is to
achieve a very quick boot time(under 2 seconds to a shell prompt). We then
provide a user space utility to boot another linux kernel, this allows our
customers to use Linux as a bootloader. We boot to an initial ramdisk then use a
linuxrc script as a replacement for a typical bootloader(e.g. U-Boot). In the
background we can then mount a large filesystem with Debian installed. In my
opinion it works out quite nicely in that one can use our boards as more of an
appliance(apply power and it's on, rather than waiting for a computer to boot).
--
Best Regards,
________________________________________________________________
Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
16525 East Laser Drive | fax: (480) 837-5300
Fountain Hills, AZ 85268 | web: www.embeddedARM.com
prev parent reply other threads:[~2009-04-08 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 16:32 AMCC 440EP phy detection Eddie Dawydiuk
2009-04-07 16:47 ` Feng Kan
2009-04-07 18:20 ` Eddie Dawydiuk
2009-04-07 17:11 ` Grant Likely
2009-04-07 17:18 ` Stefan Roese
2009-04-08 0:10 ` Eddie Dawydiuk
2009-04-08 15:47 ` Eddie Dawydiuk
2009-04-08 16:01 ` Stefan Roese
2009-04-08 17:00 ` Grant Likely
2009-04-08 18:19 ` Stefan Roese
2009-04-08 18:35 ` Eddie Dawydiuk [this message]
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=49DCEE6B.7010704@embeddedarm.com \
--to=eddie@embeddedarm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@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;
as well as URLs for NNTP newsgroup(s).