lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251026144958.26750-45-sashal@kernel.org>
Date: Sun, 26 Oct 2025 10:49:23 -0400
From: Sasha Levin <sashal@...nel.org>
To: patches@...ts.linux.dev,
	stable@...r.kernel.org
Cc: Sammy Hsu <zelda3121@...il.com>,
	Sammy Hsu <sammy.hsu@....com.tw>,
	Jakub Kicinski <kuba@...nel.org>,
	Sasha Levin <sashal@...nel.org>,
	chandrashekar.devegowda@...el.com,
	netdev@...r.kernel.org
Subject: [PATCH AUTOSEL 6.17-6.12] net: wwan: t7xx: add support for HP DRMR-H01

From: Sammy Hsu <zelda3121@...il.com>

[ Upstream commit 370e98728bda92b1bdffb448d1acdcbe19dadb4c ]

add support for HP DRMR-H01 (0x03f0, 0x09c8)

Signed-off-by: Sammy Hsu <sammy.hsu@....com.tw>
Link: https://patch.msgid.link/20251002024841.5979-1-sammy.hsu@wnc.com.tw
Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Signed-off-by: Sasha Levin <sashal@...nel.org>
---

LLM Generated explanations, may be completely bogus:

YES – adding the HP DRMR-H01 PCI ID lets existing t7xx hardware autoload
the driver without touching any other logic, so it is a low-risk
usability fix that fits stable policy.

- The change only extends the match table with `{ PCI_DEVICE(0x03f0,
  0x09c8) }` in `drivers/net/wwan/t7xx/t7xx_pci.c:940-944`, mirroring
  the existing Dell-specific entry and leaving probe/remove logic
  untouched.
- `t7xx_pci_probe()` (drivers/net/wwan/t7xx/t7xx_pci.c:834-917) runs the
  same initialization path for all matched devices; no vendor-based
  branching exists, so the new ID simply enables already-tested code on
  this HP-branded modem.
- Without this entry, kernels cannot bind the built-in driver to
  DRMR-H01 hardware, which is a clear user-visible malfunction for any
  system shipping with that modem.
- The modification is self-contained, has no architectural impact, and
  aligns with prior stable-acceptable device-ID additions for the same
  subsystem.

Backporting will restore driver functionality on new HP platforms with
virtually zero regression risk. Potential next step: 1) Queue it for the
maintained stable branches that carry the t7xx driver.

 drivers/net/wwan/t7xx/t7xx_pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/wwan/t7xx/t7xx_pci.c b/drivers/net/wwan/t7xx/t7xx_pci.c
index 8bf63f2dcbbfd..eb137e0784232 100644
--- a/drivers/net/wwan/t7xx/t7xx_pci.c
+++ b/drivers/net/wwan/t7xx/t7xx_pci.c
@@ -939,6 +939,7 @@ static void t7xx_pci_remove(struct pci_dev *pdev)
 
 static const struct pci_device_id t7xx_pci_table[] = {
 	{ PCI_DEVICE(PCI_VENDOR_ID_MEDIATEK, 0x4d75) },
+	{ PCI_DEVICE(0x03f0, 0x09c8) }, // HP DRMR-H01
 	{ PCI_DEVICE(0x14c0, 0x4d75) }, // Dell DW5933e
 	{ }
 };
-- 
2.51.0


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ