#
4b1a56af |
| 09-Jan-2022 |
jsg <jsg@openbsd.org> |
spelling feedback and ok tb@ jmc@ ok ratchov@
|
#
ce595ab8 |
| 03-Jun-2021 |
patrick <patrick@openbsd.org> |
Implement multicast support in mvpp(4) to make IPv6 work. With this change it's also not necessary to remember the old lladdr, since the old one will be purged automatically prior to installing the
Implement multicast support in mvpp(4) to make IPv6 work. With this change it's also not necessary to remember the old lladdr, since the old one will be purged automatically prior to installing the current set of multicast addresses.
Complaint filed by matthieu@
show more ...
|
#
6d508037 |
| 08-Nov-2020 |
patrick <patrick@openbsd.org> |
U-Boot might not have cleaned its pools. The pool needs to be empty before we fill it, otherwise our packets are written to wherever U-Boot allocated memory. Cleaning it up ourselves is worrying as
U-Boot might not have cleaned its pools. The pool needs to be empty before we fill it, otherwise our packets are written to wherever U-Boot allocated memory. Cleaning it up ourselves is worrying as well, since the BM's pages are probably in our own memory. Best we can do is stop the BM, set new memory and drain the pool. Tests show that this still returns U-Boot's entries. Now, where have those been stored... in HW or in memory?
show more ...
|
#
b3a1ec52 |
| 03-Nov-2020 |
patrick <patrick@openbsd.org> |
Disable HW PHY polling. It's enabled by default.
|
#
41cd246c |
| 22-Aug-2020 |
patrick <patrick@openbsd.org> |
Rework unicast/multicast configuration. Keep note that this only changes the code configuring the parser, we do not yet add the proper multicast filters.
|
#
31f14a25 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Remove unnecessary BM cookie defines.
|
#
b137aaec |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Rename gmac interrupt register defines to stay consistent with other gmac register defines.
|
#
1adf4f54 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Add enum for L2 cast like for L3.
|
#
13d9cc68 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Some register define renaming.
|
#
f247ea09 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Remove an unnecessary define.
|
#
4d0a0269 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Even more whitespace and header changes.
|
#
017da651 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
More whitespace and enum cleanup.
|
#
ad54c436 |
| 17-Aug-2020 |
patrick <patrick@openbsd.org> |
Plenty of whitespace fixups.
|
#
09e5d825 |
| 22-Jul-2020 |
patrick <patrick@openbsd.org> |
Init GOP and COMPHY.
|
#
e042150e |
| 22-Jul-2020 |
patrick <patrick@openbsd.org> |
Use correct ethertype and IP proto defines.
|
#
af1244a6 |
| 22-Jul-2020 |
patrick <patrick@openbsd.org> |
Use 1U for BIT(x), always define it and use it in four more places.
|
#
1a945772 |
| 25-Jun-2020 |
patrick <patrick@openbsd.org> |
Add mvpp(4), a driver for the Marvell Packet Processor v2, as used on the Armada 7K and 8K SoCs. Additionally, it seems to be used on the upcoming CN9K SoCs. This only supports version v2.2, since
Add mvpp(4), a driver for the Marvell Packet Processor v2, as used on the Armada 7K and 8K SoCs. Additionally, it seems to be used on the upcoming CN9K SoCs. This only supports version v2.2, since the older v2.1 is only used on some old ARMv7 we have no support for, and where there is no hardware for us to support.
A huge part of this driver is configuring the TCAM/SRAM-based "parser". Thus most of the code, especially the parser handling, was ported from EDK2 with a sed script doing plenty of automatic renaming and un-camel- casing.
The controller supports multiple TX/RX queues/vectors and RSS, so this would be a nice platform for testing network processing improvement on arm64. For now though we only configure and use a single queue.
The driver is still unfinished, but it's time to continue the work in tree. At least we can already send and receive packets, good enough for dhclient to work.
Since the MACCHIATObin uses Clause 45 10G PHYs and SFPs, link state handling is still a bit bogus, as we have no support for that. The 1G RJ45 port works fine though.
ok dlg@
show more ...
|