Linux CAN drivers development
 help / color / mirror / Atom feed
From: Olivier Sobrie <olivier@sobrie.be>
To: Jeremy Conners <jeremy.conners@gmail.com>
Cc: mkl@pengutronix.de, pgarnero@visteon.com,
	linux-can@vger.kernel.org, socketcan@hartkopp.net
Subject: Re: Kvaser USB CAN II support in Linux Kernel
Date: Tue, 26 Aug 2014 14:19:55 +0200	[thread overview]
Message-ID: <20140826121955.GA10926@hposo> (raw)
In-Reply-To: <CAG+qKUtVvJ2RZC+FzzSU91-fSu01nFK1T+_BVE2ytP=VuOc+ag@mail.gmail.com>

Hi Jeremy,

On Mon, Aug 25, 2014 at 02:27:15PM -0700, Jeremy Conners wrote:
> Hello gentlemen,
> 
> I've been working on a project recently with an embedded linux device that
> needs to interface with a J1939/N2K bus.  For initial bring-up, I'm using a
> Kvaser USB CAN II device.  I recently found this thread (http://
> comments.gmane.org/gmane.network.socketcan.user/1445) that was very helpful to
> get the kernel to recognize the device and properly create the can0/1 devices.
>  Where can I join the discussion/mailing list as it seems to have been shutdown
> or moved recently?  I also may be able to help contribute to the discussion and
> /or help with additional work on this driver as I have a vested interest in
> getting this all running.

The linux-can mailing list (linux-can@vger.kernel.org) is the right place
to discuss such things.

Concerning the support for your device, as Pierre stated in the thread,
there are two families of Kvaser devices: "leaf" and "usbII".
Currently only the "leaf" family is supported by the driver in the kernel.
Pierre did a copy of kvaser_usb.c and adapted it to make it work with work
_only_ "usbII" devices. He sent the adapted driver as an attachment
(kvaser_usb2.c).

If you compare the two drivers (kvaser_usb2.c and kvaser_usb.c), you will
see that there are not a lot of differences between the two. I think
the best would be to adapt kvaser_usb.c to support both "leaf" and "usbII"
devices.
I've one such device at home but I have not had the time yet to have a look
at this... So if you want to adapt the driver, you're welcome :-)

Kind regards,

-- 
Olivier

           reply	other threads:[~2014-08-26 12:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAG+qKUtVvJ2RZC+FzzSU91-fSu01nFK1T+_BVE2ytP=VuOc+ag@mail.gmail.com>]

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=20140826121955.GA10926@hposo \
    --to=olivier@sobrie.be \
    --cc=jeremy.conners@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=pgarnero@visteon.com \
    --cc=socketcan@hartkopp.net \
    /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