Hi Jamie, Mike,
Mike Frysinger wrote:
On Tuesday 15 December 2009 14:52:59 Jamie Lokier wrote:
Mike Frysinger wrote:
On Saturday 12 December 2009 00:12:19 Jamie Lokier wrote:
I'm looking for a Git repository which corresponds to the kernel in
the uClinux distribution, to see the changes with history in a
cherry-pickable form. Is there a repository?
i dont know what you're looking for exactly, but the kernel that ships
with the uClinux-dist is largely a vendor kernel now (which is to say,
it's the mainline one plus board ports and drivers), and from what i
understand, a good m68k/coldfire reference.
It also has a lot of arm-nommu changes, which is my interest at the
moment as I'm porting something from 2.4 which isn't in anyone's tree,
but is yet another arm-nommu variant. I don't know if I would find
all the things I need in the mainline kernels.
yes, Greg also keeps quite a bit of arm-nommu stuff and is probably the most
usable (only?) tree for it. i dont track the arm kernel, so i'd forgotten
about this. i do recall a guy stepping up and finally getting things
mainlined, but that's going on like right now, so i doubt mainline is good
enough for you atm. i imagine it'll be a few releases before you can sanely
switch over to mainline.
The non-MMU ARM is more tricky. I try to keep the uClinux-dist
ARM no-mmu targets working (well at least GDB/ARMulator/Skyeye).
But it is very much on a as-time-permits basis for me.
Catalin Marinas (from ARM) got the last of required core changes
commited to Linus' tree for 2.6.32 - so all the core parts are
now there for non-MMU ARM. I am in the process of bringing that
into uClinux-dist (for a new kernel patch) that will have hopefully
have its non-mmu ARM targets all working with the current 2.6.32
code base. I expect there is a few things I'll need to clean out
(that is remove :-) from the uClinux-dist kernel to get that
non-MMU ARM working again.
I doub't main-line will be enough on its own right now yet.
The ARM arch peiecs for real targets not all be there. (Maybe
it is good enough, I just don't know yet).
in terms of nommu-specific changes, those largely come from David
Howells and dont see the uClinux-dist tree until they're mainlined
(or Greg merges them).
I'm not sure about that. I see quite a few nommu-specific changes in
the uClinux-dist tree relative to the same mainline kernel version.
I had hoped to see the not-ready-for-mainline nommu changes in David
Howells nommu.git :-), but that doesn't seem to see much action. We
can't have everything I guess :-)
i dont really know of what you speak exactly. i just downloaded the latest
uclinux-dist (20091129) and i dont see anything terribly important in mm/ or
fs/, just the normal smattering of random vendor-specific changes.
The flow of real non-arch NOMMU changes is pretty small these days.
I think that is why David's nommu.got, and mine too, just don't
get used much anymore.
I see more changes go through Andrew Moreton than any other route
at the moment. Majority of those probably come from David Howells.
And to see if there are arch-independent nommu changes in uClinux-dist
that are slow getting mainlined, because I need to work with another
completely different nommu architecture too. I'm about to embark on
some core nommu memory management changes to help with fragmentation
resistance.
i think there is space for defragmentation too ... obviously not in the VM
sense where physical pages get shuffled, but in the buddy allocator sense
where contiguous smaller pages get reassembled into larger pages.
If the patch flow for generic nommu is via David Howells -> mainline
-> uClinux-dist,
Yes, very much this is correct.
then I can monitor mainline, but if it's David ->
Greg -> uClinux-dist sometimes, then I need to monitor uClinux-dist
releases because I'm not sure where else I'd find them.
i'm sure Greg can correct me, but i dont think it's ever gone (in recent
times) from David to Greg only. David is the FRV arch maintainer and pretty
good at all the nommu stuff, so he pushes straight to Linus. there isnt
technically a "nommu" maintainer, but David is the current defacto one (at
least in my eyes).
David has certainly done more non-arch non-MMU work in recent times.
when pushing patches around though, uclinux-dev/Greg/Paul/etc... tend to be
CC-ed so everyone stays in the loop.
Yeah, exactly. David (and Andrew) are pretty good at CC'ing relevant
people. I see most of the changes go by, but I am not in the pushing
path for most of them.
Unfortunately the uClinux-dev list doesn't see all of the patches
(probably due to it being sub-scriber only).
I find lkml impossibly high traffic -- unsubscribed a few years ago due to
that -- so I don't know what passes through there these days. If the most
interesting patches are often only appearing there, I guess I will
need to write some list-processing tool to draw my attention to
patches which I'd likely be interested in.
i use gmail + word filters to manage lkml. the fast majority gets archived
without me ever seeing it.
And lo, a google for David and I find uclinux-dist-devel which I
hadn't noticed before. Perhaps I should subscribe there.
dont let the name fool you. it's Blackfin-specific (even though nommu patches
do get CC-ed through there). we rely on the domain (@blackfin...) to indicate
the Blackfin-specific aspect rather than duplicating it in the list names with
like "bfin" qualifiers.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: g...@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: 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
