| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
From Thaison Nguyen
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the first cut of this diff was made with coccinelle using this spatch:
@rule@
type caddr_t;
expression m, off, len, cp;
@@
-m_copydata(m, off, len, (caddr_t)cp)
+m_copydata(m, off, len, cp)
i had fix it's opinionated idea of formatting by hand though, so
i'm not sure it was worth it.
ok deraadt@ bluhm@
|
| |
|
|
|
|
|
| |
The address filter is not affected by link parameter changes,
so its reprogramming can be skipped.
|
|
|
|
|
|
|
|
|
| |
Set up the DMAC filter in one go instead of doing it separately for
unicast and multicast DMACs. This attempts to make the code a little
more readable. The setup should now run a bit faster as well because
it now does fewer register accesses.
Tested on CN5020, CN6120 and CN7130.
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the system recognize and configure Netgear ProSecure UTM25.
Of the network ports, LAN1-4 and WAN1 are functional. WAN2 does not work
for some reason. Even though WAN1 has a separate link to the SoC, the
connection appears to go through the same switch that the LAN ports use.
At the moment, the system relies on U-Boot to set up the switch so that
the LAN and WAN segments stay separate.
Initial diff and input from Thaison Nguyen, thank you!
|
|
|
|
|
|
|
| |
Detect octeon board model in one place, and replace firmware-supplied
board_type with an abstract model identifier in driver code. This makes
it easier to manage with different products, and board flavours, that
happen to use the same model information, such as board_type.
|
| |
|
| |
|
|
|
|
|
|
| |
OK dlg@, bluhm@
No Opinion mpi@
Not against it claudio@
|
|
|
|
|
|
| |
Unfortunately, machines tend to come with underpopulated device trees,
and consequently this change is not very useful as is. The lack of good
data is troublesome especially with things like I2C bus switches.
|
|
|
|
|
| |
This generally is an exercise in futility because the phandle of the
controller node tends to be missing.
|
| |
|
| |
|
|
|
|
| |
This makes certain machines' management network port usable.
|
|
|
|
|
|
|
|
|
|
| |
This makes various receive and transmit event counters readable. This
additionally replaces the old, and somewhat unusual, way of updating
error counters in ifp.
Most of the hardware counters are 32 bits wide. Hence the code polls
them periodically and adds the values to 64-bit software counters.
The hardware counters are cleared when read.
|
|
|
|
| |
ok kettenis visa
|
| |
|
| |
|
| |
|
|
|
|
| |
ok dlg@ tobhe@
|
| |
|
|
|
|
| |
OK pirofti@
|
| |
|
|
|
|
|
|
| |
conversion steps). it only contains kernel prototypes for 4 interfaces,
all of which legitimately belong in sys/systm.h, which are already included
by all enqueue_randomness() users.
|
|
|
|
|
|
|
|
| |
Load the kernel image from the filesystem upfront in rdboot and pass
the loaded image to octboot(4)'s kexec call in a memory buffer. As a
result, octboot(4) does not rely on a mounted filesystem.
OK deraadt@
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This network driver covers higher-end models of the OCTEON III family.
They have a modified design whose interface is not compatible with
the lower-end models or earlier chip generations.
The code is still a work in progress. However, it is capable enough
to make the SGMII port functional on the CN7360.
No objection from deraadt@
|
| |
|
| |
|
| |
|
|
|
|
| |
drivers is gross. discussed with visa.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
of this piece of code is to facilitate the use of fdt.
|
| |
|
| |
|
|
|
|
| |
or sending an IPI.
|
|
|
|
| |
kernel handover safer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this device access problem, this new loader has
been built on top of a small kernel. The kernel provides all the
necessary devices drivers, while most of the usual bootloader logic
is in a userspace program in a ramdisk.
The loader program is accompanied by a special device, octboot(4).
The main purpose of this device is to implement a mechanism for
loading and launching kernels. The mechanism has been inspired by Linux'
kexec(2) system call.
The bootloader will be enabled later when it is ready for general use.
Discussed with deraadt@
|
|
|
|
| |
Not enabled yet because of a conflict with octrtc(4).
|
| |
|
|
|
|
| |
an interrupt handler.
|