[Buildroot] BeagleBoneBlack Updates?

[Buildroot] BeagleBoneBlack Updates?

[Frank Hunleth]

It's been a while since there's been discussion on the bbb, and I
wanted to check on the current status. I've been sitting on some
patches that have been working for me for the past few months. Spenser
Gilliland had also posted a github reference to his patches a month or
so ago. As far as I can tell, the main difference is HDMI and graphics
acceleration are either working or close to working in his tree. I
don't use either feature.

I don't mind making a pass to clean up what I have and submit it to
the list, but if work is going on with Spenser's or someone else's
then I'll hold off.

Thanks,
Frank

[Buildroot] BeagleBoneBlack Updates?

[Zoltan Gyarmati]

On 09/13/2013 02:58 PM, Frank Hunleth wrote:
> It's been a while since there's been discussion on the bbb, and I
> wanted to check on the current status. I've been sitting on some
> patches that have been working for me for the past few months. Spenser
> Gilliland had also posted a github reference to his patches a month or
> so ago. As far as I can tell, the main difference is HDMI and graphics
> acceleration are either working or close to working in his tree. I
> don't use either feature.
>
> I don't mind making a pass to clean up what I have and submit it to
> the list, but if work is going on with Spenser's or someone else's
> then I'll hold off.
>
> Thanks,
> Frank
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Hi Frank&all,

 i have/had plans to get together the available patches and send them
in, but didn't find the time for that, but anyway, if you start it, i'm
keen to do some testing rounds.


-- 
br, 
Zoltan Gyarmati
mail: mr.zoltan.gyarmati at gmail.com
freenode nick: zgyarmati

[Buildroot] BeagleBoneBlack Updates?

[Jesse Cobra]

Same here, I have built your (Franks) branch and Spensers and done some
minimal testing.

I dont use HDMI for anything at the moment, just the PRUSS and a few other
things. (ath9k drivers).

-Jesse



On Fri, Sep 13, 2013 at 10:39 AM, Zoltan Gyarmati <
mr.zoltan.gyarmati@gmail.com> wrote:

> On 09/13/2013 02:58 PM, Frank Hunleth wrote:
> > It's been a while since there's been discussion on the bbb, and I
> > wanted to check on the current status. I've been sitting on some
> > patches that have been working for me for the past few months. Spenser
> > Gilliland had also posted a github reference to his patches a month or
> > so ago. As far as I can tell, the main difference is HDMI and graphics
> > acceleration are either working or close to working in his tree. I
> > don't use either feature.
> >
> > I don't mind making a pass to clean up what I have and submit it to
> > the list, but if work is going on with Spenser's or someone else's
> > then I'll hold off.
> >
> > Thanks,
> > Frank
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
>
> Hi Frank&all,
>
>  i have/had plans to get together the available patches and send them
> in, but didn't find the time for that, but anyway, if you start it, i'm
> keen to do some testing rounds.
>
>
> --
> br,
> Zoltan Gyarmati
> mail: mr.zoltan.gyarmati at gmail.com
> freenode nick: zgyarmati
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130913/889666db/attachment-0001.html>

[Buildroot] BeagleBoneBlack Updates?

[Thomas Petazzoni]

Dear Frank Hunleth,

On Fri, 13 Sep 2013 08:58:27 -0400, Frank Hunleth wrote:
> It's been a while since there's been discussion on the bbb, and I
> wanted to check on the current status. I've been sitting on some
> patches that have been working for me for the past few months. Spenser
> Gilliland had also posted a github reference to his patches a month or
> so ago. As far as I can tell, the main difference is HDMI and graphics
> acceleration are either working or close to working in his tree. I
> don't use either feature.
> 
> I don't mind making a pass to clean up what I have and submit it to
> the list, but if work is going on with Spenser's or someone else's
> then I'll hold off.

I believe Spenser might be busy with the other OpenGL work, so I think
you could probably take your work and his BBB work, and submit patches
to the list. I'd really to see the BBB be an officially supported
platform in Buildroot.

Thanks,

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

[Buildroot] BeagleBoneBlack Updates?

[Thomas Petazzoni]

Dear rh,

On Fri, 13 Sep 2013 15:38:27 -0700, rh wrote:

> I've heard that someone (TI) was supposed to be getting code into
> the kernel 3.12-rc series. But I saw a message recently and it looked
> like the 3.12 merge window was missed so 3.13 is the target.

A patch adding a basic Device Tree for the BBB has been posted on the
Linux ARM kernel mailing list. But the support is fairly minimal, i.e
MMC/SD is not even supported, for example.

> Some in the linux kernel aren't fond of ARM devices so maybe there's
> a logjam.

I really don't see where this statement comes from. There are
gazillions of patches being integrated to support ARM devices. I've
myself worked over the last year on upstreaming the support for some
ARM processors, and while it certainly requires some work, I clearly
don't think there is some resistance against ARM devices at all.

> But I've also been told that it's due to lack of resources at
> TI.

I believe this is more the problem. TI already had issues getting the
complete support for their SoCs merged in mainline (due to the
complexity of their SoC, and also probably due to the internal
organization of TI), but now TI has laid off a huge number of
engineers, including some of which where working on upstreaming work.
So there's even less work force in TI to do this work.

And on the other hand, the CircuitCo guys have not tried at all to
submit any of their patches to mainline (the Device Tree patch
mentioned above being the first one). Their excuse is that they have
been having issues to cooperate with TI on upstreaming effort, but when
we see how long it takes TI to bring stuff in mainline, there is
certainly room for others to contribute. However, I admit it is hard to
do mainline work when the SOC vendor is also doing something, but you
don't know what.

> So maybe BBB will truly be a DIY platform. The problem that exists
> is that using the wrong device tree code can result in destroying devices.
> It seems that some people have done that and blown up their HDMI
> interface.

This is if you use the mainline kernel. The BBB defconfig in Buildroot
will use the BBB-custom kernel provided by CircuitCo, because we should
certainly offer to our users a kernel that allows to use as many
features as possible of the BBB.

Best regards,

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

[Buildroot] BeagleBoneBlack Updates?

[Frank Hunleth]

On Sat, Sep 14, 2013 at 1:33 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
> Dear Frank Hunleth,
>
> On Fri, 13 Sep 2013 08:58:27 -0400, Frank Hunleth wrote:
> > It's been a while since there's been discussion on the bbb, and I
> > wanted to check on the current status. I've been sitting on some
> > patches that have been working for me for the past few months. Spenser
> > Gilliland had also posted a github reference to his patches a month or
> > so ago. As far as I can tell, the main difference is HDMI and graphics
> > acceleration are either working or close to working in his tree. I
> > don't use either feature.
> >
> > I don't mind making a pass to clean up what I have and submit it to
> > the list, but if work is going on with Spenser's or someone else's
> > then I'll hold off.
>
> I believe Spenser might be busy with the other OpenGL work, so I think
> you could probably take your work and his BBB work, and submit patches
> to the list. I'd really to see the BBB be an officially supported
> platform in Buildroot.

Sounds good.

I just rebased to the upstream and was pleased to see the updated
Linaro compilers. The Beaglebone Debian work uses Linaro 4.8-2013.07,
and I had as a todo item to try to match up compilers when I had a
chance. Both Spenser and I were using EABI compilers (as opposed to an
EABIhf one like Debian.)

I tried making the switch to EABIhf, but found out a that init won't
start due to not being able to load libc.so.6. I assumed that
somewhere I just had a compiler option different so that busybox was
being compiled with a slightly different ABI than what Linaro had done
with their version of libc. As far as I can tell with readelf, I have
both busybox and libc.so.6 reporting ABI 3.1.1 and listing:

Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "7-A"
  Tag_CPU_arch: v7
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3
  Tag_Advanced_SIMD_arch: NEONv1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: int
  Tag_ABI_HardFP_use: SP and DP
  Tag_ABI_VFP_args: VFP registers
  Tag_CPU_unaligned_access: v6

Right now, I'm not sure where to look for possible other differences.
CodeSourcery and the built-in toolchains work fine (albeit with EABI).
I was wondering if anyone else has run into issues with EABIhf to
might help me debug this.

Thanks,
Frank



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

[Buildroot] BeagleBoneBlack Updates?

[Greg Beresford]

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-
> bounces at busybox.net] On Behalf Of Frank Hunleth
> Sent: 16 September 2013 02:16
> To: Thomas Petazzoni
> Cc: buildroot
> Subject: Re: [Buildroot] BeagleBoneBlack Updates?
>
> On Sat, Sep 14, 2013 at 1:33 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> >
> > Dear Frank Hunleth,
> >
> > On Fri, 13 Sep 2013 08:58:27 -0400, Frank Hunleth wrote:
> > > It's been a while since there's been discussion on the bbb, and I
> > > wanted to check on the current status. I've been sitting on some
> > > patches that have been working for me for the past few months. Spenser
> > > Gilliland had also posted a github reference to his patches a month or
> > > so ago. As far as I can tell, the main difference is HDMI and graphics
> > > acceleration are either working or close to working in his tree. I
> > > don't use either feature.
> > >
> > > I don't mind making a pass to clean up what I have and submit it to
> > > the list, but if work is going on with Spenser's or someone else's
> > > then I'll hold off.
> >
> > I believe Spenser might be busy with the other OpenGL work, so I think
> > you could probably take your work and his BBB work, and submit patches
> > to the list. I'd really to see the BBB be an officially supported
> > platform in Buildroot.
>
> Sounds good.
>
> I just rebased to the upstream and was pleased to see the updated
> Linaro compilers. The Beaglebone Debian work uses Linaro 4.8-2013.07,
> and I had as a todo item to try to match up compilers when I had a
> chance. Both Spenser and I were using EABI compilers (as opposed to an
> EABIhf one like Debian.)
>
> I tried making the switch to EABIhf, but found out a that init won't
> start due to not being able to load libc.so.6. I assumed that
> somewhere I just had a compiler option different so that busybox was
> being compiled with a slightly different ABI than what Linaro had done
> with their version of libc. As far as I can tell with readelf, I have
> both busybox and libc.so.6 reporting ABI 3.1.1 and listing:
>
> Attribute Section: aeabi
> File Attributes
>   Tag_CPU_name: "7-A"
>   Tag_CPU_arch: v7
>   Tag_CPU_arch_profile: Application
>   Tag_ARM_ISA_use: Yes
>   Tag_THUMB_ISA_use: Thumb-2
>   Tag_FP_arch: VFPv3
>   Tag_Advanced_SIMD_arch: NEONv1
>   Tag_ABI_PCS_wchar_t: 4
>   Tag_ABI_FP_rounding: Needed
>   Tag_ABI_FP_denormal: Needed
>   Tag_ABI_FP_exceptions: Needed
>   Tag_ABI_FP_number_model: IEEE 754
>   Tag_ABI_align_needed: 8-byte
>   Tag_ABI_align_preserved: 8-byte, except leaf SP
>   Tag_ABI_enum_size: int
>   Tag_ABI_HardFP_use: SP and DP
>   Tag_ABI_VFP_args: VFP registers
>   Tag_CPU_unaligned_access: v6
>
> Right now, I'm not sure where to look for possible other differences.
> CodeSourcery and the built-in toolchains work fine (albeit with EABI).
> I was wondering if anyone else has run into issues with EABIhf to
> might help me debug this.
>

This is because the new linaro toolchain is expecting to find libc in /lib/arm-linux-gnueabihf/ as reported in https://bugs.busybox.net/show_bug.cgi?id=6452.

There's a patch to adapt toolchain/helpers.mk to the new linaro layout in the attachment to that bug, and I can say that the patch works for me, but I don't know if it would break anything else!

Regards
Greg


Disclaimer: This email contains proprietary information some or all of which may be legally privileged and/or is confidential. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, distribute, copy or print this email. Any views expressed in this message are those of the individual sender, except where the message states otherwise. ZBD Displays accepts no responsibility for any computer virus which might be transferred by way of this email. We may monitor all email communication through our networks. If you contact us by email, we may store your name and address to facilitate communication. ZBD Displays Ltd is registered in England and Wales, company registration number: 03929602. Registered Office: Malvern Hills Science Park, Geraldine Road, Malvern,  Worcestershire, WR14 3SZ, UK

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

[Buildroot] BeagleBoneBlack Updates?

[Frank Hunleth]

Hi Greg,

On Mon, Sep 16, 2013 at 5:06 AM, Greg Beresford
<greg.beresford@zbdsolutions.com> wrote:
>
>
>> -----Original Message-----
>> From: buildroot-bounces at busybox.net [mailto:buildroot-
>> bounces at busybox.net] On Behalf Of Frank Hunleth
>> Sent: 16 September 2013 02:16
>> To: Thomas Petazzoni
>> Cc: buildroot
>> Subject: Re: [Buildroot] BeagleBoneBlack Updates?
>>
>> On Sat, Sep 14, 2013 at 1:33 AM, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com> wrote:
>> >
>> > Dear Frank Hunleth,
>> >
>> > On Fri, 13 Sep 2013 08:58:27 -0400, Frank Hunleth wrote:
>> > > It's been a while since there's been discussion on the bbb, and I
>> > > wanted to check on the current status. I've been sitting on some
>> > > patches that have been working for me for the past few months. Spenser
>> > > Gilliland had also posted a github reference to his patches a month or
>> > > so ago. As far as I can tell, the main difference is HDMI and graphics
>> > > acceleration are either working or close to working in his tree. I
>> > > don't use either feature.
>> > >
>> > > I don't mind making a pass to clean up what I have and submit it to
>> > > the list, but if work is going on with Spenser's or someone else's
>> > > then I'll hold off.
>> >
>> > I believe Spenser might be busy with the other OpenGL work, so I think
>> > you could probably take your work and his BBB work, and submit patches
>> > to the list. I'd really to see the BBB be an officially supported
>> > platform in Buildroot.
>>
>> Sounds good.
>>
>> I just rebased to the upstream and was pleased to see the updated
>> Linaro compilers. The Beaglebone Debian work uses Linaro 4.8-2013.07,
>> and I had as a todo item to try to match up compilers when I had a
>> chance. Both Spenser and I were using EABI compilers (as opposed to an
>> EABIhf one like Debian.)
>>
>> I tried making the switch to EABIhf, but found out a that init won't
>> start due to not being able to load libc.so.6. I assumed that
>> somewhere I just had a compiler option different so that busybox was
>> being compiled with a slightly different ABI than what Linaro had done
>> with their version of libc. As far as I can tell with readelf, I have
>> both busybox and libc.so.6 reporting ABI 3.1.1 and listing:
>>
>> Attribute Section: aeabi
>> File Attributes
>>   Tag_CPU_name: "7-A"
>>   Tag_CPU_arch: v7
>>   Tag_CPU_arch_profile: Application
>>   Tag_ARM_ISA_use: Yes
>>   Tag_THUMB_ISA_use: Thumb-2
>>   Tag_FP_arch: VFPv3
>>   Tag_Advanced_SIMD_arch: NEONv1
>>   Tag_ABI_PCS_wchar_t: 4
>>   Tag_ABI_FP_rounding: Needed
>>   Tag_ABI_FP_denormal: Needed
>>   Tag_ABI_FP_exceptions: Needed
>>   Tag_ABI_FP_number_model: IEEE 754
>>   Tag_ABI_align_needed: 8-byte
>>   Tag_ABI_align_preserved: 8-byte, except leaf SP
>>   Tag_ABI_enum_size: int
>>   Tag_ABI_HardFP_use: SP and DP
>>   Tag_ABI_VFP_args: VFP registers
>>   Tag_CPU_unaligned_access: v6
>>
>> Right now, I'm not sure where to look for possible other differences.
>> CodeSourcery and the built-in toolchains work fine (albeit with EABI).
>> I was wondering if anyone else has run into issues with EABIhf to
>> might help me debug this.
>>
>
> This is because the new linaro toolchain is expecting to find libc in /lib/arm-linux-gnueabihf/ as reported in https://bugs.busybox.net/show_bug.cgi?id=6452.
>
> There's a patch to adapt toolchain/helpers.mk to the new linaro layout in the attachment to that bug, and I can say that the patch works for me, but I don't know if it would break anything else!
>

Thanks! That was the issue.

Frank