* Re: Re: Change FEC and SCC1 sequence,But SCC1 not work?
@ 2004-06-11 6:22 hjzgq
2004-06-11 16:02 ` Wolfgang Denk
0 siblings, 1 reply; 2+ messages in thread
From: hjzgq @ 2004-06-11 6:22 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: wd
Wolfgang Denk:
Thanks a lot!
My bootargs is "setenv bootargs root=/dev/ram ip=10.32.5.17:10.32.5.15::255.255.0.0:bug
:::off"
Today,I found fec device down when linux kernel running ,but I can see "eth1(fec ethernet)" status with "ifconfig" command,I checked linux kernel and found fec device down when kernel running.
After debugging,I found linux kernel close the device when running "ip_auto_config()" function in "net/ipv4/ipconfig.c",then, I deleted "ic_open_devs()" funtions, AND EVERYING
WORKS WELL!
But why do it be added to Linux kernel?
Best regards,
Michael. Z.
----- Original Message -----
From: Wolfgang Denk
Subject: Re: Change FEC and SCC1 sequence,But SCC1 not work?
Sent: Fri Jun 11 01:17:56 CST 2004
> In message <5357004.1086858754080.JavaMail.postfix@mx27.mail.sohu.com> you wrote:
> >
> > Briefly, my platform is MPC860T from Motorola. I'm using ppcboot
> > 1.1.16 to tftp the kernel 2.4.4 through FEC and then load
> > NFS/RAMDISK. If I configure the kernel with only FEC, then
> > everything works well(NFS works and ping through eth0 works). If I
> > configure the kernel with both FEC(as eth0) and SCC1(as eth1),it
> > works well too,but when I configure ther kernel with both SCC1(eth0)
> > and FEC(as eth1) (net/setup.c)! . I try to ping out through
> > FEC(eth1), I get ring buffer dumps and no ping response:
>
> Please post the "Kernel command line" as printed when your kernel
> boots. You did include a network device parameter in your ip= boot
> argument, didn't you?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Change FEC and SCC1 sequence,But SCC1 not work?
2004-06-11 6:22 Re: Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
@ 2004-06-11 16:02 ` Wolfgang Denk
0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Denk @ 2004-06-11 16:02 UTC (permalink / raw)
To: hjzgq; +Cc: linuxppc-embedded
In message <116411.1086934938680.JavaMail.postfix@mx27.mail.sohu.com> you wrote:
>
> My bootargs is "setenv bootargs root=/dev/ram ip=10.32.5.17:10.32.5.15::255.255.0.0:bug
> :::off"
> Today,I found fec device down when linux kernel running ,but I can see "eth1(fec ethernet)" status with "ifconfig" command,I checked linux kernel and found fec device down when kernel running.
>
> After debugging,I found linux kernel close the device when running "ip_auto_config()" function in "net/ipv4/ipconfig.c",then, I deleted "ic_open_devs()" funtions, AND EVERYING
> WORKS WELL!
But you are removing perfectly valid code. Don't do this!!
Just read the documentation (especially Documentation/nfsroot.txt)
and pass the CORRECT boot arguments, which in case or several network
interfaces MUST specify which interface to configure, i. e. the
minimum information is then
... ip=10.32.5.17:10.32.5.15::255.255.0.0:bug:eth0:off
[Note that your "ip=" string has one colon too many, too.]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Software suppliers are trying to make their software packages more
``user-friendly''. . . . Their best approach, so far, has been to
take all the old brochures, and stamp the words, ``user-friendly'' on
the cover. - Bill Gates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-06-11 16:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-11 6:22 Re: Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
2004-06-11 16:02 ` Wolfgang Denk
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).