From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot
Date: Wed, 23 Dec 2015 19:39:43 +0100 [thread overview]
Message-ID: <20151223193943.21a6f0fc@free-electrons.com> (raw)
In-Reply-To: <1450894505.3036056.475106194.467AC874@webmail.messagingengine.com>
Dear Craig Swank,
On Wed, 23 Dec 2015 10:15:05 -0800, Craig Swank wrote:
> Here is my response again. I sent one a few minutes ago but it might be
> too big because I tried attaching the build output.
>
> > Does it work with some other kernel?
> Yes, it works with the default kernel that is defined in
> configs/beaglebone_defconfig
>
> > Do you have console= defined in the bootargs to the proper value?
> I tried playing around with console= a few days ago, but I didn't get it
> working with that. I really am not sure what the correct args would be.
> I'm going to revisit that now and see if I can find what they should be
> set to.
>
> I uploaded the build output to
> https://www.dropbox.com/s/nbm6r5520g0wutf/nohup.out.bz2?dl=0
I don't see anything obviously wrong here. Unfortunately, I don't have
a BBB with me to test this right now. Maybe someone else on the list
will have this at hand.
That being said, you can still follow my Buildroot tutorial at
https://www.youtube.com/watch?v=1PfthHCfudY, where I'm doing a step by
step description of building a Buildroot configuration for the BBB.
It's not using the kernel from http://github.com/beagleboard/linux.git,
but instead the mainline Linux kernel. But it should give you another
thing to test and look at.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-23 18:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 17:04 [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot Craig Swank
2015-12-23 17:47 ` Thomas Petazzoni
[not found] ` <1450893821.3034067.475093450.34890777@webmail.messagingengine.com>
2015-12-23 18:15 ` Craig Swank
2015-12-23 18:39 ` Thomas Petazzoni [this message]
2015-12-23 18:59 ` Craig Swank
2015-12-23 22:45 ` Craig Swank
2015-12-23 22:52 ` Thomas Petazzoni
2015-12-24 0:42 ` Craig Swank
2015-12-24 12:44 ` Chris LaRocque
2015-12-24 19:35 ` Craig Swank
2015-12-26 16:00 ` Chris LaRocque
2015-12-26 16:31 ` Craig Swank
2015-12-26 18:34 ` Craig Swank
2015-12-26 23:02 ` Frank Hunleth
2015-12-26 23:44 ` Craig Swank
2015-12-27 0:09 ` Chris LaRocque
2015-12-27 10:08 ` Thomas Petazzoni
2015-12-27 13:34 ` Craig Swank
2015-12-27 13:35 ` Craig Swank
2015-12-27 16:28 ` Chris LaRocque
2015-12-27 17:01 ` Craig Swank
2015-12-27 18:36 ` Chris LaRocque
2015-12-27 18:48 ` Craig Swank
2015-12-27 19:27 ` Craig Swank
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=20151223193943.21a6f0fc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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