**** BEGIN LOGGING AT Wed Apr 17 02:59:57 2019 Apr 17 04:34:26 interesting, never heard of preadv2() and pwritev2() before Apr 17 04:34:31 TIL Apr 17 09:37:52 hello! Apr 17 13:11:27 Hi, I am using the kernel version 4.14, debian 9.5. May I know how to enable UART in uEnv.txt? Apr 17 13:16:36 you've asked that previously, I answered it, you said "ok thanks". if there's some detail that's unclear, ask a more specific question Apr 17 13:18:38 I dont think I have asked this question before. Because I were using 8.7. Everything was working there before Apr 17 13:19:30 I asked you how to enable WiFi and PRU in 8.7 Apr 17 13:19:37 before Apr 17 13:21:53 and I advised you to use the latest image, you mentioned not being able to find the slots file, I explained how things worked on the latest image Apr 17 13:23:33 @zmatt, that conversation is different. Again, you suggested to use latest version because you did not provide solution to make it work in 8.7 Apr 17 13:23:56 https://pastebin.com/Q320etJe Apr 17 13:25:56 The conversation ended with < zmatt> or you could enable their overlays in /boot/uEnv.txt and not have to do anything at runtime. Apr 17 13:26:16 if you want to use an overlay instead of cape-universal then you just stick the path to the dtbo into the "dtb_overlay" variable or one of uboot_overlay_addr4-7 (under the heading "custom capes") Apr 17 13:27:52 (uboot_overlay_addr0-3 would in principle also work, but they're more specifically intended to override the overlay selection of actual physical capes that have a cape identification eeprom) Apr 17 13:30:22 This should work right? uboot_overlay_addr4=/lib/firmware//BB-UART1-00A0.dtbo uboot_overlay_addr5=/lib/firmware/BB-UART4-00A0.dtbo uboot_overlay_addr6=/lib/firmware/BB-SPIDEV1-00A0.dtbo Apr 17 13:31:33 dont need to use this option as before - cape_enable=bone_capemgr.enable_partno=BB-UART1, BB-UART4, BB-SPIDEV1 Apr 17 13:31:41 ? Apr 17 13:33:06 I'm not sure what the purpose is of asking this question. I tell you the answer is to do X. You then ask "so I do X, and not Y?" Why do you ask this question? If it were Y, I would have mentioned Y Apr 17 13:33:59 zmatt, please understand my question Apr 17 13:34:15 previously, these two options were combined Apr 17 13:35:09 now you are asking me to do the X option alone and expecting me to not to ask Y question. Both are related right? Apr 17 13:35:58 plus /boot/uEnv.txt contains examples of all relevant options in comments. do you see "bone_capemgr.enable_partno" anywhere in there? Apr 17 13:36:33 You guys are completely removed slots in new version. Where do I find all these documents? Do you have any set of documentation for kernel 4.14 and 9.5? so that I can refer there instead of asking you Apr 17 13:37:24 nope, but there really isn't anything more to it then already explained Apr 17 13:43:41 Raj_ docs are /boot/uEnv.txt and https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays Apr 17 13:46:57 Thanks zmatt, rcn-ee. Documentation is more general not specific. How do I verify whether the expected UART are enabled like this b. cat /sys/devices/platform/bone_capemgr/slots before? Apr 17 13:51:04 Raj_ if you enabled it in /boot/uEnv.txt, it's "enabled"... The only reason it wouldn't be "enabled" is if you have an ancient version of u-boot on the eMMC blocking u-boot overlays to be loaded.. Apr 17 13:52:00 That's why we have the "sudo /opt/scripts/tools/version.sh" script to check the bootloader version. Apr 17 13:54:45 oh ok, still no way to verify! will check and get back to you if any. Thanks. Apr 17 13:55:14 you can verify the actual pin configuration using my show-pins utility Apr 17 13:55:23 Raj_ there is a very simple to verify, use the peripheral. Apr 17 13:56:58 Raj_ you can also grep/script /proc/device-tree/ and check the node.. Apr 17 13:58:10 For example: cat /proc/device-tree/ocp/serial@*/status Apr 17 14:24:15 m **** BEGIN LOGGING AT Wed Apr 17 22:48:44 2019 **** ENDING LOGGING AT Thu Apr 18 02:59:57 2019