From: Robert S. Grimes <rsg@alum.mit.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Port for M5329EVB ColdFire MCF5329 eval board - needs network!
Date: Wed, 13 Jun 2007 22:14:51 -0400 [thread overview]
Message-ID: <4670A49B.7010703@alum.mit.edu> (raw)
Hi all,
I've been working on a port for the Freescale/LogicPD eval board with
the ColdFire MCF5329 microcontroller. I've got it up and running from
flash and all. No network yet - and I'm not sure how to proceed there.
It seems from an example or two that U-Boot network drivers are usually
fairly simple. Is it true that a simple polled driver is sufficient?
I'd like to get Ethernet working, but I have more pressing concerns
right now, so I can't really spend a lot of time on it. However, I'd be
interested in working with others, and certainly would welcome a bit
more guidance; I haven't really found much in the way of an "Ethernet
Driver How-To", and I've looked. Of course, I could have missed it...
On a different topic, I would like to submit my BSP. I don't know how
interested people would be, given its current state - no Ethernet, and
frankly, not extensively tested. I will be using it over the next few
months, so I'd expect these to improve, but it's probably not really
ready for formal inclusion. What does one do in such situations? What
is the process for new BSPs, especially incomplete "beta" versions?
Thanks for your time,
-Bob
next reply other threads:[~2007-06-14 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 2:14 Robert S. Grimes [this message]
2007-06-14 3:01 ` [U-Boot-Users] Port for M5329EVB ColdFire MCF5329 eval board - needs network! Ben Warren
2007-06-14 11:24 ` Robert S. Grimes
2007-06-14 14:35 ` Ben Warren
2007-06-18 16:06 ` [U-Boot-Users] Port for M5329EVB ColdFire MCF5329 eval board -needs network! Liew Tsi Chung-r5aahp
2007-06-19 6:38 ` [U-Boot-Users] Port for M5329EVB ColdFire MCF5329 eval board - needs network! Thomas Jansson
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=4670A49B.7010703@alum.mit.edu \
--to=rsg@alum.mit.edu \
--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.