qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org, Marc Kleine-Budde <mkl@pengutronix.de>,
	Pavel Pisa <pisa@fel.cvut.cz>
Cc: Matyas Bobek <bobekmat@fel.cvut.cz>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	 Nikita Ostrenkov <n.ostrenkov@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: i.MX6 SabreLite FlexCAN emulation for QEMU progress/working
Date: Mon, 15 Dec 2025 18:14:12 +0000	[thread overview]
Message-ID: <1B709815-4D9A-4C4A-B5DA-C69B432F7B5E@gmail.com> (raw)
In-Reply-To: <20250710-carrot-pillbug-of-election-eca4ab-mkl@pengutronix.de>



Am 10. Juli 2025 12:50:41 UTC schrieb Marc Kleine-Budde <mkl@pengutronix.de>:
>On 10.07.2025 12:58:05, Pavel Pisa wrote:
>> Hello Marc and others,
>> 
>> Matyas Bobek has implemented FlexCAN emulation for i.MX6
>> targets in the frame of his bachelor thesis
>> 
>>   https://dspace.cvut.cz/bitstream/handle/10467/122654/F3-BP-2025-Bobek-Matyas-BP_Bobek_FlexCAN_final_4.pdf
>> 
>> with reviews there
>> 
>>   https://dspace.cvut.cz/handle/10467/122779
>> 
>> Please, if you have problems to access documents, try that later,
>> our large archive with theses and publications is under
>> "AI" scrape-bots attacks almost permanently... or send me note
>> and I send the document directly.
>> 
>> The project continues and on base of Marc Kleine-Budde
>> review, Matyas Bobek has implemented timestamping
>> which should ensure correct messages ordering
>> even if FIFO mode is not used in the drivers,
>> Linux driver default case. There is even workaround
>> to advance timestamp if the the QEMU virtual time
>> is too coarse to provide unique values for for
>> too fast delivered messages through virtual bus
>> without real bits serialization.
>
>Nice! Good work!

Indeed!

>
>> The actual code is available on the "flexcan"
>> branch of the repository
>> 
>>   https://gitlab.fel.cvut.cz/bobekmat/qemu-flexcan
>> 
>> The clean, minimal patches sequence will be prepared
>> for review for the proposal for inclusion into QEMU
>> mainline, hopefully soon.
>> 
>> In longer term perspective, I have interrest in i.MX8
>> and other FlexCAN variants with FD support, etc.
>> I do not know if Mr. Bobek will have time and interest
>> to continue in this direction. I can offer that as the
>> another thesis or can offer that as summer job
>> etc. But latter would need some funding for students
>> motivation and their time compensation and I have had
>> never and do not have any QEMU related project for such
>> funding now and even minimal chance is even in future
>> for other than CTU CAN FD IP core where we support
>> silicon and FPGA products. So no timing, chances,
>> estimates for something beyond i.MX6 FlexCAN. 
>
>ACK, I think getting things mainline is more important than CAN-FD
>support.

Any news?

I've been playing with Matyas' flexcan branch and integrated the FlexCAN device model into the imx8mp-evk machine [1]. With some minor modifications such as allowing for 64-bit access I am able to run cangen+candump on either side and see the communication!

I think Matyas' work should be upstreamed. How shall we proceed? If desired, I could do the upstreaming process, leaving all credits to Matyas of course. IIUC we'd need Matyas' Signed-off-by tags (of the *squashed* branch) in this case for legal reasons, correct?

What do you think?

Best regards,
Bernhard

[1] https://github.com/shentok/qemu/tree/imx8mp-flexcan

>
>regards,
>Marc
>


      reply	other threads:[~2025-12-15 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 10:58 i.MX6 SabreLite FlexCAN emulation for QEMU progress/working Pavel Pisa
2025-07-10 12:50 ` Marc Kleine-Budde
2025-12-15 18:14   ` Bernhard Beschow [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=1B709815-4D9A-4C4A-B5DA-C69B432F7B5E@gmail.com \
    --to=shentey@gmail.com \
    --cc=bobekmat@fel.cvut.cz \
    --cc=mkl@pengutronix.de \
    --cc=n.ostrenkov@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=pisa@fel.cvut.cz \
    --cc=qemu-devel@nongnu.org \
    --cc=socketcan@hartkopp.net \
    /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;
as well as URLs for NNTP newsgroup(s).