From: Wolfgang Grandegger <wg@grandegger.com>
To: "Heinz-Jürgen Oertel" <hj.oertel@t-online.de>, linux-can@vger.kernel.org
Subject: Re: adding can4linux to drivers/char
Date: Sat, 21 Sep 2013 21:55:45 +0200 [thread overview]
Message-ID: <523DF9C1.30300@grandegger.com> (raw)
In-Reply-To: <1881932.U1kQQJkqCz@heinz.site>
On 09/21/2013 01:03 AM, Heinz-Jürgen Oertel wrote:
> Hello Linux CAN community,
>
> long before SocketCAN, which now is part of the Linux kernel drivers, can4linux was available as the CAN device driver for Linux.
>
> I now like to add it to the kernel source tree as well. What to you think about it. And how should I start and proceed?
> I would like to start with the Xilinx XCANPS as can be found on the Zynq processor. Maybe also with one PCI board, the CPC-PCI (EMS Wünsche).
>
> What is the best way? My current development for the PC is based on OpenSuse with kernel 3.7.10. for Xilinx it is kernel 3.10. Can I send a patch against 3.7 and to whom can I send it?
>
> Hope to get some answers helping me with the project. Thanks.
I fully share Marc's opinion. There is a working and portable driver
interface for the CAN bus. Why adding another one to the Linux kernel? I
think you need *strong* arguments to get it accepted. There might be
some CAN controllers not yet supported in Linux-CAN but I think it's
better (for the community) to invest in providing and posting Linux-CAN
patches for those devices instead. Porting can4linux applications to
Linux-CAN should be straight-forward and not a big deal.
Wolfgang.
next prev parent reply other threads:[~2013-09-21 19:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 23:03 adding can4linux to drivers/char Heinz-Jürgen Oertel
2013-09-21 9:17 ` Oliver Hartkopp
2013-09-21 19:57 ` Wolfgang Grandegger
2013-09-21 13:38 ` Marc Kleine-Budde
2013-09-21 16:37 ` Sebastian Haas
2013-09-21 17:09 ` Marc Kleine-Budde
2013-09-21 18:17 ` Oliver Hartkopp
[not found] ` <CADGMhsXaJOpbdCgEAoOguZWX2rS_P0a-H5UDZwUWiHD4Nj=upw@mail.gmail.com>
2013-09-22 10:40 ` Marc Kleine-Budde
2013-09-22 11:01 ` Oliver Hartkopp
2013-09-23 13:46 ` Marc Kleine-Budde
2013-09-21 19:55 ` Wolfgang Grandegger [this message]
2013-09-29 16:28 ` Heinz-Jürgen Oertel
2013-09-29 17:44 ` Marc Kleine-Budde
2013-09-29 17:45 ` Sebastian Haas
2013-09-29 18:44 ` Marc Kleine-Budde
2013-09-29 19:23 ` Max S.
2013-09-29 19:17 ` Heinz-Jürgen Oertel
2013-09-29 19:43 ` autobaud detection (was: Re: adding can4linux to drivers/char) Marc Kleine-Budde
2013-09-30 7:30 ` adding can4linux to drivers/char Sebastian Haas
2013-09-30 10:20 ` Kurt Van Dijck
2013-09-29 19:23 ` Heinz-Jürgen Oertel
2013-09-30 9:35 ` Oliver Hartkopp
2013-10-01 20:20 ` AW: " May, Stefan
2013-10-02 7:49 ` Oliver Hartkopp
2013-10-02 8:43 ` Linux CAN CUSE hacks, SocketCAN and RT Was: " Pavel Pisa
2013-10-02 9:47 ` Wolfgang Grandegger
2013-09-29 19:41 ` Wolfgang Grandegger
2013-09-30 7:40 ` Sebastian Haas
2013-09-30 8:21 ` Wolfgang Grandegger
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=523DF9C1.30300@grandegger.com \
--to=wg@grandegger.com \
--cc=hj.oertel@t-online.de \
--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.