| 9b2a503a | 24-Apr-2025 |
Adrian Chadd <adrian@FreeBSD.org> |
e6000sw: add support for 88E6190X
This adds the minimum support required to probe/attach the 88E6190X.
I've tested this against an AT&T ATT-150 OCP device (Silicom i3000)
with local changes to expo
e6000sw: add support for 88E6190X
This adds the minimum support required to probe/attach the 88E6190X.
I've tested this against an AT&T ATT-150 OCP device (Silicom i3000)
with local changes to export MDIO via ixge(4).
Hints are required to probe/attach/configure the switch on amd64,
but with the mentioned diffs, it does work.
Thanks to Stas Alekseev <stas@alekseev.us> for the pull request
and Stas / Jason Hensler <omegadraconis@gmail.com> for chasing
down information about the chipset, linux stuff and AT&T OCP
hardware information.
PR: kern/281211
Pull Request: https://github.com/freebsd/freebsd-src/pull/1408
Differential Revision: https://reviews.freebsd.org/D50044
Reviewed by: imp
show more ...
|
| c78f603a | 25-Apr-2025 |
Adrian Chadd <adrian@FreeBSD.org> |
e6000sw: schedule e6000sw_tick() to occur once a second
Although all the machinery is present, the tick routine only ran once.
It was never rescheduled. So, reschedule it.
However in practice I've
e6000sw: schedule e6000sw_tick() to occur once a second
Although all the machinery is present, the tick routine only ran once.
It was never rescheduled. So, reschedule it.
However in practice I've discovered that the tick routine is running
whilst a bunch of phys are actually being probe/attached on each per-port
MII bus being created and probed off of the switch itself.
Until that's debugged (and likely the whole PHY management stuff is
cleaned up here), just add a NULL check and thus don't panic.
Differential Revision: https://reviews.freebsd.org/D50031
Reviewed by: imp
show more ...
|
| ee7f62fa | 25-Apr-2025 |
Adrian Chadd <adrian@FreeBSD.org> |
e6000sw: stop / drain the taskqueue (and tick) during detach
Although the tick isn't running every hz right now, when it /is/
running at hz, the shutdown path will race with an existing running
tick
e6000sw: stop / drain the taskqueue (and tick) during detach
Although the tick isn't running every hz right now, when it /is/
running at hz, the shutdown path will race with an existing running
tick routine, causing unpredictable panics.
* Introduce a shutdown flag which will abort doing the tick work if set
* set the shutdown flag and start cancel/draining the taskqueue during
detach.
Differential Revision: https://reviews.freebsd.org/D50030
show more ...
|
| af298663 | 25-Apr-2025 |
Adrian Chadd <adrian@FreeBSD.org> |
e6000sw: unlock the driver lock in the error path during attach
The driver sleep lock was being held during most of the error paths,
and not unlocking it will panic the kernel during detach. So, fi
e6000sw: unlock the driver lock in the error path during attach
The driver sleep lock was being held during most of the error paths,
and not unlocking it will panic the kernel during detach. So, fix it.
Differential Revision: https://reviews.freebsd.org/D50029
Reviewed by: imp
show more ...
|