All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BR-AVR32] [PATCH] Support for new MIMC200 board
Date: Tue, 7 Oct 2008 11:16:05 +0200	[thread overview]
Message-ID: <20081007111605.129b9d3e@hcegtvedt> (raw)
In-Reply-To: <48EB26CD.4010003@mimc.co.uk>

On Tue, 07 Oct 2008 10:07:25 +0100
Mark Jackson <mpfj@mimc.co.uk> wrote:

> Hans-Christian Egtvedt wrote:
> 
> <snip>
> 
> > 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
board...

> the linux stuff was a bit of a sticking point ... Atmel's AVR32
> patches are all based on 2.6.25.10. 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 2.6.25.10 ?
> 

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
2.6.27-rcN.

<snipp>

-- 
Best regards,
Hans-Christian Egtvedt

      reply	other threads:[~2008-10-07  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 12:34 [Buildroot] [PATCH] Support for new MIMC200 board Mark Jackson
2008-10-07  5:41 ` [Buildroot] [BR-AVR32] " Hans-Christian Egtvedt
2008-10-07  8:33   ` Mark Jackson
2008-10-07  8:43     ` Hans-Christian Egtvedt
2008-10-07  9:07       ` Mark Jackson
2008-10-07  9:16         ` Hans-Christian Egtvedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081007111605.129b9d3e@hcegtvedt \
    --to=hans-christian.egtvedt@atmel.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.