From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Kurt Van Dijck <kurt.van.dijck@eia.be>
Cc: Sako Youssouf <youssouf.sako@renault-trucks.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Informations About CAN API of the Linux Kernel
Date: Fri, 08 Mar 2013 13:04:40 +0100 [thread overview]
Message-ID: <5139D3D8.2020305@volkswagen.de> (raw)
In-Reply-To: <20130308100548.GA496@vandijck-laurijssen.be>
Am 08.03.2013 11:05, schrieb Kurt Van Dijck:
>>> The J1939 API that is available on gitorious[1] is waiting for acceptance.
>>> The API has not changed for almost a year now, and is working.
>>> The J1939 API is quite different from raw CAN, since J1939 adds an
>>> addressing scheme. This makes it hard for non-J1939 users to
>>> judge about the usefullness of the API.
Yes. Unfortunately.
>>> Therefore, it's important that users of the J1939 stack share their
>>> opinion about it.
>>> Therefore, also your opinion matters and may contribute to the acceptance.
>>> If you find the J1939 stack usefull of course :-)
Indeed user feedback is really required.
>>
>> Would it be possible to add the j1939 support to staging? I mean from
>> the technical and from the political (is staging reserved for drivers
>> only?) point of view.
>
> That is a good idea.
> Technically, staging is underneath drivers/, which answers the political
> question: yes, it's for drivers probably.
Please check:
http://www.kroah.com/log/linux/linux-staging-update.html
It's for "drivers" and "filesystems".
You don't need to modify the kernel infrastructure to add drivers and
filesystems - but you need to change infrastructure to add new networking
functionalities.
Therefore i don't think, that this would work with the staging approach.
Btw. how can we gain more interest and users to the evaluation of Kurts j1939
stack? I remember about 3 persons asking about it (even about details) - what
happened to them?
Regards,
Oliver
next prev parent reply other threads:[~2013-03-08 12:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B7D120CFC15DC438D721B998AD9D9E9097105AB@SEGOTNC5180-N2.vcn.ds.volvo.net>
2013-03-06 15:42 ` Informations About CAN API of the Linux Kernel Marc Kleine-Budde
2013-03-06 16:03 ` Sako Youssouf
2013-03-06 16:18 ` Marc Kleine-Budde
2013-03-06 16:25 ` Sako Youssouf
2013-03-06 16:36 ` Marc Kleine-Budde
2013-03-06 16:41 ` Sako Youssouf
2013-03-07 12:40 ` Kurt Van Dijck
2013-03-08 8:55 ` Marc Kleine-Budde
2013-03-08 10:05 ` Kurt Van Dijck
2013-03-08 12:04 ` Oliver Hartkopp [this message]
2013-03-08 13:07 ` Kurt Van Dijck
2013-03-08 13:31 ` Kurt Van Dijck
2013-03-08 13:27 ` Yegor Yefremov
2013-03-11 9:31 ` Kurt Van Dijck
2013-03-11 10:03 ` Oliver Hartkopp
2013-03-11 10:21 ` Yegor Yefremov
2013-03-13 14:57 ` Kurt Van Dijck
2013-03-14 8:04 ` Heinz-Jürgen Oertel
2013-03-14 8:28 ` Wolfgang Grandegger
2013-03-14 8:41 ` Heinz-Jürgen Oertel
2013-03-14 10:34 ` Heinz-Jürgen Oertel
2013-03-14 11:00 ` Kurt Van Dijck
2013-03-14 12:25 ` Yegor Yefremov
2013-03-14 12:31 ` Heinz-Jürgen Oertel
2013-03-16 9:48 ` Heinz-Jürgen Oertel
2013-03-08 12:51 ` Robert Schwebel
2013-03-11 9:29 ` Kurt Van Dijck
2013-03-11 15:10 ` Marc Kleine-Budde
2013-03-11 15:34 ` Kurt Van Dijck
2013-03-11 16:00 ` Marc Kleine-Budde
2013-03-11 17:20 ` Oliver Hartkopp
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=5139D3D8.2020305@volkswagen.de \
--to=oliver.hartkopp@volkswagen.de \
--cc=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=youssouf.sako@renault-trucks.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 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.