From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Leo Stan <leo.stanislas@qut.edu.au>, linux-can@vger.kernel.org
Subject: Re: kvaser leaf and SocketCAN
Date: Wed, 29 Apr 2015 06:45:28 -0400 [thread overview]
Message-ID: <20150429104528.GA5712@linux> (raw)
In-Reply-To: <55406A03.9060105@pengutronix.de>
On Wed, Apr 29, 2015 at 07:20:03AM +0200, Marc Kleine-Budde wrote:
> On 04/29/2015 06:39 AM, Leo Stan wrote:
> > Hi Austin, thanks for your reply.
> >
> > My ifconfig -a returns :
> >
> > eth0 Link encap:Ethernet HWaddr 44:8a:5b:6d:50:8d
> > inet addr:131.181.70.9 Bcast:131.181.70.255 Mask:255.255.255.0
> > inet6 addr: fe80::468a:5bff:fe6d:508d/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:3869 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1783 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:1268663 (1.2 MB) TX bytes:481256 (481.2 KB)
> > Interrupt:19
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:65536 Metric:1
> > RX packets:228 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:228 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:37579 (37.5 KB) TX bytes:37579 (37.5 KB)
> >
> > wlan0 Link encap:Ethernet HWaddr e8:2a:ea:de:3b:ae
> > UP BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > So I don't think it detected the Leaf...
> >
> > Now that I check my /dev/ folder there is actually leaf0 in it. Maybe
> > installing the drivers from Kvaser prevents me from using SocketCan?
Yes, per their release notes, the Kvaser out-of-tree driver scripts
blacklists the in-tree SocketCAN driver to prevent it from auto-loading:
http://www.kvaser.com/software/7330130980754/relnotes/relnotes_linuxcan.txt
>
> This can be the problem. Please try with the mainline drivers only.
>
Exactly.
Regards,
Darwish
next prev parent reply other threads:[~2015-04-29 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 7:31 kvaser leaf and SocketCAN max
2015-04-22 8:03 ` Marc Kleine-Budde
2015-04-29 2:01 ` Leo Stan
2015-04-29 3:50 ` Austin Schuh
2015-04-29 4:39 ` Leo Stan
2015-04-29 5:20 ` Marc Kleine-Budde
2015-04-29 6:15 ` Leo Stan
2015-04-29 6:33 ` Alexander Stein
2015-04-29 6:34 ` Marc Kleine-Budde
2015-04-29 10:45 ` Ahmed S. Darwish [this message]
2015-04-30 3:11 ` Leo Stan
2015-04-30 6:04 ` Marc Kleine-Budde
2015-04-30 6:14 ` Leo Stan
2015-04-30 6:25 ` Leo Stan
2015-04-30 6:48 ` Marc Kleine-Budde
2015-04-30 7:27 ` Oliver Hartkopp
2015-05-04 1:52 ` Leo Stan
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=20150429104528.GA5712@linux \
--to=darwish.07@gmail.com \
--cc=leo.stanislas@qut.edu.au \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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.