On Tue, Mar 04, 2025 at 01:26:42PM -0800, Jason Thorpe wrote:
> The firmware selects which CPU module gets to boot the system (the
> criteria used is unimportant here), and the UART on that module is
> connected to the console port and the RTC on that module is the
> authoritative RTC for the syste
Hi,
Hope everyone is doing well. I am Dorjoy. I am from Bangladesh. I am
interested in the Tickless NetBSD with high-resolution timers[1]
project. I wanted to know if this project is still up for grabs and if
a mentor is available for this project. I would like to start to
discuss this one and see
Hello,
I wasn't able to get internet working on NetBSD under QEMU and since
I'm completely unfamiliar with NetBSD and I'll definitely need more
time than I have currently, I will not apply for the moment. But, I
was thinking about it and realized that changes to the scheduler would
also be require
On Mon, Mar 10, 2025 at 04:43:30PM +0200, Andrius V wrote:
> Taylor has a good analysis and explanation of the issue
> https://mail-index.netbsd.org/netbsd-bugs/2024/03/26/msg082202.html,
> which I also noticed by testing ATA RAID setup on VIA controllers.
> [...]
Good analysis.
> Given that thr
On Tue, Mar 11, 2025 at 04:33:51PM +0200, Andrius V wrote:
> The major difference is that vn_bdev_open() increments
> (*vpp)->v_writecount++;
> That prevents from the v_writecount > 0 assert failure on vn_close()
> (https://nxr.netbsd.org/xref/src/sys/dev/ata/ld_ataraid.c#249)
>
> My only conce
