From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Li Yang-r58472" <LeoLi@freescale.com>
Cc: "Cedric Pontois" <cpontois@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: Tue, 6 Mar 2007 12:42:18 +0300 [thread overview]
Message-ID: <20070306124218.4bebc288@localhost.localdomain> (raw)
In-Reply-To: <989B956029373F45A0B8AF02970818902DA97B@zch01exm26.fsl.freescale.net>
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
next prev parent reply other threads:[~2007-03-06 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 10:12 [patch 1/1] ppc: Possible bug fix for FCC driver Cedric Pontois
2007-03-06 2:23 ` Li Yang-r58472
2007-03-06 9:42 ` Vitaly Bordug [this message]
2007-03-06 11:03 ` Cedric Pontois
2007-03-06 21:45 ` Vitaly Bordug
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=20070306124218.4bebc288@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=LeoLi@freescale.com \
--cc=cpontois@nortel.com \
--cc=dmalek@jlc.net \
--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