Hi Lennart,
Lennart Sorensen wrote:
On Thu, May 21, 2009 at 04:53:33PM +1000, Greg Ungerer wrote:
I have started an upload of a new uClinux-dist patch, at:
http://www.uclinux.org/pub/uClinux/dist/patches/uClinux-dist-20080808-20090520.patch.gz
It won't all be there for probably about 24 hours. So hold of
downloading 'till tomorrow :-)
It includes a linux-2.6.29 kernel, and other various fixes and
source updates - nothing major. I think most targets work as well
as the did with the 2.6.26 kernel in there. (Excepting ARMulator
I think, I haven't had time to look at it yet).
As usual please post any patches and fixes here. (I may be a
little slow in responding for the next couple of weeks, I'll be
away).
I haven't released a linux-2.6.29-uc0 patch set as I normally would.
Instead I have been pushing my changes into the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
And then promoting them from there. Means less work for me :-)
But, are people attached to using the -uc patch series?
Does anyone still want me to create them?
So far in that git tree in the "for-linus" branch is a set of
changes to clean up the various ColdFire reset/reboot code, it should
work much better on all platforms now.
There is some more merged include file cleanups in the "includes"
branch.
The biggest changes in that git tree and some interrupt controller
improvements I am working on. There is now specific support code
for each of the various types of interrupt controllers used in
the various ColdFire parts. The support for the new parts with the
larger more flexible interrupt controllers is clean and nice (so
for 5208, 5235, 5271/5275, 5282, 5329 and their type). The code
for the older parts (5206, 5249, 5307, 5407, etc) is better, but
I am still working to improve it a little more.
What kind of improvements does the new interrupt code bring (specifically
for the 5271 that I am using)? Faster, more flexible, cleaner code?
Generally speaking the motivation is to make the ColdFire interrupt
support fit into the kernel model. Specifically this means the ability
to mask/unmask/ack interrupts directly from the kernels arch independent
interrupt code. Currently in ColdFire land we unmask interrupts in
pretty much an ad-hoc fashion as required. And for those interrupts
that need ack'ing we do that with hacks in drivers and the like.
I want to clean this up and make it all work "properly".
Unfortunately it is not as simple as it sounds. There is quite a few
differences in the interrupt controllers used across the various
ColdFire parts now. The modern parts are strait forward, the older
parts are taking a little more effort. It all seems to be falling
out nicely overall though.
In terms of external differences you may not see too much on the
5271. Internally it means I can simplify the interrupt setup for
the internal devices (timers, UARTs, FEC, etc).
On cores that support external interrupts it meands getting
drivers going is a much simpler task.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: [email protected]
SnapGear Group, McAfee PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
