All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Quinton Cook <quinton.cook@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: J1939-22
Date: Fri, 24 Mar 2023 18:39:05 +0100	[thread overview]
Message-ID: <20230324173905.yrm5bpzpnyxf4bzf@pengutronix.de> (raw)
In-Reply-To: <CAAL29+00Rur1AWfj-gbzTo2afyYgsg-zY0B9rvgPoPaLaz8wNw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On 24.03.2023 09:55:58, Quinton Cook wrote:
> Hello my name is Quinton Cook. I was wondering if anyone was planning
> on implementing the new J1939-22 protocol in the linux kernel? If not
> I would love to implement it! Any help on getting started with linux
> kernel development would be greatly appreciated.

J1939-22 adds support for CAN-FD. What else are the differences to the
classical CAN J1939?

Without knowing any differences between J1939 and J1939-22, I suggest to
extend the existing J1939 support in the kernel for J1939-22.

So the first steps would be to get familiar with J1939 and it's kernel
implementation. Then discuss with some proof-of-concept patches what
needs to be modified/extended to support J1939-22.

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung Nürnberg              | Phone: +49-5121-206917-129  |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-03-24 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 16:55 J1939-22 Quinton Cook
2023-03-24 17:39 ` Marc Kleine-Budde [this message]

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=20230324173905.yrm5bpzpnyxf4bzf@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=quinton.cook@gmail.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.