On Monday, November 18, 2013 8:29:24 PM Greg KH wrote: > On Mon, Nov 18, 2013 at 08:19:38PM +0000, Luke-Jr wrote: > > My software does not interface with keyboards under any condition. > > > > Some specific devices I'm working with include: > > FTDI: Avalon, Butterfly Labs BitFORCE & BitFORCE SC, The Chili > > CP210X: Bitfountain Block Erupter Emerald/Sapphire > > CDC/ACM: Big Picture Mining, BTCFPGA ModMiner > > PL2303: Icarus > > How can you control them through libusb? Why not just use the tty > device the kernel exports for you? Right, I got distracted writing this part. I'm only really using libusb as a fallback for HID devices (since hidapi has support already)... HID: NanoFury and HashBuster nano > > > And why not just use the kernel interfaces to the device? That way you > > > know it works properly with anything else that has opened it at the > > > time. > > > > I do, when permissions are set such that I can. Unfortunately, the > > current Gentoo-stable eudev does not give any groups access to hidraw > > devices, so it fails over to libusb. > > Then fix that by using console-kit to set the permissions of the devices > that the local user has access to. Often there is no local user on these systems. Luke -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
