From: Kurt Van Dijck Subject: Re: using j1939 Date: Fri, 9 Dec 2011 14:47:22 +0100 Message-ID: <20111209134721.GA309@e-circ.dyndns.org> References: <20111206104432.91170@gmx.net> <20111206121403.GB322@e-circ.dyndns.org> <4EDE1785.9000306@volkswagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from gate.eia.be ([194.78.71.18]:37387 "EHLO mail.eia.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751693Ab1LINr0 (ORCPT ); Fri, 9 Dec 2011 08:47:26 -0500 Content-Disposition: inline In-Reply-To: <4EDE1785.9000306@volkswagen.de> Sender: linux-can-owner@vger.kernel.org List-ID: To: Wolfgang Cc: linux-can@vger.kernel.org Wolfgang et.al., I created git://gitorious.org:~kurt-vd/linux-can/linux-can-j1939.git This is a clone of linux-can (currently 3.2.0-rc2+), with can-j1939 built in. Kurt On Tue, Dec 06, 2011 at 02:24:21PM +0100, Oliver Hartkopp wrote: > On 06.12.2011 13:37, Wolfgang wrote: > >>I'm afraid you lost me on this. Using your (cross)toolchain, you do > >>$ make > >>etc. to compile (& install) the binaries. > > > >The guys from pengutronix (I am using ptxdist 2010.07.1) told me > >that I have to know how the things in the repositories > >have to be built. > > > >>>But now I am facing the next problem, what type of packages do > >I have to > >create for each particular repository? > >>I believe you're asking something for a specific build system, but I > >>do not know which one. > >>What build system do you use? > > > >found and using toolchain: > >'/opt/OSELAS.Toolchain-1.99.3/powerpc-603e-linux-gnu/ > >gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/bin' > > > > Hello Wolfgang, > > when you build your BSP e.g. with > > ptxdist images > > in the directory 'build-target/linux-2.6.xx' your Linux kernel is > unpacked, patched and compiled. > > For a quick hack you can just try to update the files in > > build-target/linux-2.6.xx/net/can/* > build-target/linux-2.6.xx/include/linux/can/* > > with the files from Kurt (can-j1939-modules). > > The you need to drop the compile stage with > > pxtdist drop kernel.compile > > And then build the stuff again (with 'ptxdist images') > > Btw. the idea from Kurt with cross-compiling is also good. > > But you should define the KERNELDIR= .../build-target/linux-2.6.xx > then as THIS is the real kernel you are building for your system. > > Regards, > Oliver > > > > -- > 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