From: Hubert Denkmair <xor@xor.wtf>
To: linux-can@vger.kernel.org
Subject: Generic USB driver for small hardware projects?
Date: Mon, 4 Apr 2016 22:08:41 +0200 [thread overview]
Message-ID: <5702C9C9.3050706@xor.wtf> (raw)
Hi all,
I'm new to this list, so please excuse if my topic has been discussed
before. I didn't find anything like it in the recent archives, though...
I'm currently building - as others did before me - a small, cheap, open
hardware USB-CAN-Converter.
Now I have the same problem as everyone before me - how to get socketcan
support for it.
Of course, I can make a ACM device and implement the slcan protocol.
Which is, imho, a ugly hack and, besides needing a userspace daemon,
seems to have some shortcomings (e.g. not supporting the netlink config
interface, only a few supported bitrates...).
I'd much rather like to build a native socketcan usb driver for my
hardware. As this seems to be overkill for a small project like mine,
I'd propose to do something better:
Why not build a usb driver with a generic interface that all hardware
projects can implement if they want native socketcan support?
Though, before starting something like that, I'd like to know how you
think about it. Can I expect some support from the list?
Is there a existing usb driver to start from?
Do you think there is a chance to get such a driver into mainline kernel
in the near future?
If there is some interest, I'd like to discuss on the list how such a
interface should look like; E.g. provide all socketcan features, in a
way so that it's both easy to implement in firmware and the linux
driver, while making it possible for the hardware to also support other
protocols, e.g. the slcan interface.
Please let me know what you think of my proposal,
Cheers
Hubert
next reply other threads:[~2016-04-04 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 20:08 Hubert Denkmair [this message]
2016-04-06 13:23 ` Generic USB driver for small hardware projects? Maximilain Schneider
2016-04-06 13:54 ` xor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5702C9C9.3050706@xor.wtf \
--to=xor@xor.wtf \
--cc=linux-can@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).