From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Pavel Pisa" <pisa@fel.cvut.cz>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Gustavo Romero" <gustavo.romero@linaro.org>
Cc: qemu-devel@nongnu.org,
Francisco Iglesias <francisco.iglesias@amd.com>,
Jason Wang <jasowang@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] hw/net/can: clean-up unnecessary includes
Date: Mon, 9 Dec 2024 17:22:34 +0100 [thread overview]
Message-ID: <2e219dd1-c9a7-4bc6-b33e-c4918e5b59c2@linaro.org> (raw)
In-Reply-To: <202412091223.02308.pisa@fel.cvut.cz>
On 9/12/24 12:23, Pavel Pisa wrote:
> Hello Alex,
>
> On Monday 09 of December 2024 11:06:35 Alex Bennée wrote:
>> The event_notifier, thread and socket includes look like copy and
>> paste of standard headers. None of the canbus devices use chardev
>> although some relied on chardev to bring in bitops and byte swapping
>> headers. In this case include them directly.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Acked-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
>
> Tested on Debian/GNU/Linux for SJA1000 and CTU CAN FD
>
> QEMU=/home/pi/repo/qemu/qemu-build/qemu-system-x86_64
>
> $QEMU -enable-kvm -kernel $KERNEL \
> -m 512M \
> -initrd ramdisk.cpio \
> -virtfs local,path=shareddir,security_model=none,mount_tag=shareddir \
> -vga cirrus \
> -append "console=ttyS0 \
> -object can-bus,id=canbus0-bus \
> -object can-host-socketcan,if=can0,canbus=canbus0-bus,id=canbus0-socketcan \
> -device kvaser_pci,canbus=canbus0-bus \
> -device ctucan_pci,canbus0=canbus0-bus,canbus1=canbus0-bus \
> -nographic
>
> By the way, I would like to discuse how to update CTU CAN FD a SJA1000
> IRQ handling to allow mapping on FPGA target platform buses from command
> line.
+ Gustavo
>
> I have some working prototype
>
> https://github.com/ppisa/qemu/commits/net-can-ctucanfd-platform/
>
> but I have some questions how to implement interrupts processing
> (or logic function) correct and acceptable way. I wills tart new
> thread and hope somebody responses and teaches me what is the
> proper solution.
>
> Best wishes,
>
> Pavel
next prev parent reply other threads:[~2024-12-09 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:06 [RFC PATCH] hw/net/can: clean-up unnecessary includes Alex Bennée
2024-12-09 11:23 ` Pavel Pisa
2024-12-09 16:22 ` Philippe Mathieu-Daudé [this message]
2024-12-09 18:58 ` Pierrick Bouvier
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=2e219dd1-c9a7-4bc6-b33e-c4918e5b59c2@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=francisco.iglesias@amd.com \
--cc=gustavo.romero@linaro.org \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pisa@fel.cvut.cz \
--cc=qemu-devel@nongnu.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 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).