From: Wolfgang Grandegger <wg@grandegger.com>
To: Ernast Sevo <ersevs@gmail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Linux-CAN <linux-can@vger.kernel.org>
Subject: Re: command ip -details -statistics link show wlan0
Date: Sat, 08 Jun 2013 09:42:42 +0200 [thread overview]
Message-ID: <51B2E072.3090206@grandegger.com> (raw)
In-Reply-To: <51B239EA.6060603@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]
Hi Ernast,
Please do not drop the CC to the Linux-CAN mailing list...
On 06/07/2013 09:52 PM, Wolfgang Grandegger wrote:
> On 06/07/2013 09:32 PM, Ernast Sevo wrote:
>> Hello,
>>
>> I apologize for resurrecting an old thread but I finally got around
>> to testing a program which uses
>> socket can that I wrote and I get quite a few overrun errors. I also
>> tried increasing the priority of
>> the MCP2515 IRQ which made things slightly better for me but not good
>> enough. Are there any other
>> suggestions as to how to fix these overrun errors? or at least improve
>> them a bit more.
>
> What priority did you use? Could you show the output of
>
> # ps -m -eo pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm
>
> when the test app is running? Note that these option are not available
> with the busybox version of ps.
>
> I also wrote:
>
>>> Recently I also stumbled over the following optimized driver
>>> MCP2515:
>>>
>>> http://clientes.netvisao.pt/anbadeol/mcp2515.html
>>>
>>> But that would required some effort to update and test it.
>
> Would be interesting if this driver behaves better concerning message
> losses. What kernel version are you using?
Just to give this driver a try, I have attached
"mcp2515-extern-v1.tar.bz2", my out-of-tree version of the MCP2515
driver mentioned above. On my Ubuntu system (running Linux 3.2.0), I
just use the following commands to get the kernel module built:
$ tar xf mcp2515-extern-v1.tar.bz2
$ cd mcp2515-extern
$ ./make-modules.sh
For your embedded environment you need to tweak "make-modules.sh",
though, or use the following command:
$ CONFIG_CAN_DEBUG_DEVICES=y CONFIG_CAN_MCP2515=m \
make -C <path-to-your-kernel-tree> SUBDIRS=`pwd` modules
You should then be able to load "mcp2515.ko" on your embedded system
(after removing the old MCP2510 driver):
# rmmod mcp2510
# insmod mcp2515.ko
If you are lucky, it will work out of the box.
Wolfgang.
[-- Attachment #2: mcp2515-extern-v1.tar.bz2 --]
[-- Type: application/x-bzip, Size: 6079 bytes --]
next prev parent reply other threads:[~2013-06-08 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 18:58 command ip -details -statistics link show wlan0 Ernast Sevo
2013-05-16 7:02 ` Wolfgang Grandegger
[not found] ` <CAOD0pekopW9g0SD=BnOMCEp3SdVZPrx5jY_CKLjZV09sWepS6A@mail.gmail.com>
2013-05-16 13:43 ` Ernast Sevo
2013-05-16 13:45 ` Marc Kleine-Budde
[not found] ` <5194F46D.4060905@grandegger.com>
2013-05-16 15:32 ` Ernast Sevo
2013-05-16 15:37 ` Marc Kleine-Budde
2013-05-16 15:43 ` Wolfgang Grandegger
2013-05-16 16:37 ` Ernast Sevo
[not found] ` <CAOD0pekym7Ey1eRn-ndwjEnsJUpf84xHbexztpRBjUKqoaGcPw@mail.gmail.com>
[not found] ` <51B239EA.6060603@grandegger.com>
2013-06-08 7:42 ` Wolfgang Grandegger [this message]
2013-06-10 12:53 ` Ernast Sevo
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=51B2E072.3090206@grandegger.com \
--to=wg@grandegger.com \
--cc=ersevs@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;
as well as URLs for NNTP newsgroup(s).