All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kozusky <mkozusky@kkmicro.cz>
To: linux-can@vger.kernel.org
Subject: Re: can4linux compilation for i.mx25 under 2.6.39
Date: Wed, 30 May 2012 14:05:42 +0200	[thread overview]
Message-ID: <jq52en$i2e$1@dough.gmane.org> (raw)
In-Reply-To: <4FC6099D.3030906@pengutronix.de>

Dne 30.5.2012 13:50, Marc Kleine-Budde napsal(a):
> Hello Martin,
>
> On 05/30/2012 01:39 PM, Martin Kozusky wrote:
>> Hello,
>> I downloaded latest sources of can4linux from svn and I'm trying to
>> compile it for 2.6.39 kernel (i.mx25 driver).
>> I edit cross-imx25 with proper compiler settings etc then ".
>> cross-imx25" and "make"
>>
>> There are some errors like
>> core.c:441:12: error: 'CAN1_BASE_ADDR' undeclared
>> core.c:452:11: error: 'MXC_INT_CAN1' undeclared
>>
>> I can change CAN1_BASE_ADDR to MX25_CAN1_BASE_ADDR and MXC_INT_CAN1 to
>> MX25_INT_CAN1, but there is error
>>
>> imx35.c:18:26: fatal error: mach/mxc_can.h: No such file or directory
>
> It comes from a Karo patch:
>
> http://git.openpandora.org/cgi-bin/gitweb.cgi?p=openembedded.git;a=commitdiff_plain;h=58d6c0ace0c9fe2a3ed9fa845bec9a89583e2fd5
>
>> Does anybody have idea where do I get this file? When I comment this
>> line, compilation continues and stops at
>>
>> imx35.c:113:18: error: dereferencing pointer to incomplete type
>>
>> Does it have anything to do with Karo tx25 board? (which I'm not using)
>> I already have CAN running using SocketCAN, but I also wanted to try
>> can4linux.
>
> Why do you want to use can4linux? Socketcan is the official CAN Stack
> for Linux. Be sure you use the latest kernel, because the flexcan driver
> has some bugs and problems prior to v3.4.
>
> Regards, Marc
>
>

Hello Marc,
I wanted to try if it will be faster than socketcan (which is dropping 
some CAN frames on my HW under heavy load). I need the closest way to 
the controller, and I thought that when can4linux is not using sockets 
layer it could be faster. I also wanted to try LinCAN (which is compared 
to SocketCAN here: 
http://dce.felk.cvut.cz/hanzalek/publications/Hanzalek10_168894.pdf  ) 
but I think it doesn't support Flexcan

Martin


  reply	other threads:[~2012-05-30 12:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 11:39 can4linux compilation for i.mx25 under 2.6.39 Martin Kozusky
2012-05-30 11:50 ` Marc Kleine-Budde
2012-05-30 12:05   ` Martin Kozusky [this message]
2012-05-30 12:08     ` Martin Kozusky
2012-05-30 12:18       ` Marc Kleine-Budde
2012-05-30 12:34         ` Martin Kozusky
2012-05-30 12:37           ` Marc Kleine-Budde
2012-05-30 12:16     ` Marc Kleine-Budde
2012-05-30 12:29       ` Martin Kozusky
2012-05-30 12:40         ` Marc Kleine-Budde
2012-05-30 12:50           ` Martin Kozusky
2012-05-30 13:18             ` Marc Kleine-Budde
2012-05-30 13:26               ` Martin Kozusky
2012-05-30 14:18                 ` Marc Kleine-Budde
2012-05-31 13:29                   ` Martin Kozusky
2012-05-31 13:42                     ` Marc Kleine-Budde
2012-05-31 16:28                       ` Oliver Hartkopp
2012-06-01  8:12                         ` Martin Kozusky
2012-06-01 11:22                           ` Oliver Hartkopp
2012-06-01  6:19                       ` Martin Kozusky

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='jq52en$i2e$1@dough.gmane.org' \
    --to=mkozusky@kkmicro.cz \
    --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 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.