From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jeff Holtz <jeff.holtz@movimentogroup.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Rebuild Drivers for Ubuntu
Date: Mon, 12 May 2014 08:22:51 +0200 [thread overview]
Message-ID: <537068BB.5040901@hartkopp.net> (raw)
In-Reply-To: <loom.20140512T070934-65@post.gmane.org>
Hello Jeff,
I would suggest the following:
Download the can-modules git from gitorious:
git clone git://gitorious.org/linux-can/can-modules.git
cd can-modules/net/can/
make CONFIG_CAN=n CONFIG_CAN_RAW=n CONFIG_CAN_BCM=n CONFIG_CAN_GW=n
This should have created a can-isotp.ko which you can load with
sudo insmod ./can-isotp.ko
# dmesg | tail -1
[ 452.044371] can: isotp protocol (rev 20130731 alpha)
There's no need to compile the CAN mainline modules again.
You just need the linux-headers-<your-kernel-version> and the standard gcc
build environment (which was needed to compile can-utils anyway).
Please give me some feedback if it doesn't work as expected on your machine.
Regards,
Oliver
On 12.05.2014 07:13, Jeff Holtz wrote:
> I'm developing some ISOTP programs and would like to rebuild the drivers to
> include the CAN-ISOTP.ko file for UBUNTU (currently using 14.04 LTS) I can
> get the code for the build for 14.04 which includes all the can, can-bcm,
> can-raw ko's but nt the isotp. I've git the can-modules but having
> difficulties merging the latest code and where to place it to build. Any
> help/instructions would be appreciated.
>
> for example:
> cp ~/can-modules /usr/src/linux-3-13.0/.
> make SUBDIR=drivers/net/can
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-05-12 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 5:13 Rebuild Drivers for Ubuntu Jeff Holtz
2014-05-12 6:22 ` Oliver Hartkopp [this message]
2014-05-12 6:54 ` Jeff Holtz
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=537068BB.5040901@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=jeff.holtz@movimentogroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.