[Buildroot] BeagleBone patches

[Buildroot] BeagleBone patches

[Frank Hunleth]

I had been sitting on some patches for making br builds for the
BeagleBone. I finally got the time to update and clean them up, and
they should show up to the list soon. I hope that this is better late
than never.

There were some things that I wasn't sure about:

1. I could not avoid adding a couple files under a board/beaglebone
directory. There aren't that many other configurations that do this,
so I wasn't quite sure how everyone would like BeagleBone referenced.
Please let me know if the folder structure should change.

2. You'll see that MLO gets built with U-boot rather than with the
X-Loader package. I'm not familiar with why the two were integrated,
but it seems to be the way that TI is doing it now with the bone so I
added an option.

3. There were a few Linux kernels to choose from. The one that I used
is the currently released version from the beagleboard group (I just
verified a couple days ago). Rather than commit the kernel
configuration that I use with my project, I pulled in the one from the
released kernel. This seemed more "right", but I did have to modify it
to compile in EXT2 so that it could mount the generated rootfs. I also
modified the kernel config to compress the kernel with gzip rather
than lzo to avoid requiring the person compiling the code to install
lzop. The latter is probably completely trivial, but I have found br's
minimalist dependencies really nice in the past and didn't want to add
another. The one thing that I don't like about this kernel
configuration is that enables an enormous number of features. I'm
guessing that this is an Angstrom-ism, and I wanted to pass it by the
list before spending any time modifying it.

Thanks,
Frank

[Buildroot] BeagleBone patches

[Peter Korsgaard]

>>>>> "Frank" == Frank Hunleth <fhunleth@troodon-software.com> writes:

Hi,

 Frank> I had been sitting on some patches for making br builds for the
 Frank> BeagleBone. I finally got the time to update and clean them up,
 Frank> and they should show up to the list soon. I hope that this is
 Frank> better late than never.

Great. I have a beaglebone as well now, but I haven't had much time to
play with it yet.

 Frank> There were some things that I wasn't sure about:

 Frank> 1. I could not avoid adding a couple files under a
 Frank> board/beaglebone directory. There aren't that many other
 Frank> configurations that do this, so I wasn't quite sure how everyone
 Frank> would like BeagleBone referenced.  Please let me know if the
 Frank> folder structure should change.

It's probably not a problem, but post your patches and I'll review in
detail.

 Frank> 2. You'll see that MLO gets built with U-boot rather than with
 Frank> the X-Loader package. I'm not familiar with why the two were
 Frank> integrated, but it seems to be the way that TI is doing it now
 Frank> with the bone so I added an option.

Yes, I believe MLO in u-boot is the "new" way, and X-loader is going
away long term.

 Frank> 3. There were a few Linux kernels to choose from. The one that I used
 Frank> is the currently released version from the beagleboard group (I just
 Frank> verified a couple days ago).

Do you mean git://github.com/hvaibhav/am335x-linux.git? Only very basic
am335x support is in mainline yet, so that imho makes sense at the
moment.

 Frank> Rather than commit the kernel configuration that I use with my
 Frank> project, I pulled in the one from the released kernel. This
 Frank> seemed more "right", but I did have to modify it to compile in
 Frank> EXT2 so that it could mount the generated rootfs. I also
 Frank> modified the kernel config to compress the kernel with gzip
 Frank> rather than lzo to avoid requiring the person compiling the code
 Frank> to install lzop.

Hmm, that sounds like a buildroot bug. We already build liblzo for the
host, so building lzop as well wouldn't be a big deal.

 Frank> The latter is probably completely trivial, but I have found br's
 Frank> minimalist dependencies really nice in the past and didn't want
 Frank> to add another. The one thing that I don't like about this
 Frank> kernel configuration is that enables an enormous number of
 Frank> features. I'm guessing that this is an Angstrom-ism, and I
 Frank> wanted to pass it by the list before spending any time modifying
 Frank> it.

Please post the patches, that will make it easier to give concrete
feedback.

-- 
Bye, Peter Korsgaard

[Buildroot] BeagleBone patches

[Frank Hunleth]

On Thu, Mar 8, 2012 at 4:19 PM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Frank" == Frank Hunleth <fhunleth@troodon-software.com> writes:
> ?Frank> 1. I could not avoid adding a couple files under a
> ?Frank> board/beaglebone directory. There aren't that many other
> ?Frank> configurations that do this, so I wasn't quite sure how everyone
> ?Frank> would like BeagleBone referenced. ?Please let me know if the
> ?Frank> folder structure should change.
>
> It's probably not a problem, but post your patches and I'll review in
> detail.

Hmm. It looked like everything worked when I sent the patches. I see
that they're posted at

http://lists.busybox.net/pipermail/buildroot/2012-March/051170.html
http://lists.busybox.net/pipermail/buildroot/2012-March/051169.html

But given that they don't have any replies, maybe they didn't get emailed out?

>
> ?Frank> 2. You'll see that MLO gets built with U-boot rather than with
> ?Frank> the X-Loader package. I'm not familiar with why the two were
> ?Frank> integrated, but it seems to be the way that TI is doing it now
> ?Frank> with the bone so I added an option.
>
> Yes, I believe MLO in u-boot is the "new" way, and X-loader is going
> away long term.
>
> ?Frank> 3. There were a few Linux kernels to choose from. The one that I used
> ?Frank> is the currently released version from the beagleboard group (I just
> ?Frank> verified a couple days ago).
>
> Do you mean git://github.com/hvaibhav/am335x-linux.git? Only very basic
> am335x support is in mainline yet, so that imho makes sense at the
> moment.

Jason Kridner told me that the hvaibhav git was the latest development
head, and that the latest release was at
https://github.com/koenkooi/linux/tree/linux-ti33x-psp-3.2-r5a+gitr09e9651bcf2ee8d86685f2a8075bc6557b1d3b91.

The "koenkooi" tree appears to have better support on the beagle
mailing list. It also runs well for me, so that's the one that I used
in the patch. I expect that the "official released kernel" will change
again in the coming months as more of the features from Koen's tree
get merged into the hvaibhav tree.

>
> ?Frank> Rather than commit the kernel configuration that I use with my
> ?Frank> project, I pulled in the one from the released kernel. This
> ?Frank> seemed more "right", but I did have to modify it to compile in
> ?Frank> EXT2 so that it could mount the generated rootfs. I also
> ?Frank> modified the kernel config to compress the kernel with gzip
> ?Frank> rather than lzo to avoid requiring the person compiling the code
> ?Frank> to install lzop.
>
> Hmm, that sounds like a buildroot bug. We already build liblzo for the
> host, so building lzop as well wouldn't be a big deal.
>
> ?Frank> The latter is probably completely trivial, but I have found br's
> ?Frank> minimalist dependencies really nice in the past and didn't want
> ?Frank> to add another. The one thing that I don't like about this
> ?Frank> kernel configuration is that enables an enormous number of
> ?Frank> features. I'm guessing that this is an Angstrom-ism, and I
> ?Frank> wanted to pass it by the list before spending any time modifying
> ?Frank> it.
>
> Please post the patches, that will make it easier to give concrete
> feedback.

If you don't see the patch emails, I'll resend them tomorrow morning.
It's weird that they didn't go through at the same time.

Thanks,
Frank

[Buildroot] BeagleBone patches

[Thomas Petazzoni]

Le Thu, 8 Mar 2012 22:53:18 -0500,
Frank Hunleth <fhunleth@troodon-software.com> a ?crit :

> But given that they don't have any replies, maybe they didn't get
> emailed out?

No, no, they have been received. I have even marked them as "to
review", but haven't had the time yet to do so.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] BeagleBone patches

[Frank Hunleth]

On Fri, Mar 9, 2012 at 3:19 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Thu, 8 Mar 2012 22:53:18 -0500,
> Frank Hunleth <fhunleth@troodon-software.com> a ?crit :
>
>> But given that they don't have any replies, maybe they didn't get
>> emailed out?
>
> No, no, they have been received. I have even marked them as "to
> review", but haven't had the time yet to do so.

No worries. I know that you guys are busy. Thanks for letting me know
that they were received.

Frank