Hi! Yes, I have thought about it, but when I started writing the pcap driver, I didn't know about socketcan, and this user-space driver was already mostly ready (had to be ported a wee bit from c++), as I have used an own program to display the can frames before.
Problem is, I'm not sure I have the courage to start kernel driver development :) and I had a hard time finding information on how a socketcan driver should behave on the net with a few google searches. Another approach would be to rewrite the interface on the microcontroller itself, but again I have no idea what requests and responses a usb-socketcan device should implement, and I am having quite a hard time with the USB peripheral, because it is only scarcely documented in the user manual. So for now I think I'll stick with the libusb-based driver, and maybe add more or less native support for socketcan later on. Also I'm not sure if m$ windows supports socketcan? Regards, Ákos On 28 December 2011 12:23, Felix Obenhuber <fe...@obenhuber.de> wrote: > Hi, > > On Sat, 2011-12-17 at 17:54 +0100, Akos Vandra wrote: >> I have just written support for one of my CAN->USB adapter gadgets, so >> that it would work with libpcap and thus with wireshark. I would love >> to see support for my device as an option in future releases. > > Did you think about writing a SocketCAN driver for your device? > PCAP already has support for SocketCAN. Furthermore the SocketCAN > interface is very well established and comes with drivers for lots of > CAN hardware. > > cheers, > > Felix > > - > This is the tcpdump-workers list. > Visit https://cod.sandelman.ca/ to unsubscribe. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
