| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <f6b4565a0808041030v595dcba7s329b00b3e08dd532@mail.gmail.com> Date: Mon, 4 Aug 2008 13:30:33 -0400 From: "Andrey Turovsky" <turova@...il.com> To: linux-kernel@...r.kernel.org Subject: usb-skeleton driver question Hello everyone, I hope this is not the wrong place for my question. If it is, please let me know where I should go with it. I am trying to develop a linux USB driver for communication between two linux-enabled embedded devices (though current development is being done on an ubuntu machine connected to one device). Currently, the device simply send as much ascii data as it can through the USB connection. The goal is to maximize throughput on the full speed connection. I have gone through the relevant sections of the O'Reilly book "Linux Device Drivers", but am fairly confused as to how to actually go about writing the driver. I am starting with the usb-skeleton driver. I changed the product and vendor IDs to match the device and get a friendly dmesg output: "USB Skeleton device now attached to USBSkel-192". Unfortunately, I cannot find too much relevant information as to what to do next. The part I need help with is figuring out how to connect to this device and read from it. There are no new devices in /dev/ and even if I create one, I'm not sure how to link the driver to it. Thanks for any help.. -Andrey -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists