From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "GARNERO, PIERRE (P.)" <pgarnero@visteon.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Kvazer USB CAN driver
Date: Tue, 07 Jan 2014 15:45:41 +0100 [thread overview]
Message-ID: <52CC1315.6060209@hartkopp.net> (raw)
In-Reply-To: <a8d74bed340445f081325afedf044bb5@AMSPR06MB053.eurprd06.prod.outlook.com>
Hello Pierre,
I moved your question to the new linux-can mailing list you should use in future.
On 07.01.2014 15:17, GARNERO, PIERRE (P.) wrote:
>
> I would like to use a KVAZER USBcan Rugged device with the socketcan library.
>
> I use Raspbian OS and I have built a kernel with anything enabled regarding CAN.
>
>
>
> I have loaded the following modules:
>
> # modprobe can
>
> # modprobe vcan
>
> # modprobe can-raw
>
> # modprobe can-dev
>
> # modprobe kvazer-usb
>
>
>
> But any ip link command (ex: ip link add dev can0 type can) failed with
> “RTNETLINK answer : operation not permitted” (excepted for vcan which works well).
When your modprobe succeeded (and the USB adapter is attached) a can0
interface should have been created by the kvaser-usb driver automatically.
The "ip link add dev can0 type can" is wrong.
You may add virtual CAN devices with this procedure, e.g.
ip link add dev vcan0 type vcan
But you can never create a real CAN interface with the ip tool.
>
> Could someone provide me some hints regarding the steps to have a Kvaser
> USBcan device up and running using the net driver ?
>
Once can0 showed up:
e.g. with dmesg | grep can0
or in
cat /proc/net/dev
You can set the bitrate and set the interface to up afterwards:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/networking/can.txt?h=linux-3.12.y#n758
Regards,
Oliver
next parent reply other threads:[~2014-01-07 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8d74bed340445f081325afedf044bb5@AMSPR06MB053.eurprd06.prod.outlook.com>
2014-01-07 14:45 ` Oliver Hartkopp [this message]
2014-01-07 15:15 ` Kvazer USB CAN driver GARNERO, PIERRE (P.)
[not found] ` <1389107792.5708.9.camel@blackbox>
[not found] ` <85d7d20e09a64996a182e491c6d250e0@AMSPR06MB053.eurprd06.prod.outlook.com>
2014-01-08 21:28 ` Oliver Hartkopp
2014-01-09 7:12 ` GARNERO, PIERRE (P.)
2014-01-09 13:14 ` GARNERO, PIERRE (P.)
2014-01-13 9:31 ` GARNERO, PIERRE (P.)
2014-01-16 11:02 ` Olivier Sobrie
2014-01-16 12:55 ` GARNERO, PIERRE (P.)
2014-01-17 9:36 ` GARNERO, PIERRE (P.)
2014-01-17 9:50 ` Marc Kleine-Budde
2014-01-17 13:50 ` GARNERO, PIERRE (P.)
2014-01-17 14:00 ` Marc Kleine-Budde
2014-01-18 14:26 ` GARNERO, PIERRE (P.)
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=52CC1315.6060209@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=pgarnero@visteon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.