All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Petazzoni <maxime.petazzoni@bulix.org>
To: buildroot@busybox.net
Subject: [Buildroot] beagleboard support
Date: Tue, 18 Jan 2011 10:20:07 -0800	[thread overview]
Message-ID: <20110118182007.GD9083@bulix.org> (raw)
In-Reply-To: <895970.43224.qm@web161805.mail.bf1.yahoo.com>

Hi Steve,

* Steve Calfee <nospamcalfee@yahoo.com> [2011-01-17 17:06:51]:

> I found a patch from last may proposing a beagleboard defconfig, but it is not 
> in my 11/10 release of buildroot. Does anyone know the status of beagleboard 
> support?

AFAIK BeagleBoard support has not been merged in yet. The patch from
last May is being progressively reworked. I recently submitted a patch
for X-Loader support which is a pre-requesite to BeagleBoard support. We
then need to implement building a kernel from Git instead of from a
released tarball (kernel trees with BeagleBoard support are usually not
tarballed), and finally we can add the board support.

I haven't heard anything back on my X-Loader support patch though, but I
guess everyone is pretty busy in the beginning of the new year.

- Maxime
-- 
Maxime Petazzoni <http://www.bulix.org>
 ``One by one, the penguins took away my sanity.''
Writing software in California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110118/62c702c6/attachment.asc>

  reply	other threads:[~2011-01-18 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  1:06 [Buildroot] beagleboard support Steve Calfee
2011-01-18 18:20 ` Maxime Petazzoni [this message]
2011-01-18 22:32   ` Luca Ceresoli

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=20110118182007.GD9083@bulix.org \
    --to=maxime.petazzoni@bulix.org \
    --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.