From: "\"Bernd Krumböck\"" <krumboeck@universalnet.at>
To: linux-can@vger.kernel.org
Subject: SocketCAN driver for USB2CAN converter (8 devices)
Date: Sat, 17 Nov 2012 08:33:04 +0100 [thread overview]
Message-ID: <afad22f184c5b1bc8e833f5dc02d3b84.squirrel@webmail.universalnet.at> (raw)
Hi!
I'm developing a driver for the USB2CAN converter from "8 devices"
(http://www.8devices.com/product/2/usb2can).
At the moment the community seems to be very small, so I'm the only tester
and I have only this USB2CAN converter. Hope this situation will change in
future.
What must be done that this driver will become part of the kernel?
Source: https://github.com/krumboeck/usb2can
best regards,
Bernd
next reply other threads:[~2012-11-17 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 7:33 "Bernd Krumböck" [this message]
2012-11-17 9:37 ` SocketCAN driver for USB2CAN converter (8 devices) Wolfgang Grandegger
2012-11-19 7:38 ` "Bernd Krumböck"
2012-11-19 18:16 ` Marc Kleine-Budde
2012-11-19 18:24 ` Marc Kleine-Budde
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=afad22f184c5b1bc8e833f5dc02d3b84.squirrel@webmail.universalnet.at \
--to=krumboeck@universalnet.at \
--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).