linux-kernel - Configuring previously loaded module

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <fb4a4650708261502v5b64ca6ev680599ad9eb58b3@mail.gmail.com>
Date:	Sun, 26 Aug 2007 19:03:00 -0300
From:	"Thiago Ramos dos Santos" <dimtracker@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Configuring previously loaded module

Hi.

I have 2 devices which use the usbserial module: a CDMA modem and a
Palm PDA (to be more especific, the PDA uses the visor module, which
uses the usbserial).
When I plug the PDA to the computer, the visor module gets
automatically loaded by the kernel, and so is the usbserial module.
When the modem is pluged, the module is not loaded automaticaly, so I
created a hotplug entry for it.
For both devices I put rules in udev configuration files, so they are
autmaticaly mapped to the same /dev node in despite of the ttyUSB*
node they are mapped to.

The problem is that the modem requires the usbserial module to be
loaded with some parameters: product=xxxxx vendor=xxxxx. So, if I plug
the PDA first, the usbserial is loaded without those parameters, and
when the modem is pluged, the ttyUSB nodes are not created for it. So
I have to manually unload both the visor and usbserial modules, reload
the usbserial with the specific parameters (to get the ttyUSB nodes
for the modem) and reload the visor module (to recreate the ttyUSB
nodes for the PDA).

Is there anyway to configure the previously loaded usbserial module
with the modem parameters without having to unload it? If it is not
possible, is there any other solution?

Thanks
Thiago
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/