From: "Mark A. Greer" <mgreer@mvista.com>
To: Val Henson <val@nmt.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: GT64260 ethernet
Date: Fri, 01 Feb 2002 16:35:39 -0700 [thread overview]
Message-ID: <3C5B264B.4884586B@mvista.com> (raw)
In-Reply-To: 20020201134723.G30787@boardwalk
Val Henson wrote:
> We have a board with the Galileo GT64260 chip and we'd like to use the
> gt64260 ethernet driver. At the moment, its config option is in
> arch/ppc/config.in and is controlled by the CONFIG_GT64260 option
> (which is not turned on for our boards, CONFIG_GEMINI is). I'd think
> that the preferred way to fix this is to put the CONFIG_GT64260_ETH
> option in drivers/net/config.in. The alternative is to have
>
> if [ "$CONFIG_GT64260" = "y" -o "$CONFIG_GEMINI" = "y" ]; then
This may not be the best place for it but right now, that stuff is in
arch/ppc/config.in. When you turn on CONFIG_GT64260 (presumably as a
result of selecting your platform--see CONFIG_EV64260), there will be an
additional submenu show up under "Platform support" called "Galileo
GT64260 Options". Go in there and select the enet drivers you want and
pick a MAC addr if you don't like the default.
I guess that should migrate to the drivers/net Config.in...
The driver worked once but has been broken by the latest checkin (at
least for me). I have a version that works for me. I will push it out
sometime next week but if you need it now, let me know and I'll email it
to you.
Mark
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-01 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 20:47 GT64260 ethernet Val Henson
2002-02-01 20:56 ` Jeff Garzik
2002-02-01 23:38 ` Mark A. Greer
2002-02-01 23:35 ` Mark A. Greer [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=3C5B264B.4884586B@mvista.com \
--to=mgreer@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=val@nmt.edu \
/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.