Linux CAN drivers development
 help / color / mirror / Atom feed
From: John Whitmore <arigead@gmail.com>
To: linux-can@vger.kernel.org
Subject: mcp251x can't drop the can0 Interface
Date: Fri, 7 Feb 2014 20:12:37 +0000	[thread overview]
Message-ID: <20140207201236.GB28637@griso.site> (raw)

I guess you might say that I'm playing with an MCP2515 connected to a
RaspberryPi. I've got a problem which I've asked about on the RaspberryPi
forum but have never received an answer, so as a last resort I thought I'd try
here.

Basically I bring up the MCP2515 in listen mode at a certain baud rate. I
wanted to work on auto detetection of baud rate. So after listening for a
period of time at a certain baud rate I try to change the baud rate but I
can't do that with the linux mcp251x driver (I don't think it's the driver's
fault but have no idea whose it is). I've put in some debug statements
to see what happens when I execute "ifconfig can0 down" and basically the
interface goes down momentarily and then gets brough straight back up
again. So when I try to use the "ip" command to set the new baud rate I get an
error that the device is busy. 

Now I'm not sure if the issue is in the linux kernel or in the system
utilities "ifconfig" and "ip", but just wondered if anybody has seen this
behaviour. (I saw that there was a book published in January on linux
networking and must see if it deals with internals or just socket
programming.) If somebody could point me in the correct direction to look I'd
be very grateful. Or if somebody can confirm or deny this behaviour. 

             reply	other threads:[~2014-02-07 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 20:12 John Whitmore [this message]
2014-02-08 17:10 ` mcp251x can't drop the can0 Interface Marc Kleine-Budde
2014-02-10 22:28   ` John Whitmore
2014-02-10 22:34     ` Marc Kleine-Budde
2014-02-10 22:43       ` John Whitmore

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=20140207201236.GB28637@griso.site \
    --to=arigead@gmail.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