From: Wolfgang Grandegger <wg@grandegger.com>
To: kedari appana <kedare06@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re:
Date: Wed, 08 May 2013 09:11:53 +0200 [thread overview]
Message-ID: <5189FAB9.1040905@grandegger.com> (raw)
In-Reply-To: <CANdmM3MFEe-iXinRohUN9rEF-C2CoEg1va=nE7W-=KThogz7sg@mail.gmail.com>
On 05/08/2013 08:25 AM, kedari appana wrote:
> Hi,
>
> if i type the below command i am getting the following errors
> # ip link show can0
> 2: can0: <NOARP40000> mtu 16 qdisc noop qlen 10
> link/[280]
That's a strange output. Where does the "40000" come from? Maybe you are
using an old version of the "ip" program. The command shown below should
report:
# ip link help
...
TYPE := { vlan | veth | vcan | dummy | ifb | macvlan | can }
If you don't see "can", it's the wrong version.
> #cat /proc/interrupts
> in this i am not getting entry for my can interrupt handler
The device must be started to have the interrupt line requested. Please read
http://lxr.free-electrons.com/source/Documentation/networking/can.txt#L747
on how to use the "ip" program for CAN.
> #./canconfig can0 bitrate 50000 ctrlmode triple-sampling on
> this command was successfull but when i debugging it is showing can0:
> bit-timing not yet defined
>
> #If i use ifconfig can0 up
> error is can0: bit-timing not yet defined
> ifconfig: SIOCSIFFLAGS: Invalid argument
> Please help me what is the problem.
Your tools seem not to work properly. What does
# canconfig can0
print out? Anyway, please try using "ip" in the first place.
Please do not repeat the same question multiple times. It does usually
not help in getting an answer more quickly.
Wolfgang.
next prev parent reply other threads:[~2013-05-08 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 6:25 (unknown), kedari appana
2013-05-08 7:11 ` Wolfgang Grandegger [this message]
2013-05-14 14:38 ` kedari appana
2013-05-08 8:11 ` Re: Yegor Yefremov
-- strict thread matches above, loose matches on Subject: below --
2013-12-20 11:49 Unify Loan Company
2017-02-23 15:09 RE: Qin's Yanjun
2017-11-13 14:55 Amos Kalonzo
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=5189FAB9.1040905@grandegger.com \
--to=wg@grandegger.com \
--cc=kedare06@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox