public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: "Pankajkumar Misra (RBEI/EEA2)" <Pankaj.Kumar@in.bosch.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: MCP2515 implementation is slow
Date: Wed, 26 Nov 2014 17:13:37 +0100	[thread overview]
Message-ID: <5475FC31.6020105@eurekelettronica.it> (raw)
In-Reply-To: <45c8e0a27f1140be831e1c21d65a2091@SGPMBX1004.APAC.bosch.com>

On 11/26/2014 06:02 AM, Pankajkumar Misra (RBEI/EEA2) wrote:

> But we are doing it on Kernel version 3.4.
>
>>
>> http://clientes.netvisao.pt/anbadeol/mcp2515.html
>>
>> Actually it runs on a 2.6.27 kernel with a Samsung S3C2442 SoC. It runs
>> without any problem running @ 250Kbit/s and 125Kbit/s with some burst of
>> a frame every 2 or 4 msecs. For sure your application has to be 'niced'

I've told you it runs for sure on 2.6.27.

> Lets see what is possible.

I think with some minor changes to the SPI API it is a viable way to do.

If you reach a working driver why not including it in the -next linux 
merge window??

Regards,
-- 
            ,,,
           (o o)
======oOO==(_)==OOo======

Gianluca Renzi
R&D
phone: +39.0542.609120
fax:   +39.0542.609212

       .oooO  Oooo.
======(   )==(   )=======
        \ (    ) /
         \_)  (_/

===================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
  \ source code!  /
   ---------------
     ¯\_(".)_/¯

  reply	other threads:[~2014-11-26 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 16:19 MCP2515 implementation is slow Pankajkumar Misra (RBEI/EEA2)
2014-11-25 16:47 ` gianluca
2014-11-26  5:02   ` Pankajkumar Misra (RBEI/EEA2)
2014-11-26 16:13     ` gianluca [this message]
2014-11-26 12:02   ` Rost, Martin
2014-11-26 12:32     ` Andri Yngvason
2014-11-27  7:46       ` David Jander
2014-11-27  7:33 ` David Jander

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=5475FC31.6020105@eurekelettronica.it \
    --to=gianlucarenzi@eurekelettronica.it \
    --cc=Pankaj.Kumar@in.bosch.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