Emulex OneConnect BladeEngine 2/3 iSCSI HBAs
A family of 10 Gigabit Ethernet iSCSI host bus adapters built on ServerEngines (later Emulex, later Broadcom) BladeEngine 2/3 and OneConnect silicon, sold from the late 2000s through the mid-2010s for storage networking in enterprise servers and blade systems. The hardware offloads iSCSI protocol processing onto the card so servers can boot from and access SAN storage over Ethernet.
recommendation
Worth keeping but documenting its niche, because the underlying ServerEngines/Emulex OneConnect 10GbE iSCSI offload adapters are old hardware no longer sold new in 2025, yet the driver still receives genuine upstream cleanup work as recently as 2026. Annotating it as legacy would help distros and admins understand it targets a shrinking installed base without forcing premature removal.
repository signals
sources
- lore.kernel.org
be2iscsi still receives upstream code cleanup in 2026; not obviously abandoned or under active removal.
- cateee.net
LKDDb maps CONFIG_BE2ISCSI to Emulex/ServerEngines BladeEngine2/3 and OneConnect iSCSI PCI IDs, and shows the driver still present in current kernel series.
- docs.broadcom.com
Broadcom-hosted Emulex datasheet identifies OCe11102-I as a 10Gb Ethernet iSCSI adapter in the OneConnect family, indicating an older 10GbE offload product line rather than a current mainstream platform.
codex reasoning notes (technical)
Kernel inspection via shell (`rg`, `sed`) identified Emulex/OneConnect/BladeEngine 2/3 PCI IDs and branding. Lore evidence came from `lore_file_timeline` on `drivers/scsi/be2iscsi/be_main.c`, which showed substantive 2026 maintenance and no removal signal in the returned activity; cited lore URL is from that tool output. LKDDb URL came from web search and confirms the exact hardware family plus continued Kconfig presence. Broadcom datasheet URL came from web search and anchors the product family as older 10GbE iSCSI-offload hardware. Conclusion: hardware looks legacy and unlikely to be sold new in 2025, but upstream activity is still real, so deprecation should be limited to annotation rather than removal.