From: Sylvain Munaut <tnt@246tNt•com>
To: John Rigby <jcrigby@gmail•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Using bestcomm in an external module (MPC5200B to be exact)
Date: Thu, 27 Jul 2006 21:15:17 +0200 [thread overview]
Message-ID: <44C910C5.3090409@246tNt.com> (raw)
In-Reply-To: <4b73d43f0607271030o7170e8dcn28bd3f62ec243426@mail.gmail.com>
Hi John,
Frankly ... I don't know, I don't get how this new thing works ...
if you figure it out, be my guest do it and explain it to me ;)
It would be great because I get this cleaned API sitting on my
tree along with the IDE DMA and the FEC code that I'd really
like to send ...
Sylvain
John Rigby wrote:
> Sylvain,
>
> How can I help getting the mpc5200 migrated to the powerpc tree?
> I should have some time to help with this.
>
> After we get it migrated we can get the bestcomm code in and
> the various drivers that use it.
>
> Also, did you ever get a liteb board? If not send me your address
> and I will try again to get you one.
>
> Thanks
> John
>
> On 7/17/06, Sylvain Munaut <tnt@246tnt•com> wrote:
>> Benjamin Herrenschmidt wrote:
>> >> But anyway, it's mainly internal cleanup and adapting drivers
>> >> from the public version on my git tree to this newest/cleaner
>> >> version is a 15 min work ;)
>> >>
>> >
>> > Any reason why you aren't regulary submitting those patches for
>> upstream
>> > inclusion ?
>> >
>> Yes. What's in there and not in main streams adds quite a lot to
>> arch/ppc ... So
>> MPC5200 should be adapted to arch/powerpc first and then those changes.
>> And since
>> no-one did that yet and I haven't done it yet either ... (I must admit I
>> had a quick look
>> and I didn't understand much on how to do the change ...)
>>
>>
>> Sylvain
>>
>>
>> PS: Sorry for the lag (like 15 days...) you know email
>> problem/appartement change/vacation/... the usual ;)
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs•org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
next prev parent reply other threads:[~2006-07-27 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:28 Using bestcomm in an external module (MPC5200B to be exact) Trueskew
2006-06-19 13:15 ` Andrey Volkov
2006-06-19 14:50 ` Trueskew
2006-06-19 21:32 ` John Rigby
2006-06-20 0:48 ` Trueskew
2006-06-20 19:15 ` Sylvain Munaut
2006-06-28 4:08 ` John Rigby
2006-06-20 19:03 ` Sylvain Munaut
2006-06-30 23:33 ` Benjamin Herrenschmidt
2006-07-17 22:13 ` Sylvain Munaut
2006-07-27 17:30 ` John Rigby
2006-07-27 19:15 ` Sylvain Munaut [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 4:47 Trueskew
2006-06-17 18:53 ` Frank Bennett
2006-06-18 1:26 ` SalQ
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=44C910C5.3090409@246tNt.com \
--to=tnt@246tnt$(echo .)com \
--cc=jcrigby@gmail$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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