From: Peter Seiderer <ps.report@gmx.net>
To: Eric Stahl <ericstahl@limntech.com>
Cc: Vincent Mailhol <vincent.mailhol@gmail.com>,
marm@hms-networks.de, linux-can@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9] can: usb: IXXAT USB-to-CAN adapters drivers
Date: Fri, 23 Jun 2023 14:09:32 +0200 [thread overview]
Message-ID: <20230623140932.61b7769c@gmx.net> (raw)
In-Reply-To: <afff3b9a-8d84-49c9-4fc0-a07a792d4177@limntech.com>
Hello Eric,
On Mon, 19 Jun 2023 10:25:27 -0400, Eric Stahl <ericstahl@limntech.com> wrote:
> Hi all,
>
> The socketcan@hms-networks.de is bouncing for me. I removed both Florian
> Ferg's email (flfe@hms-networks.de) and sockectcan@hms-networks.de. I
> saw Markus from hms commenting on the last thread (PATCH v8) resolving
> those issues, so I've added him to this chain. I'm not sure if they are
> still a problem.
>
> I've backported Peter's PATCH v9 and it works well for me. It seems that
Thanks for testing effort ;-)
> hms is distributing a driver that does not incorporate the proposed
> changes from the past reviews
> (https://forum.hms-networks.com/t/socketcan-driver-for-linux-20-04/70299/30).
> Their driver has not worked for me with higher level CANopen libraries,
From a quick look at the provided sources they seem to (at least) lack the
following fix 'can: ixxat_usb: do not free skb before last usage'
(which was needed for my CAN FD use case to work with the HMS provided
sources):
https://codeberg.org/psreport/socketcan-linux-ix-usb-can/commit/51b3021
> but Peter's v8/v9 and Florian's past contributions work well. I would
> like to get ixxat's active pci socketcan drivers pulled into the mainline.
>
Not on my agenda (as I have only access to USB-to-CAN FD hardware at the
moment)...
> I don't mean to hijack this thread, but I was wondering if it's
> appropriate to add those pci drivers to this patch to get reviewed, or
> if it's more appropriate to open a separate patch.
I think best is to provide it as a separate patch as a starting point...
Regards,
Peter
>
> Thanks,
>
> Eric
next prev parent reply other threads:[~2023-06-23 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 20:01 [PATCH v9] can: usb: IXXAT USB-to-CAN adapters drivers Peter Seiderer
2023-05-31 7:25 ` Vincent Mailhol
2023-06-19 14:25 ` Eric Stahl
2023-06-23 12:09 ` Peter Seiderer [this message]
2023-07-07 16:48 ` Peter Seiderer
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=20230623140932.61b7769c@gmx.net \
--to=ps.report@gmx.net \
--cc=ericstahl@limntech.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marm@hms-networks.de \
--cc=mkl@pengutronix.de \
--cc=vincent.mailhol@gmail.com \
--cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox