From: Wolfgang Denk <wd@denx.de>
To: "Brian Padalino" <bpadalino@perigee.com>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: U-Boot, tftp and PCI ethernet
Date: Fri, 25 Jul 2003 15:14:43 +0200 [thread overview]
Message-ID: <20030725131448.E7A9AC602D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 25 Jul 2003 08:10:49 EDT." <DGEEIPOFGGPOACEFBGGCGEJFCAAA.bpadalino@perigee.com>
In message <DGEEIPOFGGPOACEFBGGCGEJFCAAA.bpadalino@perigee.com> you wrote:
>
> Does U-Boot support booting over ethernet controllers found on the PCI bus,
Your question has nothing to do with embedded linux and is thus off
topic on this list.
Please post U-Boot related quuestions to the u-boot-users mailing
list instead.
Yes, U-Boot can use PCI based network cards if there is (1) PCI
support for your board and (2) an U-Boot ethernet driver for the
network card
> specifically I am wondering how hard it would be to boot from an Intel e1000
> ethernet controller rather than the on-chip ethernet on my Ebony board.
It's not hard at all. An e1000 driver has been ported to U-Boot.
> Has anyone had experience with this, or can point me in the right direction
> on where to look to write some simple drivers to support transfers from the
> e1000 card, that would be great.
See the drivers/ directory in the U-Boot source code.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Weekends were made for programming. - Karl Lehenbauer
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-07-25 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 12:10 U-Boot, tftp and PCI ethernet Brian Padalino
2003-07-25 13:14 ` Wolfgang Denk [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=20030725131448.E7A9AC602D@atlas.denx.de \
--to=wd@denx.de \
--cc=bpadalino@perigee.com \
--cc=linuxppc-embedded@lists.linuxppc.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).