From: Olivier Bornet <Olivier.Bornet@puck.ch>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Olivier Bornet <Olivier.Bornet@puck.ch>
Subject: Problem with iuu_phoenix module
Date: Mon, 25 May 2009 01:27:50 +0200 [thread overview]
Message-ID: <20090524232750.GE13019@puck.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
Hi all,
I have just update my kernel to the last available, and I have some troubles
with the iuu_phoenix.c usb module. (update was from 2.6.22 to 2.6.29.2).
The problem seems to come at close(). I mean, when I do a close() of the
ttyUSBx device, the driver not only do the close(), but it's like that we
insert a new physical device.
For example, I have /dev/ttyUSB0. I have one programm successfully using it.
When this program close the device, a new one is coming up (/dev/ttyUSB1 if I
have no other ttyUSB devices). Then, the "old" ttyUSB0 disaspear. This cause
troubles, because at each close(), the device change.
Is this a "feature", or a bug ?
Is this related to iuu_phoenix only, or to the USB system ?
Before, I was using the iuu_phoenix version 0.9 from
http://eczema.ecze.com/iuu_phoenix.html and this problem wasn't present.
But it's no more compatible with the kernel since 2.6.25 (or 26), due to the
changes in the USB structures. I have make a port of the changes done since the
0.5 (which was the base used for the kernel version) to 0.9, and the same
problem exists. If the list is interested, I will be happy to send my patch.
TIA for any help.
Have a nice day.
Olivier
--
Olivier Bornet
Olivier.Bornet@puck.ch
Swiss Ice Hockey Results : http://puck.ch/
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2009-05-24 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090524232750.GE13019@puck.ch \
--to=olivier.bornet@puck.ch \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox