Linux CAN drivers development
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: cedric koch-hofer <cedric.koch-hofer@snowsat.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Configuration CAN sja1000_isa
Date: Thu, 26 Apr 2012 13:32:23 +0200	[thread overview]
Message-ID: <4F993247.30704@grandegger.com> (raw)
In-Reply-To: <CALptkFSUrfcktNof43BL9anBb0SuJCye4ELd9qAWNA-F9T_svQ@mail.gmail.com>

On 04/26/2012 10:17 AM, cedric koch-hofer wrote:
> On Thu, Apr 26, 2012 at 10:03 AM, Wolfgang Grandegger <wg@grandegger.com> wrote:
>> > On 04/26/2012 09:35 AM, cedric koch-hofer wrote:
>>> >> Hello all,
>>> >>
>>> >> I am currently trying to use the CAN output of an Aaeon embedded
>>> >> system using sja1000 CAN chipset controler.
>>> >> I am using an Ubuntu with a kernel 3.0 and I do not succeed to change
>>> >> the state of my can device from down to up.
>>> >> As you can see in the following trace, all seems to work untill I try
>>> >> to activate my CAN network interface.
>>> >> After that, the interface is in state "UNKNOWN" and I can not use it
>>> >> with the socketcan tools: cansend, candump, cansniffer...
>>> >>
>>> >> Any idea will be welcome,
>> >
>> > That's wired. Does it work with "ifconfig can0 up"?

OK. it's the same with ifconfig. Hm, I have no idea. Looks like some
mismatch between the tools and the kernel. Some questions:

- What UBUNTU and kernel version do you use?
- Do you use the CAN drivers from that kernel?
- Could you try a more recent kernel?

Wolfgang.


      parent reply	other threads:[~2012-04-26 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  7:35 Configuration CAN sja1000_isa cedric koch-hofer
2012-04-26  8:03 ` Wolfgang Grandegger
2012-04-26  8:17   ` cedric koch-hofer
2012-04-26  8:54     ` Wolfgang Grandegger
2012-04-26 11:32     ` Wolfgang Grandegger [this message]

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=4F993247.30704@grandegger.com \
    --to=wg@grandegger.com \
    --cc=cedric.koch-hofer@snowsat.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