Re: [Machinekit] Re: Universal-Universal Cape Overlay [was: BeagleBone Family MachineKit image]
The link is very confusing the header says 04-02 but it links to 02-12. However, there is no mentioning of any kernel version. Am Donnerstag, 23. März 2017 18:36:01 UTC+1 schrieb Charles Steinkuehler: > > On 3/23/2017 9:44 AM, alexander...@zuehlke.com wrote: > > Are there any Jessie + 3.8 kernel Machinekit images? > > There are many. RCN just switched his builds to a 4.x kernel, but this > image should still have 3.8: > > > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28machinekit.29_Based_on_Debian_Jessie > > > > If I downgrade the > > kernel of the 03-19 image with 4.4 Xenomai preinstalled the cape > universal > > overlays will break unless I downgrade them too, correct? > > The overlays are compiled into the kernel, so should still work. > > -- > Charles Steinkuehler > cha...@steinkuehler.net > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Universal-Universal Cape Overlay [was: BeagleBone Family MachineKit image]
On 3/23/2017 9:44 AM, alexander.roess...@zuehlke.com wrote: > Are there any Jessie + 3.8 kernel Machinekit images? There are many. RCN just switched his builds to a 4.x kernel, but this image should still have 3.8: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28machinekit.29_Based_on_Debian_Jessie > If I downgrade the > kernel of the 03-19 image with 4.4 Xenomai preinstalled the cape universal > overlays will break unless I downgrade them too, correct? The overlays are compiled into the kernel, so should still work. -- Charles Steinkuehler char...@steinkuehler.net -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Universal-Universal Cape Overlay [was: BeagleBone Family MachineKit image]
Regarding 4.4 and the HDMI-audio pin issue: Setting the correct overlay in the uEnv.txt did solve the problem: ##BeagleBone Black: HDMI Audio/eMMC disabled: dtb=am335x-boneblack-nhdmi-overlay.dtb However, Machinekit is not compatible with Xenomai 3.0 and additionally, the hal_pru_generic component seems not work with the 4.4 kernel without any modification to the code. So we will be stuck with the 3.8 kernel with Machinekit right now. Are there any Jessie + 3.8 kernel Machinekit images? If I downgrade the kernel of the 03-19 image with 4.4 Xenomai preinstalled the cape universal overlays will break unless I downgrade them too, correct? Am Mittwoch, 22. März 2017 16:35:30 UTC+1 schrieb Charles Steinkuehler: > > On 3/22/2017 9:53 AM, Robert Nelson wrote: > >> > >> Now I'm wondering about managing the repositories. It really feels > like > >> your bb.org-overlays is "upstream" for the device tree files, but IIRC > >> you're still pulling config-pin from my repo. Is that correct? > > > > I've recently imported your config-pin script, into bb.org-overlays > > > > > https://github.com/beagleboard/bb.org-overlays/tree/master/tools/beaglebone-universal-io > > > > > and now it's part of the bb-cape-overlay debian/ubuntu package, so > > users can have a small image with config-pin and don't need to install > > the git package to clone the repo for the script.. > > Excellent! I'll consider this to be the "upstream" for config-pin from > now on. > > ...looks like the README needs some updating to reflect the new state of > things. If I get enough time waiting on FPGA builds I'll see if I can > send a PR. > > >> Perhaps config-pin should be promoted to it's own project with it's own > >> repo (maybe even under the beagleboard umbrella) and my existing > >> beaglebone-universal-io repo with overlays can be deprecated or > >> relegated to use with 3.8 kernels only? Got any better ideas? > > > > my only idea was to leave your repo 3.8.x only (we will probally be > > supporting 3.8.x for ever ;) ) > > I think that makes the most sense. And yes, 3.8.x will likely be > supported forever...I'm working with some of the SoC+FPGA chips which > still want to run on 3.8 (or even earlier kernels!) despite all > the nifty new FPGA configuration management available in the newer 4.x > kernels. > > I'll put a notice on my repo that it's deprecated (only supports kernel > 3.8.x and only accepting bug-fixes) and point folks to your beagleboard > repos for anything newer. > > -- > Charles Steinkuehler > cha...@steinkuehler.net > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Universal-Universal Cape Overlay [was: BeagleBone Family MachineKit image]
On 3/22/2017 9:53 AM, Robert Nelson wrote: >> >> Now I'm wondering about managing the repositories. It really feels like >> your bb.org-overlays is "upstream" for the device tree files, but IIRC >> you're still pulling config-pin from my repo. Is that correct? > > I've recently imported your config-pin script, into bb.org-overlays > > https://github.com/beagleboard/bb.org-overlays/tree/master/tools/beaglebone-universal-io > > and now it's part of the bb-cape-overlay debian/ubuntu package, so > users can have a small image with config-pin and don't need to install > the git package to clone the repo for the script.. Excellent! I'll consider this to be the "upstream" for config-pin from now on. ...looks like the README needs some updating to reflect the new state of things. If I get enough time waiting on FPGA builds I'll see if I can send a PR. >> Perhaps config-pin should be promoted to it's own project with it's own >> repo (maybe even under the beagleboard umbrella) and my existing >> beaglebone-universal-io repo with overlays can be deprecated or >> relegated to use with 3.8 kernels only? Got any better ideas? > > my only idea was to leave your repo 3.8.x only (we will probally be > supporting 3.8.x for ever ;) ) I think that makes the most sense. And yes, 3.8.x will likely be supported forever...I'm working with some of the SoC+FPGA chips which still want to run on 3.8 (or even earlier kernels!) despite all the nifty new FPGA configuration management available in the newer 4.x kernels. I'll put a notice on my repo that it's deprecated (only supports kernel 3.8.x and only accepting bug-fixes) and point folks to your beagleboard repos for anything newer. -- Charles Steinkuehler char...@steinkuehler.net -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
