[segfaultbuserr]

Is it a software issue, or a hardware issue that could be worked around in software... (sorry for the rant as an embedded system developer).

[loeg]

The latter is very common in the desktop/server space, too. If you ever write or work on drivers, you know.

[segfaultbuserr]

> If you ever write or work on drivers, you know.

Especially when the hardware vendor doesn't provide public documentation on the correct workaround.

[throwaway5959]

To the end user, if it doesn't impair performance, does it matter?

[Dylan16807]

To the end user, and doesn't impair performance, and covers all edge cases, then it doesn't matter if something is a workaround.

But we're not being end users here, we're trying to look at what went wrong. And we don't know if the other two are true either.

[mbreese]

And, if it's something that's worked around in software (meaning, it was a hardware issue), that might have issues for things like Asahi Linux, which probably won't have that workaround in place.

[makeitdouble]

Arguably it would impact the support for other OSes, especially alternative ones who'd need to reverse engineer the workaround and/or write their own to get the network stack working.

It could also fall apart the day Apple decides this machine is not supported anymore, and their next OS won't have the correct drivers anymore. It's their prerogative, but will sure suck for the machine owners.