Re: Re: RFS: socketcan-utils
> Hello Markus,
See my comments inline:
> i really appreciate your attempt to create some debian packages for the
> SocketCAN utilities and the PEAK driver!
> (FYI: the PEAK driver is now maintained by Stephane Grosjean)
In the socketcan repository? Or in the kernel? Peak had indicated that they
wanted to work with upstream.
Do you have contact information? If so, you can send me the details privately.
> Some more comments inside the text:
> > From: Markus Becker <email@example.com>
> > To: firstname.lastname@example.org
> > Subject: RFS: socketcan
> > Dear mentors,
> > I am looking for a sponsor for my package "socketcan".
> > * Package name : socketcan
> Better: socketcan-utils or at least 'can-utils' as they are for the
> standard CAN subsystem of the linux kernel. Details below.
> > Version : 0.0.1+svn1240-1
> > Upstream Author : Volkswagen Group Electronic Research
> > Wolfgang Grandegger <email@example.com>
> > Vladislav Gribov, IXXAT Automation GmbH, <firstname.lastname@example.org>
> > <email@example.com>
> Most of the tools in socketcan/trunk/can-utils have been created by myself
> working at Volkswagen Group Research. This is also the reason of the
> license text which is a BSD/GPL license which has also been used in the
> Linux Kernel sources. Setting the license to GPL-2 in Debian packages will
> fit best.
> Having a feedback on <firstname.lastname@example.org> worked pretty good
> so far as many people with know-how are monitoring the list. If you like
> to have a single maintainer name, you can take me:
> Oliver Hartkopp <email@example.com>
Alright will do that for the next version.
> > * URL : <svn://svn.berlios.de/socketcan/trunk>
> > * License : GPL-2
> > Section : net
> > It builds these binary packages:
> > socketcan-driver - Source for the socketcan kernel modules
> Please omit the socketcan-driver package idea. The BerliOS SVN is only used
> for some staging drivers, supporting of outdated kernels and development of
> new network layer protocols. The Linux Mainline kernel contains the
> up-to-date CAN drivers. Mixing the socketcan/trunk/kernel/2.6/... with
> mainline kernel stuff leads to some problems, you won't like so solve ;-)
Well, we explicitly need isotp, which is not included in stock debian images.
That's actually the reason for creating the images. Any idea of how to get
Linux mainline isotp kernel module into the Debian kernel?
Of course one needs to rmmod all CAN kernel modules and load the appropriate
I would prefer to put an explicit warning into the package description.
BTW: Is there a CAN git repository, which is fed into net-next-2.6?
> > socketcan-utils - Socket-CAN user space programs
> This is a very good approach. These utilities (e.g. for the slcan driver)
> are working great for the mainline drivers.
> > The package appears to be lintian clean.
> > My motivation for maintaining this package is:
> > Get CAN automotive networking working in Debian out-of-the-box.
> > The package can be found on mentors.debian.net:
> > - URL: http://mentors.debian.net/debian/pool/main/s/socketcan
> > - Source repository: deb-src http://mentors.debian.net/debian unstable
> > main contrib non-free
> > - dget
> > The upload would fix this RFP bugs: #568303
> > Please CC me, as I am not subscribed to the list.
> Me too :-)
> I've just googled for you as i've seen your commits to the "PEAK-System
> Linux driver packaging" from Teemu Ikonen.
Sometime back I announced this also on the socketcan mailing list, but did not
get any feedback.
Thanks for coming back to me,
> Best regards,
> > I would be glad if someone uploaded this package for me.
> > Kind regards
> > Markus Becker