The code came from Derek Molloy's Exploring Beaglebone -Tools and Techniques Chapter 9 page 362 Listing 9-10. Regarding a decent book on how to spidev have you any recommendations? I am the first to admit I am a novice and it goes without saying that we all started somewhere as frustrating as that is. So to recap add code to trace code? That sounds like a plan. All aside the real question on my mind is that I would like to rule out that there is not something else going on here with the device tree overlays that I would not be aware of? It would be helpful at this end if a guy knew where to look for updates (i.e. the source) and had a listing of what they were or how they might affect things downstream. I know how ridiculous that must sound in that Linux is an open source community backed by volunteers nonetheless I am not clear on the structure on how things come together and as such I find it utterly amazing that things work. I understand that Robert has had a big hand in it and there are many others, but I am not sure on how it all comes together. Thanks for the input no offense taken.
-- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
