Thanks, for the responses, let me clarify the problem. In 4.1.1 i have been using overlays from " https://github.com/RobertCNelson/bb.org-overlays"; and everything was working fine for the last year or so except the power button ( i gave up on this and don't remember the details, but issue was something about the power button device in /dev/ or /sys missing, and acpid not receiving any signal from the button )
so i have working system with 4.1.1 ( except the power button, which is a minor issue ). i have recently upgraded, ONLY the kernel ( and modules, and firmware ) to 4.1.22, ( also later updated overlays from bb.org-overlays ) and now the power button works fine, but /dev/spidevX.X is dead. *if i simply boot the old kernel, spidev comes back to life*. again, from the system's point of view, on 4.1.22 everything is fine, spidev exists and i can use it, however no electrons are present on the physical spi pins. Other overlays from bb.org-overlays are working fine on 4.1.22 Best Regards. 2016-04-29 18:40 GMT+02:00 Robert Nelson <[email protected]>: > > > On Fri, Apr 29, 2016 at 11:08 AM, Grzesiek Stawik <[email protected]> > wrote: > >> So i had this other issue where the power button would not trigger >> poweroff, and from time to time i try new kernel versions to see if it >> works, and i have recently switched to 4.1.22 because it does work there. >> >> But. >> >> Strange things happen with SPI in 4.1.22, spidev is now created as >> /dev/spidev2.X instead /dev/spidev1.X, or, when using "cape-universal" >> overlay, i get both /dev/spidev1.X and /dev/spidev2.X but none of them are >> working. >> > > "cape-universal" just enables the peripheral out of the box.. > > When using it, you need to use "config-pin" to mux the pin's utilized.. > > Here is the readme: > > > https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/README.md > > the 'overlay' is already loaded by default.. you just need to use > config-pin to setup the spidev pin's.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/QiFPB9HjL4Y/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CAOCHtYjrj9NUz7bD%3D6ASAy%2BUvijyRbRbjadeY0P0Xmq34TL4-g%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CAOCHtYjrj9NUz7bD%3D6ASAy%2BUvijyRbRbjadeY0P0Xmq34TL4-g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFOeQMzxUh_kLbe%3D1nTQvYprkpuY_mrZj7f6wDY9vxs2Cu4bUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
