[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Change to list policy
>> -----Original Message-----
>> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On
>> Behalf Of John Williams
>> Sent: Thursday, April 16, 2009 7:05 PM
>> To: microblaze-uclinux@xxxxxxxxxxxxxx
>> Subject: Re: [microblaze-uclinux] Change to list policy
>> Hi Antoine,
>> On Fri, Apr 17, 2009 at 12:48 AM, Antoine Calando <acalando@xxxxxxx>
>>>> Hi folks,
>>>> For those who missed it, MicroBlaze got merged into Linus's
>>>> tree yesterday! This is big news, and a big thanks to Michal for
>>>> great work he did on LKML to get it sheparded in, and thanks also
>>>> Xilinx who supported us to make this happen.
>>> Can you please provide more details on this merge:
>>> With which base was merged the official kernel? The one from
> Petalogix SVN,
>>> or may be from Xilinx git? A mix of both? BTW what was the
>>> between these two inital branches? The Xilinx version seems much
> more recent,
>>> but is it as well maintained as the Petalogix one?
>> Hmm, where to start. About 12 months ago, Michal took the PetaLogix
>> 2.6.20 SVN kernel, and reved it up to 2.6.27 (At the time), plus a
>> bunch of work replacing the older Kconfig.auto with Device Tree
>> architecture, as used in PowerPC arch.
>> We had an attempt at mainline push then, but weren't adequately
>> resourced to really give it the push it needed, so we backed away.
>> So, the tree that is merged has of course roots from our 2.6.20 tree,
>> but has had a lot of cleanup, and uses device trees as the main
>> platform configuration technology.
>> It's relation to git.xilinx.com MicroBlaze support is less clear, and
>> indeed now that MicroBlaze is merged upstream, git.xilinx.com will
>> start to reflect that fact, plus any local patches, drivers etc added
>> by Xilinx.
> Around the same time Michal did the device tree conversion for
> I also ended up doing it somewhat independently.
> The code went up to the git server, but we had to solve some other
> first (like generating the device trees, for instance) before going to
BTW: What about to write full history log for Microblaze and things related with it?
> Once 2.6.30 comes out, git.xilinx.com will be updated to reflect
> mainline, which
> supersedes everything that is at git.xilinx.com...
> The goal of git.xilinx.com is that, as drivers get converted to a form
> that can be
> submitted to mainline, that will happen and the amount of code that diff
> with mainline will
> be reduced, if not eliminated. Now that microblaze is mainline, we can
> start this process in
> earnest... :)
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
> microblaze-uclinux mailing list
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/