[Buildroot] [BR-AVR32] [PATCH] Support for new MIMC200 board

Mark Jackson mpfj at mimc.co.uk
Tue Oct 7 09:07:25 UTC 2008

Hans-Christian Egtvedt wrote:


> You must split up your patch, it contains far more than just a new
> board. Each patch should only add/change one feature in Buildroot.
> I would also recommend that you get all the kernel and U-Boot stuff
> upstream first, and then go for the Buildroot stuff.

Ho, hum.  I was kinda hoping to put that off ... too lazy, too many other things to do !!.
But I guess I just need to buckle down and get it sorted.

In fact the u-boot stuff *is* already upstream ... the u-boot patch is a bit of a hang over.  Oops.

the linux stuff was a bit of a sticking point ... Atmel's AVR32 patches are all based on
But I'm guessing that if I submit my new RTC support code won't it only be added to the latest kernels ?

How can I submit my RTC code *and* still use ?

I know I could use Haavard's latest linux (2.6.27.??), but then that's moving further away from
the buildroot "all-in-one" principal !?!

Any ideas ?

>>> Is the patch based on the latest uclibc.org repo or Buildroot for
>>> AVR32 release (v2.2.0)?
>> The latest svn (actually r23594).
> Then it is better if you post it to uclibc.org mailing list, I import
> stuff from uclibc.org, so eventually it will end up in my fork() as
> well.

Okay ... will do.

Thanks for the feedback.

More information about the buildroot mailing list