From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Enable ULi1575 Ethernet support in 8610HPCD config
Date: Thu, 15 Nov 2007 12:05:13 -0600 [thread overview]
Message-ID: <473C8A59.9030209@freescale.com> (raw)
In-Reply-To: <20071115180247.GA4441@loki.buserror.net>
Scott Wood wrote:
> On Thu, Nov 15, 2007 at 08:03:15AM -0600, Timur Tabi wrote:
>> Zang Roy-r61911 wrote:
>>
>>> I intend to keep RTL8139 and Intel EEPR100. They work on the board and
>>> can provide extra choices except the on board Ethernet port.
>
> Is there any reason one wouldn't want to use the on-board ethernet port?
Not with this patch. The only reason to enable all those other boards is
because the on-board ethernet port *didn't* work, so everyone had to some some
PCI NIC.
> Hmm, weren't you scrounging around for a certain kind of PCI NIC that
> your 8610 board's u-boot image supported not too long ago?
Yes. That's because the on-board ethernet was not supported.
> Wouldn't it have been nice if they built in support for a few of
> the most common ones? :-)
And they did. But now, it's no longer necessary.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2007-11-15 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 18:49 [U-Boot-Users] [PATCH] Enable ULi1575 Ethernet support in 8610HPCD config Jon Loeliger
2007-11-13 21:37 ` Ben Warren
2007-11-14 11:47 ` Zang Roy-r61911
2007-11-14 15:09 ` Ben Warren
2007-11-14 15:27 ` Timur Tabi
2007-11-14 15:54 ` Jon Loeliger
2007-11-14 16:04 ` Timur Tabi
2007-11-14 16:09 ` Jon Loeliger
2007-11-14 16:30 ` Stefan Roese
2007-11-14 16:40 ` Timur Tabi
2007-11-15 10:30 ` Zang Roy-r61911
2007-11-15 14:03 ` Timur Tabi
2007-11-15 18:02 ` Scott Wood
2007-11-15 18:05 ` Timur Tabi [this message]
2007-11-16 6:14 ` Zang Roy-r61911
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=473C8A59.9030209@freescale.com \
--to=timur@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.