LibBSD | rtemsbsd/mve: Fix the interrupt handler closure and installation order (!155)

[Chris Johns (@chris)]

Chris Johns commented: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/155#note_156384


This driver uses the legacy network stack model and as a result by passes the FreeBSD framework. The change https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/commit/64c77fd07adbaafd36113ad1bb6e1907a6e73e95 did not effect the FreeBSD drivers and LibBSD was tested. This highlights the fragile nature of this driver in LibBSD.

I am fine if those interested in the driver maintain it but RTEMS will not be testing it or maintaining it. I also have no idea how long this approach is viable as we could bring in changes from FreeBSD that break it. I would prefer a FreeBSD style driver however FreeBSD does not have one. NetBSD has [sys/dev/marvell/if_mvgbe.c](https://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/dev/marvell/if_mvgbe.c?rev=1.70;content-type=text%2Fx-csrc) and it supports Discovery II and III and that means we could support the second interface on the MVME5500.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/155#note_156384
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-eeldnkz74xmsa5x0clcxemxng-k/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260803/eced3298/attachment-0001.htm>