From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ssagarr Patil <hugarsagar@outlook.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: ip -details link fails
Date: Wed, 27 May 2015 19:06:22 +0200 [thread overview]
Message-ID: <5565F98E.5010101@hartkopp.net> (raw)
In-Reply-To: <BAY176-W131B8CC6A9756B64828C77D3CB0@phx.gbl>
On 05/27/2015 06:38 PM, Ssagarr Patil wrote:
> I am currently using the following version of can driver
> # cat /proc/net/can/version
> rev 20120528 abi 9
>
This is network layer stuff.
It does not tell you anything about CAN network interfaces.
> But when I do the following it fails,
>
> # ip -details link show can0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument
>
> Transmitting and reciving of can frames works.
Oh.
I assume you use a CAN driver with is not in Linux mainline, e.g. the PEAK
driver. The PEAK driver is configured differently (see its documentation).
Can you send the output of
cat /proc/net/dev
uname -a
dmesg | grep -C 5 can0
Regards,
Oliver
>
> I want to get the current bitrate of the CAN interface using the above command,
> can anyone point me to what exactly is missing ? Or is there any alternative to get
> the current bitrate of the CAN interface (ioctl/ sysfs entry..)
>
> Thanks,
> Sagar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-05-27 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 16:38 ip -details link fails Ssagarr Patil
2015-05-27 17:06 ` Oliver Hartkopp [this message]
2015-05-27 17:11 ` Ssagarr Patil
2015-05-27 17:24 ` Oliver Hartkopp
2015-05-27 19:16 ` Marc Kleine-Budde
2015-05-28 9:48 ` Ssagarr Patil
2015-05-28 15:42 ` Oliver Hartkopp
2015-05-28 16:28 ` Ssagarr Patil
2015-05-28 17:19 ` Oliver Hartkopp
2015-05-28 0:46 ` Tom Evans
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=5565F98E.5010101@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=hugarsagar@outlook.com \
--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