All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj@mimc.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [BR-AVR32] [PATCH] Support for new MIMC200 board
Date: Tue, 07 Oct 2008 10:07:25 +0100	[thread overview]
Message-ID: <48EB26CD.4010003@mimc.co.uk> (raw)
In-Reply-To: <20081007104345.59bacec2@hcegtvedt>

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.

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 ?

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.
Mark

  reply	other threads:[~2008-10-07  9:07 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 [this message]
2008-10-07  9:16         ` Hans-Christian Egtvedt

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=48EB26CD.4010003@mimc.co.uk \
    --to=mpfj@mimc.co.uk \
    --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.