From: apoorv sangal <apoorvsangal@gmail.com>
To: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>,
Linuxppc-embedded@ozlabs.org, david.jander@protonic.nl
Cc: apoorv sangal <apoorv_sangal@satyam.com>,
vikrant_basotra@satyam.com, sibi_mathew@satyam.com
Subject: Re: Problem Regarding Ping in Linux kernel version 2.4.24
Date: Mon, 10 Oct 2005 16:10:30 +0530 [thread overview]
Message-ID: <a79669360510100340g2563b441w9418001c034dbe5b@mail.gmail.com> (raw)
In-Reply-To: <20051007123126.GA6879@cathedrallabs.org>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi
Thanks for the inputs... As per your suggestion I commented
{ mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
but it doesn't make any diffrence, still the ping doesn't worked.
At Boot loader level (u-boot) Ping works fine,
Regards
Apoorv Sangal
On 10/7/05, Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org> wrote:
>
> Hi,
> > I have ported Linux kernel version 2.4.24 on MPC8266 based customized
> > Board, having LXT971 ethernet chip.
> > The root file system is JFFS2 which i have made using mkfs.jffs2 utility
> which
> > comes along with the ELDK 3.0
> > In the kernel code i checked that there is support for the LXT971 chip,
> but
> > even after enabling all the network related funcuntionalities in the
> linux
> > kernel configuration, I am either not able to ping from the board to any
> > machine on the network, nor from the any other machine to the board.
> > The board is able to ping itself.
> > Can some one please throw some light why the board is not able to ping
> any
> > other machine.
> try to comment this line in LXT971 section of driver:
> { mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
> and check if it works
>
> --
> Aristeu
>
>
[-- Attachment #2: Type: text/html, Size: 1998 bytes --]
next prev parent reply other threads:[~2005-10-10 10:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 5:05 Problem Regarding Ping in Linux kernel version 2.4.24 apoorv sangal
2005-10-07 12:31 ` Aristeu Sergio Rozanski Filho
2005-10-10 10:40 ` apoorv sangal [this message]
2005-10-10 12:36 ` Mark Chambers
2005-10-10 17:00 ` MPC8555 USB host support Stefan Roese
2005-10-11 20:29 ` Kylo Ginsberg
2005-10-12 6:59 ` Stefan Roese
2005-10-12 7:01 ` Pantelis Antoniou
2005-10-12 7:11 ` Mike Rapoport
2005-10-12 7:27 ` Stefan Roese
2005-10-12 12:34 ` Alex Zeffertt
2005-10-31 6:45 ` Mike Rapoport
[not found] ` <1131960060.7748.9.camel@hawk.pwav.net>
2005-11-15 6:59 ` Mike Rapoport
2005-11-15 12:03 ` Alexandre BASTOS
2005-11-15 15:22 ` Kumar Gala
2005-11-15 15:38 ` Mike Rapoport
2005-11-15 15:40 ` Vitaly Bordug
2005-11-16 15:50 ` Kumar Gala
2005-11-16 15:57 ` Vitaly Bordug
2005-11-17 12:34 ` Yuli Barcohen
2005-12-01 12:26 ` MPC8555 8280/8270 " Hans Schillstrom
2005-12-01 13:55 ` Mike Rapoport
2005-12-01 15:29 ` Wolfgang Denk
2005-10-11 6:27 ` Problem Regarding Ping in Linux kernel version 2.4.24 apoorv sangal
2005-10-11 12:23 ` Mark Chambers
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=a79669360510100340g2563b441w9418001c034dbe5b@mail.gmail.com \
--to=apoorvsangal@gmail.com \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=apoorv_sangal@satyam.com \
--cc=aris@cathedrallabs.org \
--cc=david.jander@protonic.nl \
--cc=sibi_mathew@satyam.com \
--cc=vikrant_basotra@satyam.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;
as well as URLs for NNTP newsgroup(s).