From: Wolfgang Grandegger <wg@grandegger.com>
To: Stuart Statman <sstatman@sunverge.com>
Cc: linux-can@vger.kernel.org
Subject: Re: "Blessed" Version
Date: Wed, 10 Oct 2012 12:58:03 +0200 [thread overview]
Message-ID: <507554BB.4000809@grandegger.com> (raw)
In-Reply-To: <5074B274.7070703@sunverge.com>
On 10/10/2012 01:25 AM, Stuart Statman wrote:
>
> Sorry if this is a repeat of an earlier question; I missed the
> transition from Berlios to this mailing list, and am only now catching up.
>
> I've been sticking with a snapshot of the source tree from months ago.
> It isn't that I don't want the changes, I just don't want to have to
> retest my gear with a new set of drivers. (I'm also sticking with older
> versions of the kernel, same reason.)
>
> However, we want to start testing against newer 2.6 kernels. However, it
> turns out that my snapshot from so many moons ago no longer compiles
> against the latest CentOS blessed 2.6 kernel.
>
> So ... how do I get the latest release version of the SocketCAN drivers,
> CAN utils, etc? I could use git to grab from the head, I suppose, but
> that may be too bleeding edge for me.
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?
> (Forgive my almost complete ignorance of git, by the way. I'm likely to
> ask wildly stupid questions on this thread.)
You are welcome.
Wolfgang.
next prev parent reply other threads:[~2012-10-10 10:58 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 [this message]
2012-10-11 19:09 ` Stuart Statman
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=507554BB.4000809@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=sstatman@sunverge.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