**** BEGIN LOGGING AT Tue Jul 05 02:59:59 2016 Jul 05 07:32:15 I have multiple CAN busses on my SoC configured and in device tree via SPI controllers , they are neatly detected and shown as interfaces in /proc/net/dev, how do I know which inteface is bound to what interface number? They do now follow the labels as I define them in the device tree Jul 05 07:57:25 Ah, I just found that /sys/class/net/can# symlinks to the virtual device tree Jul 05 11:58:52 RagBal: probably fixable with a udev rule Jul 05 12:07:20 zmatt, tell me more =) Jul 05 12:13:04 ideally the kernel would just follow the numbering given in /aliases in the DT (assuming one is given there for can devices, it is in my DT but I don't remember if that's default), but unfortunately the kernel only follows those for a few classes of devices, such as i2c, mmc in recent rcn kernels, and spi after I applied a 2-line kernel patch Jul 05 12:14:58 however an easy workaround would be by adding some property to the DT nodes, like ifname = "can0"; or such Jul 05 12:15:17 then add an udev rule like, eh, lemme see if I can guess this right Jul 05 12:17:22 SUBSYSTEM=="net", ACTION=="add", ATTR{device/of_node/ifname}!="", NAME="%s{device/of_node/ifname}" Jul 05 12:17:44 replace NAME= by NAME:= to prevent later rules from overriding it Jul 05 12:18:06 zmatt, thanks I was looking for something just like that! Jul 05 17:45:43 Anyone know the status on the Beaglebone Blue? Jul 05 21:22:59 Hello people Jul 05 22:02:52 yes... people... that's what we are Jul 05 23:41:37 Hello, I want to boot BeagBoneBlack from uMD and understand that powerloss will reset to eMMC boot. Where do I find instructions to permanently boot from uMD (uEnv.txt?) Jul 06 00:39:35 wilbert - 1) wait around and you might actually get your answer 2) the boot pins are available on the p8/9 headers, and if you look at the appropriate Reference Manuals, you see that you only have to tie one of them up or down to emulate the existing BOOT button on the main board Jul 06 01:40:25 Boot button is better than a boom button I hate it when my electronic stuff explodes. Jul 06 02:30:22 or just clear sector 512 of eMMC Jul 06 02:31:09 (or if using a FAT boot partition remove the MLO file there) Jul 06 02:31:23 that renders eMMC unbootable and ROM will automatically check uSD next Jul 06 02:54:06 hello! i'm having problems getting spi0 to work on my bbb. before initializing the /dev/spidev1.0 interface, pins 17, 18, 21 and 22 all read ~3.2 volts with a true rms multimeter. once i enable it, i get the same results. same if i send a long string of zeros or 0xFF using py-spidev. is my bbb broken? i'm unable to use flashrom with this device, but another bbb i tested works fine. thanks in advance for an Jul 06 02:54:12 y help. :) **** ENDING LOGGING AT Wed Jul 06 02:59:58 2016