From: Chris LaRocque <clarocq@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot
Date: Sat, 26 Dec 2015 11:00:07 -0500 [thread overview]
Message-ID: <n5mdi8$5go$1@ger.gmane.org> (raw)
In-Reply-To: 1450917779.3775953.475348978.37FAC3A8@webmail.messagingengine.com
Craig Swank wrote:
> Here is another thing I've found:
>
> https://github.com/beagleboard/linux/issues/49
>
> In that issue the person had some addresses set incorrectly in uEnv.txt,
> but mine doesn't have any addresses set:
>
> bootpart=0:1
> bootdir=
> uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run ram
> boot
>
> Is there something that needs to be set in uEnv.txt?
>
>
> On Wed, Dec 23, 2015, at 02:52 PM, Thomas Petazzoni wrote:
>> Dear Craig Swank,
>>
>> On Wed, 23 Dec 2015 14:45:36 -0800, Craig Swank wrote:
>> > Is it strange to you that when I do the build the output/build
>> > directory has both of these dirs?
>> >
>> > ? buildroot git:(master) ? ls output/build/linux-*
>> > output/build/linux-4.1.4-ti-r9
>> > output/build/linux-headers-3.12.10
>>
>> No, it is perfectly fine. linux-headers is used when building the
>> toolchain. linux is used to build the kernel itself.
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>
>
Hello Craig
Hopefully the attachments will be accepted.
The kernel defconfig from beagleboard.org:
1> doesn't set DEPRECATED_PARAM_STRUCT [=y] in the kernel .config. uEnv.txt
(uboot) passes in the console config as "console=ttyO0,115200n8"
2> doesn't set EXT2_FS [=y] and the default buildroot .config FS image is
ext2. at least for the beaglebone black and I'm trying to keep things sane.
You'll want to do a make source and them make linux-menuconfig and change
the parameters above.
I haven't created a patch file because I'm lazy.
Also attached is my patch (hack) for dtc, derived from Robert Nelsons
bb.org-overlays.
The dtc patch file goes into BR2_GLOBAL_PATCH_DIR ,
BR2_GLOBAL_PATCH_DIR"/dtc"
Look in the buildroot .config for how I set BR2_GLOBAL_PATCH_DIR. you'll
need to point that to your own global patch directory.
Regards
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: host-dtc-1.4.1.patch
Type: text/x-patch
Size: 32757 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151226/5748b92b/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cleaned_buildroot_v41_12182015_01.config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151226/5748b92b/attachment.ksh>
next prev parent reply other threads:[~2015-12-26 16:00 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
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 [this message]
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='n5mdi8$5go$1@ger.gmane.org' \
--to=clarocq@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