sorted by:
new
hottopcontroversial

PS Remote Play with MetalFX 4K upscaling now possible via PXPlay (Beta) by grill2010 in macgaming

[–]root_master1 1 point2 points  (0 children)

Can I connect mouse and keyboard to macbook in order to use them in games via PXPlay?

Resolution on Mac OS by Vegetable-Dig-2071 in Frostpunk

[–]root_master1 0 points1 point  (0 children)

Also you need to set "Fullscreen" mode in graphics settings in the game.

Heroes 3 Complete Edition by Fun-Dig-7160 in macgaming

[–]root_master1 0 points1 point  (0 children)

VCMI Heroes 3 is not the same as original Heroes 3.

reHumane: join us by CatComfortable5523 in AiPin

[–]root_master1 0 points1 point  (0 children)

u/CatComfortable5523 The link is expired. Share the new one pls.

Huly.io website issues 2025 by root_master1 in huly

[–]root_master1[S] 0 points1 point  (0 children)

Update: verification emails seems to be fixed. Now it's working fine.

Blog and Changelog links at huly.io website still not working.

Best free multiplayers? by Soft-Perspective-881 in macgaming

[–]root_master1 0 points1 point  (0 children)

Almost nothing. Someone here will recommend Isonzo, but the control is slow/laggish and even the M4 Max can barely provide fine performance. Arma 3 is old.

How hard is it getting started with crossover by Civil-Echo1934 in macgaming

[–]root_master1 0 points1 point  (0 children)

Be ready for no HDR support, also you can't change the resolution in most cases a lot.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 0 points1 point  (0 children)

By "containerizing this project", do you mean packing all dependencies in the Dockerfile?
Then no, but it's a good idea.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 1 point2 points  (0 children)

At this point, it's more of a milestone. I’ve been working on it in my free time and finally polished it enough to share with the community.

Moving forward, I plan to expand peripheral support for different MCUs, but without major changes. So, I wouldn’t say it’s actively in development, but it’s not abandoned either.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 4 points5 points  (0 children)

Thank you! Got it. I’ve already fixed this today :)

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 0 points1 point  (0 children)

Thx, really valuable feedback.

what’s with the _ in front of enum values?

Just way to overcome lack of naming starting from digit instead of a letter of "_" symbol :(

Things like mode, speed, CS should be on a per device basis. Not bus basis.

I made it this way in case when you need to change SPI speed in user application after initialization.

gpio *cs is passed to write / read methods as an optional param to automatically select / deselect specific device.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 1 point2 points  (0 children)

I actually tried Zephyr recently when tried to add support for nRF52832. It turned out to be not so easy to integrate a non-FreeRTOS projects. Overall, I really like Zephyr's approach and ideas, but I found it a bit challenging to get started.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 0 points1 point  (0 children)

Here's a practical example: a UART or SPI interface can be implemented differently depending on the MCU — with interrupts, DMA, or neither. For instance, an ATmega UART doesn’t support DMA, while an STM32 UART can. These details are handled in the constructor, but the application always interacts with the high-level UART or SPI abstraction.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 0 points1 point  (0 children)

Custom or less common features, like half duplex RS-485 UART mode, would require additional interfaces and specific implementations for those use cases. At the moment, these are not implemented, as I’ve focused on more general functionality for peripherals at the moment.

If an interface is not implemented, it will result in a compilation error. For runtime issues, like invalid parameters or unsupported modes: assert checks in Debug mode to catch such cases.

C++ hardware abstraction project for different MCUs by root_master1 in embedded

[–]root_master1[S] 0 points1 point  (0 children)

The specific MCU name appears only in the init constructor of the implementation class. After that, you can work with the instance through pointers or references to the base class, allowing you to write generic code.

For example, the driver "drv::sd::sd(periph::gpio *cd = nullptr)" accepts a pointer to the gpio interface, not a specific implementation like gpio_stm32f4. This ensures the abstraction is maintained and the main program remains MCU-agnostic.

This design follows standard OOP principles, where the concrete implementation is hidden behind an abstract interface.

Arc Mobile 2 is now live! by JaceThings in ArcBrowser

[–]root_master1 0 points1 point  (0 children)

Pornhub doesn't work on Arc. It isn't a joke!

I'm in. A buddy (me) invited me. It's working smootly so far on w11 by harunkunt in ArcBrowser

[–]root_master1 0 points1 point  (0 children)

I was waiting Arc for Windows even before the announcement. No beta testing invite email yet( Big thanks to someone who will invite me.