Linux CAN drivers development
 help / color / mirror / Atom feed
From: Stuart Statman <sstatman@sunverge.com>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linux-can@vger.kernel.org
Subject: Re: "Blessed" Version
Date: Thu, 11 Oct 2012 12:09:32 -0700	[thread overview]
Message-ID: <5077196C.60405@sunverge.com> (raw)
In-Reply-To: <507554BB.4000809@grandegger.com>


On 10/10/12 3:58 AM, Wolfgang Grandegger wrote:
> We have moved to http://gitorious.org/linux-can. CAN utilities and 
> kernel modules have been separated. You find them under "can-utils" 
> and "can-modules". If you can, you should use a recent kernel version 
> to avoid the "can-modules". I'm afraid, they are not really well 
> maintained. What kernel version do you plan to use? What CAN hardware 
> do you want to support? 
Strangely enough, just yesterday we made a decision to migrate CAN 
hardware that reduced the urgency of my question.

However, it does bring up another question.

I've been using slcand and "ip link set xxx up" for a piece of hardware 
that uses the slcan protocol. I'm pretty happy with how it's working, 
but I'd be happier if it was compatible with the can_if script that's in 
the utilities. I could write my own version of can_if that just does the 
right things for slcan, but it does open up a few questions :

1. What is slcan anyway, and why is it not handled like the other drivers?
2. Is there a can_if style script that already handles slcan?
-- 
Stu Statman
VP of Engineering
Sunverge, Inc
http://www.sunverge.com

  reply	other threads:[~2012-10-11 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 23:25 "Blessed" Version Stuart Statman
2012-10-10 10:58 ` Wolfgang Grandegger
2012-10-11 19:09   ` Stuart Statman [this message]
2012-10-13 10:17     ` Oliver Hartkopp
2012-10-15  6:33       ` Yegor Yefremov
2012-10-15 18:12       ` Stuart Statman

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=5077196C.60405@sunverge.com \
    --to=sstatman@sunverge.com \
    --cc=linux-can@vger.kernel.org \
    --cc=wg@grandegger.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