Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] I need a patch for AT91 to use a 2009.11 buildroot version? like buildroot-v23434.patch in 23434 version
Date: Wed, 13 Jan 2010 16:44:35 +0000 (UTC)	[thread overview]
Message-ID: <hikt9j$tir$1@ger.gmane.org> (raw)
In-Reply-To: 3ce6ccff1001130706i2cd1e5cahf159864c92d101e0@mail.gmail.com

On 2010-01-13, Miguel Angel Brintrup <brintrup@gmail.com> wrote:

> I'm install a BuildRoot development environment based in 23434
> version and respective patch. It's described in this page:
>
> http://www.at91.com/linux4sam/bin/view/Linux4SAM/BuildRootBuild#Get_buildroot
>
> I could generate my own file systems with BuildRoot and my own
> kernel with codesourcery tools.
>
> This environment works, but the newest versions of BuildRoot
> have most great tools to my develop.
>
> I need a patch for AT91 (AT91SAM9261) to use a 2009.11
> buildroot version? like buildroot-v23434.patch I use for
> BuilRoot 23434 version.
>
> Any of you have a patch to newest versions of BuildRoot for
> AT91??

What needs patching?  I use buildroot (from a git snapshot a
couple weeks ago) on an AT91 eval board, and it seems to work
fine without any patches.

-- 
Grant Edwards                   grante             Yow! My polyvinyl cowboy
                                  at               wallet was made in Hong
                               visi.com            Kong by Montgomery Clift!

      reply	other threads:[~2010-01-13 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 15:06 [Buildroot] I need a patch for AT91 to use a 2009.11 buildroot version? like buildroot-v23434.patch in 23434 version Miguel Angel Brintrup
2010-01-13 16:44 ` Grant Edwards [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='hikt9j$tir$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox