jbk: Was that able to work for you?

yeah...

i might go ahead and add some bits to decode at least some of page a2 in there... though I noticed that there's some additional values for the various fields from SFF 8636 and 8472 -- I was thinking (unless there's a reason not to) to first add those just so we're up to date

from newer revisions

The biggest gotcha is being revision aware.

And eventually CMIS support.

yeah, I don't think we have anything with CMIS support as far as I'm aware (SFF 8024 has separate transceiver ids for modules w/ CMIS)

but it looks like most of it is just defining more id values vs. changes in meaning

It's 100% different meanings.

It tells you that you need to go to the CMIS spec.

But CMIS is generally 200G+.

err sorry i meant the additional bits in the SFF documents -- they're mostly defining additional values vs. new things... yeah the CMIS is its own thing from what I saw that'd need to be handled separately

Makes sense. Let me know if there's something that'd be helpful to do there since I was responsible for a bunch of that.

I never did do the full topo stuff as we just use KR4 at Oxide.

[illumos-gate] 17765 assert.h checks post-17491 are bad for C++ -- Anders Waldenborg <anders⊙0n>