[uClinux-dev] Re: merge of m68knommu and m68k arch branches?
On Tue, Feb 22, 2011 at 08:29, Sam Ravnborg wrote:
>> >> Is there a plan to move m68k to the generic facilities as well ?
>>
>> Moving m68k to genirq is (the next thing?) on my list...
>
> If I succeed migrating sparc32 to genirq I hope to be of a little help here.
> It looks like a bigger task to migrate m68k than it was/is to migrate sparc32.
>
> It would be _very_ nice to get the last two architectures migrated to genirq.
Aren't your forgetting s390?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
[uClinux-dev] Re: merge of m68knommu and m68k arch branches?
> > > > > >> Is there a plan to move m68k to the generic facilities as well ? > > Moving m68k to genirq is (the next thing?) on my list... If I succeed migrating sparc32 to genirq I hope to be of a little help here. It looks like a bigger task to migrate m68k than it was/is to migrate sparc32. It would be _very_ nice to get the last two architectures migrated to genirq. Sam ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
[uClinux-dev] Re: merge of m68knommu and m68k arch branches?
On Tue, Feb 22, 2011 at 03:05, Greg Ungerer wrote:
> On 22/02/11 07:18, Thomas Gleixner wrote:
>> On Fri, 18 Feb 2011, Greg Ungerer wrote:
>>> Inside of the new arch/m68k is a little messy in the kernel and mm
>>> directories. There is plenty of scope for cleanup and merge on the
>>> files in here - but I want to leave that for follow up patches after
>>> this initial directory merge. As a data point, when we merged the
>>> m68k and m68knommu include files we had something like 70 or 80
>>> duplicate but separate files, after some cleanups that is now down to
>>> 10. Ongoing cleanup will merge some of these remaining ones as well.
>>>
>>> Thoughts?
>>
>> Hmm, how are you going to deal with the fact, that m68knommu uses
>> genirq, m68k not? I guess there are some more points like this
>> (clockevents, clocksource ...)
>
> Initially it has no impact. This first step pretty much just
> combines the 2 directories, it doesn't attempt to do a fine
> grained merge of each file. (It does factor out identical
> files - quite a few in arch/m68k/lib for example).
>
>
>> Is there a plan to move m68k to the generic facilities as well ?
Moving m68k to genirq is (the next thing?) on my list...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
[uClinux-dev] Re: merge of m68knommu and m68k arch branches?
Hi Thomas, On 22/02/11 07:18, Thomas Gleixner wrote: On Fri, 18 Feb 2011, Greg Ungerer wrote: Inside of the new arch/m68k is a little messy in the kernel and mm directories. There is plenty of scope for cleanup and merge on the files in here - but I want to leave that for follow up patches after this initial directory merge. As a data point, when we merged the m68k and m68knommu include files we had something like 70 or 80 duplicate but separate files, after some cleanups that is now down to 10. Ongoing cleanup will merge some of these remaining ones as well. Thoughts? Hmm, how are you going to deal with the fact, that m68knommu uses genirq, m68k not? I guess there are some more points like this (clockevents, clocksource ...) Initially it has no impact. This first step pretty much just combines the 2 directories, it doesn't attempt to do a fine grained merge of each file. (It does factor out identical files - quite a few in arch/m68k/lib for example). Is there a plan to move m68k to the generic facilities as well ? I'll look at doing what I can as I work through merging all the underlying pieces :-) Regards Greg Greg Ungerer -- Principal EngineerEMAIL: g...@snapgear.com SnapGear Group, McAfee PHONE: +61 7 3435 2888 8 Gardner Close FAX: +61 7 3217 5323 Milton, QLD, 4064, AustraliaWEB: http://www.SnapGear.com ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
[uClinux-dev] Re: merge of m68knommu and m68k arch branches?
On Mon, Feb 21, 2011 at 10:43:15PM +0100, Arnd Bergmann wrote: > On Friday 18 February 2011 13:01:53 Greg Ungerer wrote: > > >> Attached is a script and patch that does a kind of brute force > > >> simplistic merge of the directories and files. (Thanks to Stephen King > > >> for the initial version of this script, and to > > >> Sam Ravnborg for the m68k includes merge script this was based on). > > >> Nothing outside of the arch/m68k and arch/m68knommu directories is > > >> touched, and in the end there is no more arch/m68knommu. To apply you > > >> simply run the script from the top of a current kernel git tree (I used > > >> 2.6.38-rc5 for testing) and then apply the patch. > > > > > > The initial version of said script was created by Arnd IIRC. > > > > Apologies to Arnd then :-) > > I had absolutely no memory of having done said script, but if Sam > says wrote it did, that's probably true. > > I was just about to say how much I like your script when I read > that it was my idea... See semi original version in: 49148020bcb6910ce71417bd990a5ce7017f9bd3 Sam ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
