From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] net: gpio PHY driver
Date: Wed, 01 Jul 2009 14:43:05 -0400 [thread overview]
Message-ID: <4A4BAE39.2000000@RuggedCom.com> (raw)
In-Reply-To: <4A4BA8C5.3020101@gmail.com>
Darius Augulis wrote:
[snip]
> No, my system is not MPC based. I'm working on new board and CPU
> (Gemini) support in u-boot. My SoC has two GMAC controllers.
> btw, what is the right way to add new Ethernet driver?
> Should I define CONFIG_CMD_NET and CONFIG_NET_MULTI in my board config?
> Or should I define eth_* funtions right in the driver code?
I'm not an expert on the network code, but here's what I know
*I think* CONFIG_CMD_NET just turns on network commands, CONFIG_NET_MULTI says you have more than one MAC?
I recall some conversations about it being discussed recently in the mailing list, try grep-ing it for that
and check the README.
(If you haven't already)
look at u-boot/include/net.h, I think this is the functions that and ethernet driver needs to have defined.
look at u-boot/drivers/net/Makefile to see how to make u-boot build your driver by defining a new
#define CONFIG_MY_DRIVER_NAME and adding and entry there.
my exposure to the code have been mostly for powerpc and coldfire, for coldfire their ethernet driver
code is drivers/net/mcffec.c and /drivers/net/mcfmii.c, obviously this would not be what you need
but it is an example.
As always, check with the git tree on kernel.org, someone might have already done it for linux, in which case
you can try porting it into u-boot.
cheers,
- Richard
next prev parent reply other threads:[~2009-07-01 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 12:28 [U-Boot] net: gpio PHY driver Darius Augulis
2009-07-01 12:37 ` Jerry Van Baren
2009-07-01 16:31 ` Darius Augulis
2009-07-01 18:12 ` Richard Retanubun
2009-07-01 18:19 ` Darius Augulis
2009-07-01 18:43 ` Richard Retanubun [this message]
2009-07-01 18:54 ` Darius Augulis
2009-07-01 19:02 ` Ben Warren
2009-07-01 19:07 ` Darius Augulis
2009-07-01 19:18 ` Scott Wood
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=4A4BAE39.2000000@RuggedCom.com \
--to=richardretanubun@ruggedcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox