Linux Kernel tree for porting to mailine and basic support.

[minde...@gmail.com]

Hi,

What is the Linux kernel tree which is used to provide mainline support for the beaglebone black? I would like to contribute towards mainlining and I would like to know which is the tree for which the beaglebone black development happens.

I am assuming the tree is  https://github.com/beagleboard/linux. Please correct me if I am wrong.

Thanks in advance,
Gautam.

[din...@gmail.com]

Hi,

I think https://github.com/beagleboard/linux would be the best reference tree.

Which subsystem are you going to mainline? 

Regards,
Dimitar

[Drew Fustini]

Robert Nelson's Supercon workshop material is useful if you want to learn about the the repositories used for the bootloader and kernel that ships on the official Debian images:

https://github.com/RobertCNelson/Supercon-2017-PocketBeagle?files=1

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/bc2b6c30-c910-4ae5-bf11-d54a93e13341%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Drew Fustini]

If you are curious about the patches applied on top of mainline, then check out this directory from Robert's ti-linux-kernel-dev repo:

https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.14.y/patches

One out of tree driver that would great to mainline is the pinmux helper which is critical to how our config-pin utility works:

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.14.y/patches/drivers/ti/gpio/0001-BeagleBone-pinmux-helper.patch

On Nov 25, 2017 10:02 PM, <minde...@gmail.com> wrote:

--

[William Hermans]

Any video of that workshop ? All I saw from hackaday was Sammy Kamkar etc, regurgitated video . . .

[Robert Nelson]

On Tue, Nov 28, 2017 at 2:36 PM, William Hermans <yyr...@gmail.com> wrote:
> Any video of that workshop ? All I saw from hackaday was Sammy Kamkar etc,
> regurgitated video . . .

They only had camera's on the inside, we were outside in the tent.
Most of it was just me running around troubleshooting while everyone
worked their way thru the presentation..

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Graham]

The notes on GitHub say to only use VM VirtualBox 5.1.x and to not use 5.2.x.

Is that because 5.2 was too new and unstable at the time? Or is there a fundamental issue with VM Virtualbox 5.2?

--- Graham

==

[Robert Nelson]

Those notes are just for windows users. At the time of the lab,
5.2."0" had major issues.. At the time 5.1.30 just worked...

Linux users can just git clone and move thru the lecture..

[minde...@gmail.com]

On Wednesday, November 29, 2017 at 1:09:37 AM UTC+5:30, din...@gmail.com wrote:

Hi,

I think https://github.com/beagleboard/linux would be the best reference tree.

Which subsystem are you going to mainline? 

Regards,
Dimitar

Hi Dimitar,

I have not decided on anything to mainline as of now as I am new to BBB.  So the first step is to build the kernel from the right tree (which itself is confusing) and see where I can improve. At least try to solve simple problems and then move on to harder stuff. I will also start documenting stuff as I go along.

Working on the i.mx6 and i.mx7 I find the approach of NXP better where I can just "git pull" from the NXP source tree and build the kernel rather than apply a set of patches using a script. Submissions of patches would be to the i.mx maintainers which would be eventually mainlined.

Thanks,

Gautam.

[Robert Nelson]

> Hi Dimitar,
>
> I have not decided on anything to mainline as of now as I am new to BBB. So
> the first step is to build the kernel from the right tree (which itself is
> confusing) and see where I can improve. At least try to solve simple
> problems and then move on to harder stuff. I will also start documenting
> stuff as I go along.
>
> Working on the i.mx6 and i.mx7 I find the approach of NXP better where I can
> just "git pull" from the NXP source tree and build the kernel rather than
> apply a set of patches using a script. Submissions of patches would be to
> the i.mx maintainers which would be eventually mainlined.

We "are not" TI...

TI does the same thing, you can go grab their tree here:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.14.y

or:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.9.y

or:

http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.4.y

and they push things mainline..

We just use it as a base for BeagleBoard.org and then include things
that have been rejected multple times on mainline, but our users use.

[minde...@gmail.com]

Hi Robert,

I had build the https://github.com/beagleboard/linux before using arm-none-eabi-gcc before successfully. After the move to Artful in Ubuntu and using the arm-none-eabi-gcc Version 5.4.1 the compiler crashes while compiling the source. It does not crash when I build Torvalds mainline. I am not sure what the problem is here.

I am aware that you use the arm-linux-gnueabihf-gcc. Does building using arm-none-eabi-gcc cause any problems?

Thanks,

Gautam.

[Robert Nelson]

> Hi Robert,
>
> I had build the https://github.com/beagleboard/linux before using
> arm-none-eabi-gcc before successfully. After the move to Artful in Ubuntu
> and using the arm-none-eabi-gcc Version 5.4.1 the compiler crashes while
> compiling the source. It does not crash when I build Torvalds mainline. I am
> not sure what the problem is here.
>
> I am aware that you use the arm-linux-gnueabihf-gcc. Does building using
> arm-none-eabi-gcc cause any problems?

it builds fine natively with ubuntu artful:

http://gfnd.rcn-ee.org:81//farm/deb/COMPLETE-4.9.65-ti-r80-artful-armhf.txt

Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
7.2.0-8ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=arm-linux-gnueabihf- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libitm --disable-libquadmath --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-objc-gc=auto --enable-multiarch --enable-multilib
--disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16
--with-float=hard --with-mode=thumb --disable-werror --enable-multilib
--enable-checking=release --build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-8ubuntu3)

[Gautam Bhat]

Robert,

For the arm-eabi- I get the following error:
https://pastebin.com/iVmG18Xk

​For the Artful arm-none-eabi- I get the same above error​ with the compiler segfaulting.

I have filed a compiler bug here:

https://bugs.launchpad.net/ubuntu/+source/gcc-arm-none-eabi/+bug/1734420

Please see the apport attachment for the trace of compiler crash.

​The git tree is: https://github.com/beagleboard/linux​

​Thanks,

Gautam.​

On Sat, Dec 2, 2017 at 11:58 PM, Robert Nelson <robert...@gmail.com> wrote:

Can you please pastebin the build error.

Regards,

On Dec 2, 2017 11:21 AM, "Gautam Bhat" <minde...@gmail.com> wrote:

Hi Robert,

The build fails using the baremetal EABI in Artful or the Linaro
baremetal eabi binaries.  The build used to work fine before for the
baremetal eabi's.

The eabi in Artful is:

arm-none-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-none-eabi/5.4.1/lto-wrapper
Target: arm-none-eabi
Configured with: ../src/configure --build=x86_64-linux-gnu
--prefix=/usr --includedir='/usr/lib/include'
--mandir='/usr/lib/share/man' --infodir='/usr/lib/share/info'
--sysconfdir=/etc --localstatedir=/var --disable-silent-rules
--libdir='/usr/lib/lib/x86_64-linux-gnu'
--libexecdir='/usr/lib/lib/x86_64-linux-gnu' --disable-maintainer-mode
--disable-dependency-tracking --mandir=/usr/share/man
--enable-languages=c,c++,lto --enable-multilib --disable-decimal-float
--disable-libffi --disable-libgomp --disable-libmudflap
--disable-libquadmath --disable-libssp --disable-libstdcxx-pch
--disable-nls --disable-shared --disable-threads --disable-tls
--build=x86_64-linux-gnu --target=arm-none-eabi --with-system-zlib
--with-gnu-as --with-gnu-ld --with-pkgversion=15:5.4.1+svn241155-1
--without-included-gettext --prefix=/usr/lib
--infodir=/usr/share/doc/gcc-arm-none-eabi/info
--htmldir=/usr/share/doc/gcc-arm-none-eabi/html
--pdfdir=/usr/share/doc/gcc-arm-none-eabi/pdf --bindir=/usr/bin
--libexecdir=/usr/lib --libdir=/usr/lib --disable-libstdc++-v3
--host=x86_64-linux-gnu --with-headers=no --without-newlib
--with-multilib-list=armv6-m,armv7-m,armv7e-m,armv7-r CFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2'
CXXFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' FCFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' FFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' GCJFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' LDFLAGS='-Wl,-Bsymbolic-functions
-Wl,-z,relro' OBJCFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong' OBJCXXFLAGS='-g -O2
-fdebug-prefix-map=/build/gcc-arm-none-eabi-509sty/gcc-arm-none-eabi-5.4.1+svn241155=.
-fstack-protector-strong'
INHIBIT_LIBC_CFLAGS=-DUSE_TM_CLONE_REGISTRY=0
AR_FOR_TARGET=arm-none-eabi-ar AS_FOR_TARGET=arm-none-eabi-as
LD_FOR_TARGET=arm-none-eabi-ld NM_FOR_TARGET=arm-none-eabi-nm
OBJDUMP_FOR_TARGET=arm-none-eabi-objdump
RANLIB_FOR_TARGET=arm-none-eabi-ranlib
READELF_FOR_TARGET=arm-none-eabi-readelf
STRIP_FOR_TARGET=arm-none-eabi-strip
Thread model: single
gcc version 5.4.1 20160919 (15:5.4.1+svn241155-1)


Linaro eabi:

Using built-in specs.
COLLECT_GCC=arm-eabi-gcc
COLLECT_LTO_WRAPPER=/home/mindentropy/beagleboneblack/tool_chain/linaro/gcc-linaro-7.2.1-2017.11-x86_64_arm-eabi/bin/../libexec/gcc/arm-eabi/7.2.1/lto-wrapper
Target: arm-eabi
Configured with:
'/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-7.2-2017.11/configure'
SHELL=/bin/bash
--with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu
--with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu
--with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu
--with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto
--enable-shared --without-included-gettext --enable-nls
--disable-sjlj-exceptions --enable-gnu-unique-object
--enable-linker-build-id --disable-libstdcxx-pch --enable-c99
--enable-clocale=gnu --enable-libstdcxx-debug --enable-long-long
--with-cloog=no --with-ppl=no --with-isl=no --enable-multilib
--with-multilib-list=aprofile --enable-threads=no --disable-multiarch
--with-newlib --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/sysroots/arm-eabi
--with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu/arm-eabi/libc
--enable-checking=release --disable-bootstrap
--enable-languages=c,c++,lto --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu --target=arm-eabi
--prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu
Thread model: single
gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)

Thanks,
Gautam.

[minde...@gmail.com]

On Wednesday, November 29, 2017 at 1:36:56 AM UTC+5:30, Drew Fustini wrote:

If you are curious about the patches applied on top of mainline, then check out this directory from Robert's ti-linux-kernel-dev repo:

https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.14.y/patches

One out of tree driver that would great to mainline is the pinmux helper which is critical to how our config-pin utility works:

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.14.y/patches/drivers/ti/gpio/0001-BeagleBone-pinmux-helper.patch

Hi Drew,

I finished the build of the both the trees mentioned above and have documented it in my blog with the problems with different tool chains. Now that I have a working setup let me see the patches and also the pinmux patches. Should I use the same thread to discuss about this or create a new topic to discuss this? I would definitely need some help understanding things till I am used to it. I will be documenting things in my blog as I go along.

Thanks,

Gautam.

[Drew Fustini]

On Mon, Dec 11, 2017 at 3:00 AM, <minde...@gmail.com> wrote:
> Hi Drew,
>
> I finished the build of the both the trees mentioned above and have
> documented it in my blog with the problems with different tool chains. Now
> that I have a working setup let me see the patches and also the pinmux
> patches. Should I use the same thread to discuss about this or create a new
> topic to discuss this? I would definitely need some help understanding
> things till I am used to it. I will be documenting things in my blog as I go
> along.
>
> Thanks,
> Gautam.

Hi, sorry, I overlooked this email until now. Please start a new
thread if you're still having issues.

Thanks,
Drew