David Uhden Collado <daviduhden@gmail.com> wrote:

> I just found it confusing that the firmware was available, but the
> driver wasn't. It would be a good idea to create a separate list and
> warn users when installing firmware for drivers that are not yet
> available via fw_update.

It must have been a terrifying experience.

> > When developers are still working on a driver, they ask us to SHIP
> > THE
> > FIRWMARE AHEAD OF TIME, so that other developers and specific useful people
> > can play along with them to make progress.
> 
> Did you just implicitly call me useless? I admit that I'm not very
> useful when I have zero knowledge of operating system development, but
> I try to do what I can to be helpful.

Your mail did not include a fix.  It is just a litany of complaints.

> > After the thankless moaning you just die here, I'm pretty sure noone
> > wants
> > your participation.
> 
> These aren't ungrateful complaints (or "thankless moaning"). I was
> simply providing information about how this hardware works in
> OpenBSD. The dmesg messages I've seen online are from arm64, so I find
> it interesting to see this in amd64. I had no idea that this driver
> was still a work in progress, but now I know, the least I can do is
> help by testing new versions of the driver. I don't think it's
> appropriate to suggest that someone should "die" because of this.

You provided no information not already known.  The driver is disabled
because it doesn't work yet.  Can you stop talking about it?