18:18:51 <rmustacc> jbk: Was that able to work for you?
18:20:32 <jbk> yeah...
18:22:49 <jbk> 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
18:22:59 <jbk> from newer revisions
18:23:24 <rmustacc> The biggest gotcha is being revision aware.
18:23:30 <rmustacc> And eventually CMIS support.
18:32:04 <jbk> 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)
18:32:27 <jbk> but it looks like most of it is just defining more id values vs. changes in meaning
18:40:11 <rmustacc> It's 100% different meanings.
18:40:19 <rmustacc> It tells you that you need to go to the CMIS spec.
18:40:26 <rmustacc> But CMIS is generally 200G+.
18:41:31 <jbk> 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
18:56:52 <rmustacc> 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.
18:57:05 <rmustacc> I never did do the full topo stuff as we just use KR4 at Oxide.
21:18:14 <gitomat> [illumos-gate] 17765 assert.h checks post-17491 are bad for C++ -- Anders Waldenborg <anders⊙0n>