Page MenuHomeFreeBSD

iwx: Shorten log code field
ClosedPublic

Authored by thj on Apr 2 2025, 2:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 26, 7:37 AM
Unknown Object (File)
Fri, Apr 25, 3:33 AM
Unknown Object (File)
Wed, Apr 23, 2:56 AM
Unknown Object (File)
Thu, Apr 17, 2:45 AM
Unknown Object (File)
Tue, Apr 15, 5:32 PM
Unknown Object (File)
Tue, Apr 15, 10:08 AM
Unknown Object (File)
Mon, Apr 14, 8:52 AM
Unknown Object (File)
Sun, Apr 6, 11:18 AM

Details

Summary

The widest value used with code is 32 bits, other values are smaller.
Reduce this down. Update printfs.

This the build on i386.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

thj requested review of this revision.Apr 2 2025, 2:07 PM
This revision is now accepted and ready to land.Apr 2 2025, 2:08 PM
emaste added a subscriber: emaste.

In the commit message, this fixes the build

This revision was automatically updated to reflect the committed changes.

I was looking it this post-commit and wondered a lot. I don't know what's it's good for? Most of this can be done with a 7 line Dtrace script. And in addition for async commands most of this doesn't help too much as you need the information you grab from the firmware to see which hcmd it was actually executing for problems. This lots of smells like "I want to compare Linux traceinfo with FreeBSD command order" to replicate but then again you'll need the full argument information for most to actually make sense and I cannot see that here either.

(and I am not talking about the looking up command names bits which are useful elsewhere as well even without DEBUG)

I added this to iwx to debug firmware crashes in comparison to the openbsd driver. I can move back to being a header only and out of iwx. Those crashes aren't happening anymore with the move to the fc release