[Buildroot] Tossing coins on Beaglebone Black kernel version

[Buildroot] Tossing coins on Beaglebone Black kernel version

[Ezequiel Garcia]

As mentioned on IRC, beaglebone_defconfig U-Boot build is currently broken.
I don't think the error matters much, given the selected U-Boot version
is really old.

I'm working on fixing it and get a cleaner beaglebone_defconfig. While at it,
I realized the kernel version points to some random commit in some random
TI kernel tree.

As per the commit log:
""
    beaglebone: update to TI 3.12 kernel

    Git repo version is taken from meta-ti.
    It's a 3.12.10 kernel with TI's own patches on top.

    The defconfig has been kept rather close to our old defconfig.
    The kernel has been boot-tested using an NFS-root.

    Apart from the kernel change, the linux headers has also been
    updated from 3.8.12 to 3.12.10.
""

This is highly annoying, as not using a branch or tag prevents a shallow
clone, and so we need to retrieve the entire repo, even to get the
headers for the toolchain.

We are currently using git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
while TI kernel release [1] notes are pointing at
git://git.ti.com/processor-sdk/processor-sdk-linux.git.

Now, I'm not all that sure which kernel we want to use by default and that's
why I'm asking here, to hear what the rest thinks.

FWIW, I commercially support a AM335x product and we've switched to
linux mainline,
long, long time ago, because the SDK was incredibly crappy at that time.

Mainline lacks some important features such as 3D support, and platform
suspend-to-RAM, but it's in my experience less buggy, so I'd vote to
switch to it.

Unless of course, someone knows better and can point at a proper git tag
to use.

[1] http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Kernel_Release_Notes
-- 
Ezequiel Garc?a, VanguardiaSur
www.vanguardiasur.com.ar

[Buildroot] Tossing coins on Beaglebone Black kernel version

[Peter Korsgaard]

>>>>> "Ezequiel" == Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> writes:

 > As mentioned on IRC, beaglebone_defconfig U-Boot build is currently broken.
 > I don't think the error matters much, given the selected U-Boot version
 > is really old.

Yeah, our beaglebone defconfig could really use some love. It looks like
I will be getting a beaglebone green wireless so I was planning on
looking into it as well, but thanks for working on it!

 > We are currently using git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
 > while TI kernel release [1] notes are pointing at
 > git://git.ti.com/processor-sdk/processor-sdk-linux.git.

 > Now, I'm not all that sure which kernel we want to use by default and that's
 > why I'm asking here, to hear what the rest thinks.

What are the beaglebone people using for their official images? Can't we
use the same?


 > FWIW, I commercially support a AM335x product and we've switched to
 > linux mainline,
 > long, long time ago, because the SDK was incredibly crappy at that time.

Yeah, that would be my choice as well for a product. For getting started
on a beaglebone I'm less sure as mainline doesn't have any support for
the various capes.

-- 
Bye, Peter Korsgaard

[Buildroot] Tossing coins on Beaglebone Black kernel version

[Ezequiel Garcia]

On 2 June 2016 at 16:47, Peter Korsgaard <peter@korsgaard.com> wrote:
>>>>>> "Ezequiel" == Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> writes:
>
>  > As mentioned on IRC, beaglebone_defconfig U-Boot build is currently broken.
>  > I don't think the error matters much, given the selected U-Boot version
>  > is really old.
>
> Yeah, our beaglebone defconfig could really use some love. It looks like
> I will be getting a beaglebone green wireless so I was planning on
> looking into it as well, but thanks for working on it!
>

No problem. I wanted to submit the fix for the bootloader for now,
but the git full clone stalled for ages here and drove me mad.

>  > We are currently using git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>  > while TI kernel release [1] notes are pointing at
>  > git://git.ti.com/processor-sdk/processor-sdk-linux.git.
>
>  > Now, I'm not all that sure which kernel we want to use by default and that's
>  > why I'm asking here, to hear what the rest thinks.
>
> What are the beaglebone people using for their official images? Can't we
> use the same?
>

I believe they use this: https://github.com/beagleboard/linux.
It's just a matter of finding what commit/branch/tag they use.

So it's yet another choice :-)

>
>  > FWIW, I commercially support a AM335x product and we've switched to
>  > linux mainline,
>  > long, long time ago, because the SDK was incredibly crappy at that time.
>
> Yeah, that would be my choice as well for a product. For getting started
> on a beaglebone I'm less sure as mainline doesn't have any support for
> the various capes.
>

I'm not sure Buildroot would be the choice for a getting started beaglebone
user, but yeah, it would make sense to support capes properly.
-- 
Ezequiel Garc?a, VanguardiaSur
www.vanguardiasur.com.ar