On Wed, Mar 27, 2019 at 11:32 AM Daniel Kulp <[email protected]> wrote: > > > Couple of questions regarding the bone kernels.... > > 1) Is there a reason update_kernel doesn't install the various "extras" for > the bone kernel like it does for the ti kernels? I don't really care as I > don't need them, but it kind of surprised me that libpruio and such were not > installed.
https://github.com/RobertCNelson/boot-scripts/blob/2f062cfde221878a2bcb4ea87d0622aab74728e0/tools/update_kernel.sh#L565-L567 So yes, this should be extended to 4.19.x-bone, v4.14.x-bone-rt and v4.19.x-bone-rt.. > 2) Is there any indication if/when the problem of BB-I2C2-FAST-00A0 not > allowing cape-universal to work will be fixed for the bone kernels? At least > for 4.19 but preferably also for 4.14. I'm kind of working around the issue > by explicitly adding cape-universalh-00A0 to the overlays, but that's kind of > a crappy way to do it. This "works" fine in 4.19.x, the issue is you want me to spend time back-porting this feature i originally started working in on v4.16.x-bone back to v4.14.x-bone.. My big question is why? everyone hated v4.14.x-bone-rt so they either stayed on v4.4.x-bone-rt or now jumped to 4.19.x-bone-rt.. Thus give me an actual use case why v4.14.x-bone vs v4.19.x-bone at this point.. debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh git:/opt/scripts/:[2f062cfde221878a2bcb4ea87d0622aab74728e0] eeprom:[A335BNLT000C1830BBBG0785] model:[TI_AM335x_BeagleBone_Black] dogtag:[BeagleBoard.org Debian Image 2019-03-24] bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g9d95a561c9]:[location: dd MBR] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR] kernel:[4.19.29-bone29] nodejs:[v6.17.0] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C2-FAST-00A0.dtbo] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] uboot_overlay_options:[enable_uboot_cape_universal=1] pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>] pkg:[bb-cape-overlays]:[4.4.20190320.1-0rcnee0~stretch+20190320] pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227] pkg:[kmod]:[23-2rcnee1~stretch+20171005] pkg:[librobotcontrol]:[1.0.4-git20190107.0-0rcnee0~stretch+20190108] pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217] groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai] cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] dmesg | grep remote [ 1.035641] remoteproc remoteproc0: wkup_m3 is available [ 1.387562] remoteproc remoteproc0: powering up wkup_m3 [ 1.387582] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168 [ 1.390364] remoteproc remoteproc0: remote processor wkup_m3 is now up dmesg | grep pru debian@beaglebone:~$ config-pin -l P9.11 default gpio gpio_pu gpio_pd gpio_input uart debian@beaglebone:~$ config-pin -q P9.11 P9_11 Mode: default Direction: in Value: 1 debian@beaglebone:~$ config-pin P9.11 uar > > Related to #2: if we include BB-I2C2-FAST-00A0 , then it excludes those pins > from cape-universal/pinmux entirely. Thus, we cannot "config-pin" them to > be output pins if we don't need the i2c bus. I've created my own dts that > only configures the i2c clock and leaves the pins alone. I'm trying to > determine if there are any issues with that, and if not, why isn't that the > default? > Regards, -- Robert Nelson https://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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhzgySsZu3UW1LWrfDL1NaJuqkNG_%2BQjmvTzWj4vOa%2BEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
