Differential D52664

iwm: assign sequence numbers even if we ask the firmware to override
ClosedPublic
Actions

Authored by adrian on Sep 21 2025, 5:22 PM.

Details

Reviewers

glebius

Group Reviewers

wireless

Commits

rG5e49712ca8fe: iwm: assign sequence numbers even if we ask the firmware to override

Summary

I've had a report of this breaking without the sequence number
assigned (from glebius@) so, similar to iwx work, let's just re-add
it here.

Reported by: glebius

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

adrian created this revision.Sep 21 2025, 5:22 PM

Herald added a subscriber: imp. · View Herald TranscriptSep 21 2025, 5:22 PM

adrian requested review of this revision.Sep 21 2025, 5:22 PM

Harbormaster completed remote builds in B67227: Diff 162537.Sep 21 2025, 5:22 PM

adrian added a parent revision: D52655: iwx: add some lock assertions in the TX start path.Sep 21 2025, 5:23 PM

adrian added reviewers: wireless, glebius.

adrian added a project: wireless.

Yes, applying that on top of unmodified main makes iwm(4) work again.

Thanks!

This revision is now accepted and ready to land.Sep 21 2025, 6:12 PM

Closed by commit rG5e49712ca8fe: iwm: assign sequence numbers even if we ask the firmware to override (authored by adrian). · Explain WhySep 21 2025, 6:32 PM

This revision was automatically updated to reflect the committed changes.

adrian added a commit: rG5e49712ca8fe: iwm: assign sequence numbers even if we ask the firmware to override.

adrian added a child revision: D52711: net80211: create accessors for accessing the ieee80211_key key/mic data.Sep 24 2025, 3:36 PM

Revision Contents
Changeset List

Path

Size

sys/

dev/

iwm/

if_iwm.c

4 lines

Diff 162544

View Options

iwm: assign sequence numbers even if we ask the firmware to overrideClosedPublicActions