Tobias Waldekranz

1. Check the hardware datasheet (__not__ functional spec) for the pins marked `ADDR[N]n`. These are usually shared with the LED matrix signals. 2. Check the strapping of these signals on...

Congrats! That's the expected value. The least significant nibble holds the chip revision, which in your case is 1, hence the difference from my example, which assumed revision 0.

You really need the functional specification for your device, which I have, but can't share with you because the world is broken. Some say there are ways of finding datasheets...

For a builtin copper port, you probably have to: - Enable the port (set the two LSBs in register 4) - Clear any power-down state on the corresponding PHY (via...

✅ You are reading the correct values from the ID registers, yes. ❓ As for which exact PHY IP it corresponds to: I don't know. The documentation, with some exceptions,...

I'm afraid I can't help you on that front. Very cool to have support for these devices in FreeBSD! 😎

### Steps to reproduce (Presumably) 1. `./images/qemu.sh -c` 1. Choose TAP networking, 1 port 1. `./images/qemu.sh` 1. Shutdown 1. `./images/qemu.sh -c` 1. Choose TAP networking, 2 ports 1. `./images/qemu.sh` 1....

Here's a script that shows all the LED config registers, and exits with code 1 if any LED is in the wrong state: ```sh #!/bin/sh x=0 for sw in 2...

(I think I am the colleague that, apparently at least _usually_, has his wits about him :wink:) We have read through the systemd docs. I think what we were curious...

Right, but what is the _use-case_? An example could be: > We want to run `foobard` as the `foobar` user, and we have an `/etc/pam.d/login` with the following relevant `session`...