From: Sylvain Munaut <tnt@246tNt.com>
To: John Rigby <jcrigby@gmail.com>
Cc: Txema Lopez <tlopez@aotek.es>, John Rigby <jrigby@freescale.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add support for lite5200b board.
Date: Sun, 29 Jan 2006 23:21:48 +0100 [thread overview]
Message-ID: <43DD3FFC.3040608@246tNt.com> (raw)
In-Reply-To: <4b73d43f0601261329n73971003n9217374a1cc2db6f@mail.gmail.com>
John Rigby wrote:
>
>
> On 1/25/06, *Sylvain Munaut* <tnt@246tnt.com <mailto:tnt@246tnt.com>> wrote:
>
>
>
> Should apply fine on vanilla. My suggestion for now is take vanilla,
> apply this patch, then the 2-3 patch from Andrey for BestComm and stuff.
>
>
> I was working on getting bestcomm and fec working, but forward porting
> my old 2.6.10 code to current is turning out to be more difficult than I
> expected.
> If you already have working code then I'll stop working on them.
>
> Where are these patches? I'm new to this list so I don't have much
> history.
> Would I find these patches in the archive?
Checkout (with git)
http://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx
then apply
http://gitbits.246tNt.com/patches/bcomm-to-split.diff
(I haven't cleanly splitted it up yet and right now I must go, so it's
probably gonna be in the git tree this week, under the 'bestcomm' head ;)
Please report if it works fine on your board (both lite5200 and
lite5200b reports are welcome). I only did quick tests.
Sylvain
next prev parent reply other threads:[~2006-01-29 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 17:12 [PATCH] Add support for lite5200b board John Rigby
2006-01-24 18:17 ` Sylvain Munaut
2006-01-25 10:24 ` Txema Lopez
2006-01-25 23:21 ` Sylvain Munaut
2006-01-25 23:44 ` Grant Likely
2006-01-26 21:29 ` John Rigby
2006-01-29 22:21 ` Sylvain Munaut [this message]
2006-01-30 18:52 ` John Rigby
2006-01-30 20:29 ` Sylvain Munaut
2006-01-30 21:17 ` John Rigby
2006-01-30 22:17 ` John Rigby
2006-01-30 22:22 ` John Rigby
2006-01-30 23:45 ` Sylvain Munaut
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=43DD3FFC.3040608@246tNt.com \
--to=tnt@246tnt.com \
--cc=jcrigby@gmail.com \
--cc=jrigby@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tlopez@aotek.es \
/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.