Rick, also for what it's worth. Getting it compiled and working on a system does seem very straight forward and is shown step by step on that landing page you linked to.
On Thu, Oct 8, 2015 at 9:30 PM, William Hermans <[email protected]> wrote: > Not sure I understand what you're getting at, but I've read that iio has > at least two methods of access. Slow( sysfs ), and fast( mmap()). I'm not > sure that the "fast" method driver exists for our board here in the context > of the ADC's but certainly the slow sysfs method does. As for the rest of > the things mentioned on that landing page you pasted a link to . . . it > seems that he steps are very straight forward to get working, and indeed > laid out on that exact page. > > What are you wanting to do with iio ? The idea of the library does > intrigue me too. But I'm, not exactly sure I have the time to learn > yet-another-abstraction-layer . . . > > On Thu, Oct 8, 2015 at 8:37 PM, Rick Mann <[email protected]> wrote: > >> libiio (along with additional stuff in the kernel that doesn't appear to >> be in 4.1.x-ti) provides for fast ADC access, rather than getting at it >> through sysfs. >> >> > On Oct 8, 2015, at 20:07 , William Hermans <[email protected]> wrote: >> > >> > I believe the ADC already uses a libiio "driver". Assuming it is the >> same thing I'm thinking of. But for instance when you load the ADC device >> tree file, it in turn loaded the iio:device0 object for the ADC. >> > >> > Like demonstrated on my blog post here: >> http://www.embeddedhobbyist.com/2015/10/beaglebone-black-adc/ >> > >> > With that said, I do not purport to know very much about it. Just that >> it exists. >> > >> > On Thu, Oct 8, 2015 at 7:06 PM, Rick Mann <[email protected]> >> wrote: >> > What would it take to get libiio: >> > >> > >> https://wiki.analog.com/resources/tools-software/linux-software/libiio >> > >> > Into the BBB kernels? I think this would be amazing. >> > >> > >> > -- >> > Rick Mann >> > [email protected] >> > >> > >> > -- >> > 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]. >> > 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]. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> Rick Mann >> [email protected] >> >> >> -- >> 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]. >> 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]. For more options, visit https://groups.google.com/d/optout.
