From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] beagleboneblack: add board
Date: Fri, 27 Sep 2013 08:42:13 +0300 [thread overview]
Message-ID: <1380260533.22318.8.camel@viko> (raw)
In-Reply-To: <CA+T6QPknCP3O2uM_S8va-MqY+jjzmojgmADw3wg4=4ePNmLw0A@mail.gmail.com>
On Thu, 2013-09-26 at 16:53 -0400, Jason Kridner wrote:
> > Would there be any issues with bumping the kernel version to this
> for
> > the original (white) beaglebone as well?
>
> Nope. I could make one build that supported both boards, but it would
> need to have both .dtb files in it. That's the only reason I made a
> separate config. Is there an easy way to include multiple .dtb files?
> Mainline u-boot is smart enough to tell me which one needs to be used
> at boot.
>
If the linux tree is common for beaglebone white and black, I think we
could use one board directory and separate buildroot defconfig's.
next prev parent reply other threads:[~2013-09-27 5:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 18:40 [Buildroot] [PATCH] beagleboneblack: add board Jason Kridner
2013-09-26 19:42 ` Peter Korsgaard
2013-09-26 20:09 ` Ryan Barnett
2013-09-26 20:53 ` Jason Kridner
2013-09-27 5:42 ` Fatih Aşıcı [this message]
2013-09-27 6:12 ` Fatih Aşıcı
2013-09-27 14:19 ` Jason Kridner
2013-10-03 20:32 ` Peter Korsgaard
2013-10-03 23:19 ` Jason Kridner
2013-09-27 13:07 ` Ryan Barnett
2013-09-27 12:21 ` Fatih Aşıcı
2013-09-27 14:24 ` Jason Kridner
2013-09-28 3:08 ` [Buildroot] [PATCHv2] beaglebone: add BeagleBone Black support Jason Kridner
2013-09-30 6:23 ` Fatih Aşıcı
2013-10-04 15:31 ` Peter Korsgaard
[not found] ` <A20C6CC8-715F-45C3-BB9F-5085269FFD13@ti.com>
2013-10-04 15:40 ` Peter Korsgaard
2013-10-05 7:53 ` Fatih Aşıcı
2013-10-05 9:12 ` Peter Korsgaard
2013-10-05 10:21 ` Fatih Aşıcı
2013-10-05 18:13 ` Peter Korsgaard
2013-10-04 15:41 ` Jason Kridner
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=1380260533.22318.8.camel@viko \
--to=fatih.asici@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 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.