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  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]
Date:   Tue, 21 Nov 2023 14:51:55 +0700
From:   Bagas Sanjaya <>
To:     Linux Kernel Mailing List <>,
        Linux Staging Drivers <>
Cc:     Martyn Welch <>,
        Manohar Vanga <>,
        Greg Kroah-Hartman <>,
        Lukas Bulwahn <>,
        Soumya Negi <>,
        Alexon Oliveira <>,
        Andi Shyti <>,
        Jinjie Ruan <>,
        Menna Mahmoud <>,
        Gaosheng Cui <>,
        Matt Jan <>,
        Michael Straube <>,
        Dorine Tipo <>,
        Julia Lawall <>,
        Charles Han <>,
        Bagas Sanjaya <>
Subject: [PATCH RESEND] drivers: staging: vme_user: Describe VME_BUS and VME_TSI148

Help description for both options only tells users to enable them
without description of what VME bridge and TSI148 device are.

Briefly describe them.

Signed-off-by: Bagas Sanjaya <>
 This is a wording alternative to Dorine's patch [1]. The wording is
 inspired by [2] and [3].


 drivers/staging/vme_user/Kconfig | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/vme_user/Kconfig b/drivers/staging/vme_user/Kconfig
index d65cc5510649e9..8e5df6ce36e8f9 100644
--- a/drivers/staging/vme_user/Kconfig
+++ b/drivers/staging/vme_user/Kconfig
@@ -3,18 +3,32 @@ menuconfig VME_BUS
 	bool "VME bridge support"
 	depends on PCI
-	  If you say Y here you get support for the VME bridge Framework.
+	  Enable support for VME (VersaModular Eurocard bus) bridge modules.
+	  The bridge allows connecting VME devices to systems with existing
+	  interfaces (like USB or PCI) by means of translating VME protocol
+	  operations.
+	  Note that this only enables the bridge framework. You'll also
+	  likely want to enable driver for specific bridge device you have
+	  to actually use it. If unsure, say N.
 comment "VME Bridge Drivers"
 config VME_TSI148
-	tristate "Tempe"
+	tristate "Tundra TSI148 VME bridge support"
 	depends on HAS_DMA
-	 If you say Y here you get support for the Tundra TSI148 VME bridge
-	 chip.
+	 If you say Y here you get support for the Tundra TSI148 VME-to-PCI/X
+	 bridge chip (and pin-compatible clones).
+	 TSI148 is a high-performant, 2eSST and VME64-compliant VME-to-PCI/X
+	 interconnect bridge with support for PCI and PCI-X bus interface.
+	 It is primarily used in industrial and embedded systems.
+	 To compile this driver as a module, say M - the module will be
+	 called vme_tsi148. If unsure, say N.
 config VME_FAKE
 	tristate "Fake"

base-commit: 98b1cc82c4affc16f5598d4fa14b1858671b2263
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists