Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Robert Nelson robertcnel...@gmail.com writes: So the -bone is close to mainline (small # of patches). The -ti we are a basing on a ti branch: (git.ti.com, patchset 20Mb).. Plus the 'debian' linux-image-armmp will also work once we switch to jessie.. (you can even install ubuntu's linux-image *.deb) the bootloader will find it. v3.14-ti repo: https://github.com/beagleboard/linux/tree/3.14 How do you go about generating the .debs? There doesn't appear any packaging in the beagleboard/linux tree and the .debs don't appear to have corresponding source debs. Cheers, - Ben pgpaFt1lV4dKt.pgp Description: PGP signature
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Robert Nelson robertcnel...@gmail.com writes: On Fri, Sep 12, 2014 at 4:08 PM, Ben Gamari b...@smart-cactus.org wrote: Robert Nelson robertcnel...@gmail.com writes: So the -bone is close to mainline (small # of patches). The -ti we are a basing on a ti branch: (git.ti.com, patchset 20Mb).. Plus the 'debian' linux-image-armmp will also work once we switch to jessie.. (you can even install ubuntu's linux-image *.deb) the bootloader will find it. v3.14-ti repo: https://github.com/beagleboard/linux/tree/3.14 How do you go about generating the .debs? There doesn't appear any packaging in the beagleboard/linux tree and the .debs don't appear to have corresponding source debs. We are using the in-tree make deb-pkg Thanks for the thorough reply! Cheers, - Ben pgpgpKpOJ0Qix.pgp Description: PGP signature
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Jason Kridner jkrid...@beagleboard.org writes: It is time to make another big software push for BeagleBone Black. We have several recent updates from Robert, including managing the kernel as Debian packages. To try out the new code, use one of the recent images from: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 Then, you'll need to switch to the 3.14 kernel: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 It seems like this image has a greatly reduced set of modules (namely the `rt2x00` driver isn't built, although looking at the .config diff it looks like many drivers are omitted). Could the build configuration be modified to include a wider breadth of drivers? Out of curiosity, currently apt knows of three kernel series (run on a 2014-09-03 installation): `-ti`, `-bone`, and what is presumably the unsuffixed Debian upstream kernels. From what trees do these builds originate? Who maintains them? I guess the `-ti` kernel is new preferred kernel? Cheers, - Ben pgp5OWcUXijrw.pgp Description: PGP signature
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Robert Nelson robertcnel...@gmail.com writes: On Fri, Sep 12, 2014 at 12:21 PM, Ben Gamari bgamari.f...@gmail.com wrote: Jason Kridner jkrid...@beagleboard.org writes: It is time to make another big software push for BeagleBone Black. We have several recent updates from Robert, including managing the kernel as Debian packages. To try out the new code, use one of the recent images from: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 Then, you'll need to switch to the 3.14 kernel: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 It seems like this image has a greatly reduced set of modules (namely the `rt2x00` driver isn't built, although looking at the .config diff it looks like many drivers are omitted). Could the build configuration be modified to include a wider breadth of drivers? enabled them last week: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r19 Oops, should have checked this. ( i need to add a : linux-image-bb.org-v3.14-meta-package ) Out of curiosity, currently apt knows of three kernel series (run on a 2014-09-03 installation): `-ti`, `-bone`, and what is presumably the unsuffixed Debian upstream kernels. From what trees do these builds originate? Who maintains them? I guess the `-ti` kernel is new preferred kernel? So the -bone is close to mainline (small # of patches). The -ti we are a basing on a ti branch: (git.ti.com, patchset 20Mb).. Plus the 'debian' linux-image-armmp will also work once we switch to jessie.. (you can even install ubuntu's linux-image *.deb) the bootloader will find it. v3.14-ti repo: https://github.com/beagleboard/linux/tree/3.14 Thanks for the clarifcation! Cheers, - Ben pgptraa_kQsMW.pgp Description: PGP signature
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
On Fri, Sep 12, 2014 at 4:08 PM, Ben Gamari b...@smart-cactus.org wrote: Robert Nelson robertcnel...@gmail.com writes: So the -bone is close to mainline (small # of patches). The -ti we are a basing on a ti branch: (git.ti.com, patchset 20Mb).. Plus the 'debian' linux-image-armmp will also work once we switch to jessie.. (you can even install ubuntu's linux-image *.deb) the bootloader will find it. v3.14-ti repo: https://github.com/beagleboard/linux/tree/3.14 How do you go about generating the .debs? There doesn't appear any packaging in the beagleboard/linux tree and the .debs don't appear to have corresponding source debs. We are using the in-tree make deb-pkg After i push a tag to: https://github.com/beagleboard/linux/ Like: 3.14.17-ti-r19 https://github.com/beagleboard/linux/tree/3.14.17-ti-r19 I'll fire off a native build (wheezy *.deb is built in a clean wheezy chroot) fakeroot make -j5 ARCH=arm LOCALVERSION=-ti-r19 CROSS_COMPILE= KDEB_PKGVERSION=1wheezy KBUILD_DEBARCH=armhf deb-pkg This generates: linux-headers-3.14.17-ti-r19_1wheezy_armhf.deb linux-image-3.14.17-ti-r19_1wheezy_armhf.deb linux-libc-dev_1wheezy_armhf.deb (and) (which i haven't enabled in the 3.14 branch) linux-firmware-image-3.16.2-armv7-lpae-x2_1jessie_armhf.deb linux-headers-* linux-firmware-image-* linux-image-* get pushed to repos.rcn-ee.net (reprepro) linux-libc-dev_1wheezy_armhf.deb - /dev/null So unfortunately the src package is not generated via make deb-pkg thus we rely on the git tag's.. PS you can build a *.deb via cross on x86: make -j5 ARCH=arm LOCALVERSION=-gitsha CROSS_COMPILE=bin/arm-cross- KDEB_PKGVERSION=1cross KBUILD_DEBARCH=armhf deb-pkg Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
So, at this point in time. What can we expect that is better with 3.14 versus 3.8 ? I do not personally have a problem using #include for various capes if need be, but I am wondering if USB hotplug, and / or if USB support is better. As was with 3.15. On Wed, Sep 10, 2014 at 5:42 PM, Cedric Malitte cedric.mali...@gmail.com wrote: Thanks for posting, I'll try that ;) -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
On Wed, Sep 10, 2014 at 8:02 PM, William Hermans yyrk...@gmail.com wrote: So, at this point in time. What can we expect that is better with 3.14 versus 3.8 ? I do not personally have a problem using #include for various capes if need be, but I am wondering if USB hotplug, and / or if USB support is better. As was with 3.15. usb/ethernet/pm is better. Right now we are integrating Charles's universal pinmux, which will allow you to 'mux' enabled peripherals on the fly. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Thanks Robert. pm == power management ? If so how is it better ? On Wed, Sep 10, 2014 at 6:31 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Sep 10, 2014 at 8:02 PM, William Hermans yyrk...@gmail.com wrote: So, at this point in time. What can we expect that is better with 3.14 versus 3.8 ? I do not personally have a problem using #include for various capes if need be, but I am wondering if USB hotplug, and / or if USB support is better. As was with 3.15. usb/ethernet/pm is better. Right now we are integrating Charles's universal pinmux, which will allow you to 'mux' enabled peripherals on the fly. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
On Wed, Sep 10, 2014 at 8:41 PM, William Hermans yyrk...@gmail.com wrote: Thanks Robert. pm == power management ? If so how is it better ? echo mem /sys/power/state actually works.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
Very nice. thanks Robert. On Wed, Sep 10, 2014 at 6:46 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Sep 10, 2014 at 8:41 PM, William Hermans yyrk...@gmail.com wrote: Thanks Robert. pm == power management ? If so how is it better ? echo mem /sys/power/state actually works.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
*The device tree overlay support is still under development as is* * built-in 'config-pin/cape-universal' support, so static configuration* * of the .dtb is currently required. Your help is requested to make sure* * the default .dtb file includes as many configurations as possible that* * can be enabled from userspace.* Would it not be prudent to at least provide *some* mechanism to disable / enable device tree files. Before moving to the next latest greatest ? Sure, hacking the main firmware file works I suppose, but that is not a real solution. On Sun, Aug 17, 2014 at 6:26 PM, Jason Kridner jkrid...@beagleboard.org wrote: It is time to make another big software push for BeagleBone Black. We have several recent updates from Robert, including managing the kernel as Debian packages. To try out the new code, use one of the recent images from: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 Then, you'll need to switch to the 3.14 kernel: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 Report issues to one of these trackers: https://github.com/beagleboard/linux http://bugs.elinux.org/projects/debian-image-releases The device tree overlay support is still under development as is built-in 'config-pin/cape-universal' support, so static configuration of the .dtb is currently required. Your help is requested to make sure the default .dtb file includes as many configurations as possible that can be enabled from userspace. Update summary: * Repo moved to https://github.com/beagleboard/linux * Layout of Debian images now enable 'apt-get' updates to the kernel, but you need to grab a newer starting distro image * The false-start on the cape-firmware repo has been abandoned and device tree overlays are now part of the kernel tree * The kernel currently uses DMA for the USB and includes SGX support I've setup a buildbot hosted at http://builds.beagleboard.org, but I'm still working on getting it to handle pull requests, multiple branches, etc. like the MachineKit folks are doing, as well as pushing out the builds. After a bit more feedback, I'll push out some blog posts, etc. to get more people involved. Thanks for your help! -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black switching to 3.14 kernel
On Mon, Aug 18, 2014 at 5:40 AM, William Hermans yyrk...@gmail.com wrote: The device tree overlay support is still under development as is built-in 'config-pin/cape-universal' support, so static configuration of the .dtb is currently required. Your help is requested to make sure the default .dtb file includes as many configurations as possible that can be enabled from userspace. Would it not be prudent to at least provide *some* mechanism to disable / enable device tree files. Before moving to the next latest greatest ? Sure, hacking the main firmware file works I suppose, but that is not a real solution. We are going to try and do as much as possible in userspace, using idea's from Charles's universal pinmux. For stuff that we can't use that for, we are doing: https://github.com/beagleboard/linux/blob/3.14/arch/arm/boot/dts/am335x-boneblack.dts#L30 Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
