vfio VS zephyr

If you love wasting time you could give my script a shot as well from a terminal with your gpu as the -pci argument, but you'll also want to give it your USB controllers too.

In my script I have -name main,debug-threads=on in my qemu command which helps me find which child thread is the iothread. I do my pinning using the same debug thread name discovery method.

Yeah my script is public and can be found here. I've thought about making an actual link post here a few times in the past but I guess the time to do so never really came up.

These boot arguments allow me to give my VM cores 3,11 to my guest while my host continues to operate (and handle any IOThreads I may have running for the guest) on the remaining cores 0(thread0,12), core1(thread1,13) and core3 (thread2,14). Personally, I handle my pinning dynamically with a bash script I wrote and still today find myself adding features and making improvements to. It can be found here if you want to give it a shot for your use case.

How does this compare to /u/ipaqmaster's script which accepts one-liners for single or dual and you're set?

You'll get further posting here by detailing what exactly is going wrong when you try and any configuration and scripts you tried to do it with. There are also scripts which try to be the everyman and do it all for you such as this vfio bash script written by one of the members here.

You may wish to try my vfio script which handles all of that automatically. Could be worth a try.

I've missed no opportunity to plug it lately, but the slew of people using hardcoded scripts copy-pasted from some guide or youtube video has never felt right to me. I made my own dynamic script which handles most vfio problems on the fly rather than hardcoding start.sh/stop.sh scripts per configuration. It could be worth checking out given I made it for Archlinux (my desktop) and you seem to be running that too.

I use this script to help start the qemu VM (there were no recent changes to the script) (I can paste the full qemu_system_x86_64 command if that would help) https://github.com/ipaqmaster/vfio

Well, if you'd be willing to give it a test drive just for fun I made and use this for my daily VFIO ease of access if you'd want to give it a try.

Hey folks. Anyone out there waiting for BT Auracast? It was announced June 2022, and immediately struck me as must have.

I lost my earbuds, but it seems ridiculous to get a replacement without Auracast, seems like surely if I'm going to make a decent sized purchase like that it needs to support group playing. I want to tune into the radios of other people on the metro or on the bus, want to be able to watch a movie on the plane with someone.

Auracast was announced in June 2022. Anyone else out there struggling with expectations here? I'm really hoping the product announcement season that's right around the corner had a good number of Auracast announcements.

Side note, a ton of it is over my head but it's been so so fun tuning in every once and again to see how Zephyr's Bluetooth Audio work is going. Just wild now much has gone into this! https://github.com/zephyrproject-rtos/zephyr/commits/main/subsys/bluetooth/audio

I am working on adding support for VisionFive 2 in Zephyr RTOS. I have created a device tree by referencing the starfive linux, patches of hifive_unmatched FU740 SoC and patches of BeagleV Starlight.

We are unsure on how to proceed further with this error. We have opened a github discussion regarding the same issue.

Then there are samples. Look through it for anything useful. RC522 uses SPI, so getting that to work would be a good first step.

Hey, I've been trying to build an app with cmake+ninja instead of west to integrate it into a larger build system and everything works correctly except for the final stage where it uses `/usr/bin/llvm-objcopy` instead of the `${CROSS_COMPILE}` one it tries to find here.

Zephyr has a lot of good points, but I really wish it didn't use Kconfig. Getting a working config seems to be mostly a matter of copying an already working example. It might be okay for hardware side of things, but it's a really bad at software/feature dependency.

Set https://docs.zephyrproject.org/latest/build/kconfig/tips.htm... and the issue: https://github.com/zephyrproject-rtos/zephyr/issues/52575. And don't even get me started on trying anything to group options together.

In this thread u/ikravets explained that there hasn't been much demand for Zephyr, which is why they aren't doing anything with it, and in this pull request Zephyr decided to no longer recommend PlatformIO in their documentation.

The answer is always in the source: https://github.com/zephyrproject-rtos/zephyr/blob/bdaac354f4cb0ad91d952c2f6941c16240d84da2/subsys/tracing/tracing_backend_ram.c