[Buildroot] [BR-AVR32] [PATCH] Support for new MIMC200 board
hans-christian.egtvedt at atmel.com
Tue Oct 7 09:16:05 UTC 2008
On Tue, 07 Oct 2008 10:07:25 +0100
Mark Jackson <mpfj at mimc.co.uk> wrote:
> 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.
In 1.3.5 perhaps? Version 1.3.4 is default in BR now AFAIK.
I think I just applied a patch to my development three which added your
> the linux stuff was a bit of a sticking point ... Atmel's AVR32
> patches are all based on 18.104.22.168. 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 22.214.171.124 ?
Ah, you will need to submit the RTC code for the latest kernel, and add
a backported version for Buildroot.
It is a bit tricky the transition period before you have your stuff
applied to the different projects.
> 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 ?
It is fine to use 2.6.27 in Buildroot, I'll make a release later today
which takes advantage of that.
We have a new board coming out soon, and the patches are made for
More information about the buildroot