From: Pete Popov <ppopov@mvista.com>
To: Steve Johnson <stevej@ridgerun.com>,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: RE: MIPS config.in NET configuration
Date: Thu, 16 Nov 2000 17:46:52 -0800 [thread overview]
Message-ID: <3A148E0C.5056F18A@mvista.com> (raw)
Hi Steve,
> I'm trying to add support for a Galileo Tech. EV64120A board,
>building on Pete Popov's work that's already in CVS. I'm having trouble
>with the "Network device support" menu when I "make xconfig".
xconfig was broken for me the last time I did some powerpc work as
well. If you want to be really safe, use "make config".
> If I select "Galileo EV96100 Evaluation board" on the "Machine
>selection" menu, I can't select PPP support in the "Network device
>support" menu because the IP22/Decstation/Baget code in
>arch/mips/config.in eclipses the normal net menu's CONFIG_PPP. Is there
>a reasonable way to resolve two different environments needing the same
>variable defined?
> The same problem exists for CONFIG_SERIAL, which is defined by the
>Decstation and doesn't let me use the normal character device 16550 UART
>menu item.
> Please note that this is only a problem for "make xconfig". "make
>menuconfig" works correctly and selects one set of responses for network
>devices based on the machine selection. Is that the solution, that
>everyone in MIPS uses "make menuconfig"?
BTW, I hope that by the end of next week, I'll be able to send Ralf the
latest patches for the ev96100. It's running pretty well now with the
scache enabled, but I found 96100 misconfiguration problems in the sdram
decoders/subdecoders. The DEC tulip (with one small patch), serial.c
(small patch again) also run fine, as well as the 96100 internal
10/100Mbps controllers.
--
Pete Popov
MontaVista Software, Inc
ppopov@mvista.com
next reply other threads:[~2000-11-17 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 1:46 Pete Popov [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 1:15 MIPS config.in NET configuration Steve Johnson
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=3A148E0C.5056F18A@mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=stevej@ridgerun.com \
/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