Linux CAN drivers development
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Michael Muldoon <mbmuldoon07@gmail.com>
Cc: Linux-CAN <linux-can@vger.kernel.org>
Subject: Re: can acknowledgment
Date: Thu, 05 Sep 2013 22:12:40 +0200	[thread overview]
Message-ID: <5228E5B8.3010201@grandegger.com> (raw)
In-Reply-To: <CAJU5jUKkim-Pp5=VZjUfKUfRYB8b8zufwh9jtYFnhAcaYNgN5w@mail.gmail.com>

On 09/05/2013 09:45 PM, Michael Muldoon wrote:
> Here it is:
> 
> Linux version 3.2.20 (tomh@turbo_tom) (gcc version 4.5.3 (Buildroot
> 2012.05) ) #2 Wed Dec 5 14:33:28 CST 2012
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
> CPU: VIVT data cache, VIVT instruction cache
> Machine: Atmel AT91SAM9G20-EK

Even if reported, this seems not to be a Atmel AT91SAM9G20-EK board.
What do you find in "arch/arm/mach-at91/board-sam9g20ek.c".

...
> can: controller area network core (rev 20090105 abi 8)
> NET: Registered protocol family 29
> CAN device driver interface
> can: raw protocol (rev 20090105)
> mcp251x spi0.0: probed
> mcp251x spi0.2: probed
> mcp251x spi0.0: CNF: 0x01 0xff 0x02
> mcp251x spi0.2: CNF: 0x01 0xff 0x02

Strange. The latter two line should not show up before the devices are
opened (with ifconfig or ip.. Also "drivers/net/can/mcp251x.c" seems to
be special.

And how to you configure and start the CAN devices?

Wolfgang.



  reply	other threads:[~2013-09-05 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 19:47 can acknowledgment Michael Muldoon
2013-09-04 20:19 ` Aiken, Scott
2013-09-04 20:40   ` Michael Muldoon
2013-09-04 20:52     ` Aiken, Scott
     [not found]       ` <CAJU5jUKBdqRjZrxJ7P149_c_6n=JbtxvfBxr_Fh+WH4w5gxXag@mail.gmail.com>
2013-09-04 21:15         ` Aiken, Scott
2013-09-05  8:31     ` Wolfgang Grandegger
2013-09-05 12:47       ` Michael Muldoon
2013-09-05 13:45         ` Wolfgang Grandegger
2013-09-05 14:10           ` Michael Muldoon
2013-09-05 15:15             ` Wolfgang Grandegger
     [not found]               ` <CAJU5jULTsLvi4BrB5kuKC7QGVeUjTKY4ad_UA7sJ9aoXNax__g@mail.gmail.com>
     [not found]                 ` <57acf912689fb58466cb5aaac1993a59@grandegger.com>
     [not found]                   ` <CAJU5jU+F6t+WSLnsF8j7V2v9WBW+BVqQFf=00E2469RybocjzA@mail.gmail.com>
2013-09-05 19:24                     ` Wolfgang Grandegger
2013-09-05 19:45                       ` Michael Muldoon
2013-09-05 20:12                         ` Wolfgang Grandegger [this message]
2013-09-05 19:47                       ` Michael Muldoon

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=5228E5B8.3010201@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mbmuldoon07@gmail.com \
    /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