Hi! > @@ -0,0 +1,27 @@ > +What: /dev/jtag[0-9]+ > +Date: October 2017 > +KernelVersion: 4.15 > +Contact: oleksandrs@xxxxxxxxxxxx > +Description: > + The misc device files /dev/jtag* are the interface > + between JTAG master interface and userspace. > + > + The ioctl(2)-based ABI is defined and documented in > + [include/uapi]<linux/jtag.h>. > + > + The following file operations are supported: > + > + open(2) > + The argument flag currently support only one access > + mode O_RDWR. > + > + ioctl(2) > + Initiate various actions. > + See the inline documentation in [include/uapi]<linux/jtag.h> > + for descriptions of all ioctls. I tried reading the jtag.h, and am still not sure how it works. Real docs would be nice... In particular, it seems to always specify read or write actiom. Sounds like a job for read/write syscalls? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
