From: Sylvain Munaut <tnt@246tNt.com>
To: Dale Farnsworth <dale@farnsworth.org>,
linuxppc-embedded@ozlabs.org, jrigby@freescale.com
Subject: Re: [PATCH] Add fec support for mpc52xx
Date: Fri, 03 Feb 2006 01:19:28 +0100 [thread overview]
Message-ID: <43E2A190.4000409@246tNt.com> (raw)
In-Reply-To: <20060202193734.22145.qmail@farnsworth.org>
Dale Farnsworth wrote:
> In article <43E24DA6.9@freescale.com> John Rigby wrote:
>
>>Adds fec support, requires bestcom patch. Applies to Sylvains git tree.
>
>
> Hmm, I thought that fec support was already in Sylvain's git tree.
>
> I'm sure Sylvain intended it to be there.
Yup, after the recent updates that went upstream, I re-created more
cleanly my git tree. To keep it clean, I took my time to try out several
git feature and stuff before publishing result. For now the bcomm is
available as a patch and I posted the URL recently.
The splitted vesion should be uploaded tomorrow, I'll make sure I use
the latest microcode (compare with the one sent by John) but It's
getting late here.
If you don't get up too early, it should be done by the time you get up ;)
Sylvain
>
> From http://ozlabs.org/pipermail/linuxppc-embedded/2005-June/018887.html:
>
>>Date: Sun, 19 Jun 2005 00:15:32 +0200
>>From: Sylvain Munaut <tnt@246tNt.com>
>>
>>Following the obvious demand for it :
>>
>>rsync://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx.git
>>http://gitbits.246tNt.com/gitweb.cgi?p=linux-2.6-mpc52xx.git;a=summary
>>
>>Hopefully the server is setup correctly ...
>>It's not _heavily_ tested but it seems to works fine in the few test I
>>made.
>>
>>What in there :
>> - I2C patches that are already sent upstream but not yet in Linus tree
>> - Change of the mpc52xx uart device name and device ids to a range in
>> the low density serial port major. Also it's now named ttyPSC? so
>> you need to update you kernel command line (else you won't see any
>> console). Note that the ids and names choosed are NOT YET OFFICIAL,
>> I just included it in this release because some people were seeing
>> conflict with the other ids. So the name and ids may change ...
>> - Some other patches that will soon be sent upstream, just waiting
>> for you to test see if it has any negative impact.
>> - FEC and BestComm rewrite from Dale, with some improvement. For eg,
>> the FEC task now handle misaligment so the manual alignment code
>> has been removed, ...
>
>
> I hope Sylvain can resurrect the 2.6 FEC code that he, I and others
> worked on.
>
> -Dale
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
prev parent reply other threads:[~2006-02-03 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 18:21 [PATCH] Add fec support for mpc52xx John Rigby
2006-02-02 19:37 ` Dale Farnsworth
2006-02-02 19:54 ` John Rigby
2006-02-03 0:19 ` Sylvain Munaut [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=43E2A190.4000409@246tNt.com \
--to=tnt@246tnt.com \
--cc=dale@farnsworth.org \
--cc=jrigby@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.