From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Cedric Pontois" <cpontois@nortel.com>
Cc: Rachid Koucha <koucha@nortel.com>,
dmalek@jlc.net, linux-kernel@vger.kernel.org,
linuxppc-embedded@ozlabs.org
Subject: Re: [patch 1/1] ppc: Possible bug fix for FCC driver
Date: Wed, 7 Mar 2007 00:45:14 +0300 [thread overview]
Message-ID: <20070307004514.76bb83cc@localhost.localdomain> (raw)
In-Reply-To: <00B1F4365DDBE745B091C67A1CCFCB4307124DB1@zctfhxm1>
On Tue, 6 Mar 2007 12:03:57 +0100
Cedric Pontois wrote:
> Hi Vitaly,
>
> The problem seems to be similar in recent kernels
> (/drivers/net/fs_enet/mac-fcc.c). The transmit clock is inverted (TCI
> bit set). The packets are well received, transmitted packets go out
> (tx counter is ok), unfortunately as the clock is inverted (TCI) the
> data are not correctly received by the other side. The FCC works in
> 100Mbps (luck?) but doesn't in 10Mbps. I solved this problem by
> removing the TCI bit set as described in the patch. Actually, this
> problem depends also of the Ethernet phy used on board.
>
IIRC it worked for us with Davicom PHY on 10 MBps on one of 8260-like...
Well I give it a try once more with the recent kernel, but anyway if you think
you've located and fixed root cause, do (and test) a patch against recent kernel,
send it to me cc'ing netdev and linuxppc-embedded, and I'll push it along
if it is not breaking existing boards.
-Vitaly
> Cedric
>
> -----Original Message-----
> From: Vitaly Bordug [mailto:vbordug@ru.mvista.com]
> Sent: mardi 6 mars 2007 10:42
> To: Li Yang-r58472
> Cc: Pontois, Cedric UMTS (CEZ:8Z10); dmalek@jlc.net;
> linux-kernel@vger.kernel.org; linuxppc-embedded@ozlabs.org
> Subject: Re: [patch 1/1] ppc: Possible bug fix for FCC driver
>
>
> On Tue, 6 Mar 2007 10:23:43 +0800
> Li Yang-r58472 wrote:
>
> > Hi Cedric,
> >
> > For ppc embedded related patches, please also cc:
> > linuxppc-embedded@ozlabs.org.
> >
> > > We use a kernel 2.6.14 on PPC platform (MPC 8555). The FCC driver
> > works
> >
> > To submit a kernel patch upstream, the patch should be against the
> > latest kernel version which is 2.6.21-rc now.
> > > well with a 100Mbps link. But it doesn't with a 10Mbps link. To
> > > solve it, I modified the GFMR register init: removed TCI bit and
> > > set
>
> > > CRC32
> > bit
> > > instead of.
> >
> > I don't know how these bits caused the 10M link issue. Do you have
> > any reasoning?
> >
> > > Signed-off-by: Cedric Pontois <cpontois@nortel.com>
> > >
> > >
> > ----------------------------------------------------------------------
> > --
> > > -----
> > >
> > > diff -ruN pa-original/arch/ppc/8260_io/fcc_enet.c
> The fcc code in 8260_io has been obsoleted by fs_enet driver
> (drivers/net/fs_enet). It is known to work with 85xx at least in
> recent kernels. If it does not for some reason, please letus know.
>
> Thanks,
>
> -Vitaly
prev parent reply other threads:[~2007-03-06 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00B1F4365DDBE745B091C67A1CCFCB43070CE21E@zctfhxm1>
2007-03-06 2:23 ` [patch 1/1] ppc: Possible bug fix for FCC driver Li Yang-r58472
2007-03-06 9:42 ` Vitaly Bordug
2007-03-06 11:03 ` Cedric Pontois
2007-03-06 21:45 ` Vitaly Bordug [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=20070307004514.76bb83cc@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=cpontois@nortel.com \
--cc=dmalek@jlc.net \
--cc=koucha@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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).