These are VERY helpful and a meaningful way forward. But these requires
real device-drivers which i dont think we can come close to easily, but not
sure though.
On Fri, Jun 9, 2017 at 5:36 PM, Jason Kridner
wrote:
> I started to create a quick list of using drivers to talk to some modules
> on B
I started to create a quick list of using drivers to talk to some modules
on Blue. (
https://github.com/beagleboard/beaglebone-blue/wiki/One-Liner-Module-Tests).
I think the same thing could be done for MikroBus Clicks pretty easy. If
you think that is useful, I think I could try it for a bunch of
In my case its not about any specific clicks, but maybe supporting a
collaborative effort to contribute drivers to a well-known repository. In
case you have a driver that works, you can share it.
On top of that, it could be nice that all drivers were created in
consistent way so the usage was e
I have a number of Clicks. Many work easier than others. Which ones are of
most interest?
On Wed, Jun 7, 2017 at 9:44 PM Mala Dies wrote:
> Hello...I tried to get the MikroBus Cape up and running. They had some
> info. on the mikroe.com site for specific clicks but you, as I believe,
> would need
Hello...I tried to get the MikroBus Cape up and running. They had some
info. on the mikroe.com site for specific clicks but you, as I believe,
would need the compilers from their site.
Seth
P.S. I tried to get around things but I suck at this game. I kept trying
and to no avail. If I get any c
