From: Dean Matsen <deanmatsen@earthlink.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Err in config script in 2.4.22-pre4 re: LXT970 and LXT971 chips
Date: Thu, 10 Jul 2003 12:42:07 -0700 [thread overview]
Message-ID: <3F0DC18F.10106@earthlink.net> (raw)
I originally posted this on ppclinux-embedded, but webmaster as
MontaVista suggested
I post it here instead:
I noticed that in the file arch/ppc/8xx_io/Config.in in
the 2.4.22-pre4 (devel) kernel
CONFIG_FEC_LXT970 is listed twice, whereas I think
the second instance should be for the 971/972.
Originally was:
bool 'Support AMD79C874 PHY' CONFIG_FEC_AM79C874
bool 'Support LXT970 PHY' CONFIG_FEC_LXT970
bool 'Support QS6612 PHY' CONFIG_FEC_QS6612
bool 'Support LXT970 PHY' CONFIG_FEC_LXT970
bool 'Support DP83843 PHY' CONFIG_FEC_DP83843
I changed my version to say:
bool 'Support AMD79C874 PHY' CONFIG_FEC_AM79C874
bool 'Support LXT970 PHY' CONFIG_FEC_LXT970
bool 'Support QS6612 PHY' CONFIG_FEC_QS6612
bool 'Support LXT971/972 PHY' CONFIG_FEC_LXT971
bool 'Support DP83843 PHY' CONFIG_FEC_DP83843
Otherwise, you can't use a 971/972 chip. This is obviously
just a cut-and-paste error.
Thanks
Dean
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-07-10 19:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F0DC18F.10106@earthlink.net \
--to=deanmatsen@earthlink.net \
--cc=linuxppc-dev@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).