Request to pull-in new HBA & BOSS N1 PCI-ids from upstream

Bug #1961955 reported by Sujith Pandel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hwdata (Ubuntu)
Fix Released
Low
Unassigned
Focal
Won't Fix
Wishlist
Unassigned
Jammy
Won't Fix
Wishlist
Unassigned

Bug Description

Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream
Also combining request to pull-in new BOSS-N1 PCI-id from upstream

HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids.

BOSS-N1 is planned support in Ubuntu 20.04 onwards.

Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04.

PCI-id details:

1000: 00e6: 1028: 2170 HBA350i MM
1000: 00e6: 1028: 2197 HBA350i MM LP

1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET
1b4b: 2241: 1028: 2196 ROR-N100

Thanks.

description: updated
description: updated
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, the HBA and BOSS ones are part of the update https://launchpad.net/ubuntu/+source/hwdata/0.357-1 now but the ROR one doesn't seem to be upstream https://github.com/vcrhonek/hwdata/blob/master/pci.ids ? could you submit a merge proposal on github, that doesn't seem something we should carry as a distribution specific delta

Changed in hwdata (Ubuntu Jammy):
status: New → Incomplete
Revision history for this message
Sujith Pandel (sujithpandel) wrote :

Looks like pci.ids are pulled-in once in a month. We will wait for the next update to it in Apr.

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Sujith, what do you mean there, pulled from where? there is no such line upstream...

Revision history for this message
Sujith Pandel (sujithpandel) wrote :

https://github.com/vcrhonek/hwdata/commit/ae144d896eea90e527a57276accaf0da043c9f83
added the ROR-N100 to upstream hwdata.

Request you to pull this as well into Jammy.

Revision history for this message
Sujith Pandel (sujithpandel) wrote :

Hi Michael,
These ids are not included in Jammy having hwdata/jammy,now 0.357-1 all [installed].
Request you to help get these included in the SRUs.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Those changes are in https://bugs.launchpad.net/ubuntu/+source/hwdata/0.359-1 now.

Could you describe why you would like the changes backported to older series and provide a testcase? Which software are relying on those information and to for what purpose?

Changed in hwdata (Ubuntu):
importance: Undecided → Low
status: Incomplete → Fix Released
Revision history for this message
Sujith Pandel (sujithpandel) wrote :

These are new storage controllers launched/to-be-launched by Dell.
Unless hwdata carries these ids, lspci will show them as a generic storage controller, not the exact model name.
This impact is on lspci and any other tools which rely on model names displayed in lspci.
Hence the request to include in Jammy and Focal which are both supported on the platforms having these new storage controllers.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, so it's only cosmetic in the lspci report or is there a real impact for you or others? Since we got no user report and how-things-are-described-in-lspci isn't really important it doesn't sound like a high priority for a stable serie update

Revision history for this message
Sujith Pandel (sujithpandel) wrote :

It is currently only cosmetic, lspci only impact.

Revision history for this message
Sebastien Bacher (seb128) wrote :

I'm going to Mark it wontfix, it seems not something important enough to justify a stable update. If you want to work on it and update the bug to be SRU compliant and do the verification I'm fine sponsoring the update for you though

Changed in hwdata (Ubuntu Focal):
importance: Undecided → Wishlist
Changed in hwdata (Ubuntu Jammy):
importance: Undecided → Wishlist
Changed in hwdata (Ubuntu Focal):
status: New → Won't Fix
Changed in hwdata (Ubuntu Jammy):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.