From: Andreas Laumann <al@authentidate.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: Kevin Fenzi <kevin@scrye.com>, linux-kernel@vger.kernel.org
Subject: Re: usbserial not working/oops on removal
Date: Sat, 03 Mar 2007 14:27:21 +0100 [thread overview]
Message-ID: <1172928441.3710.8.camel@justine.inexnet.de> (raw)
In-Reply-To: <200703031138.20582.oliver@neukum.org>
Am Samstag, den 03.03.2007, 11:38 +0100 schrieb Oliver Neukum:
> Am Samstag, 3. März 2007 08:19 schrieb Andreas Laumann:
> > Am Samstag, den 03.03.2007, 07:45 +0100 schrieb Oliver Neukum:
> > > Am Samstag, 3. März 2007 03:37 schrieb Kevin Fenzi:
> > > > I'm seeing some oddity with the latest fedora development kernel and a
> > > > usbserial device.
> > >
> > > Very interesting. Is this repeatable? Does unplugging have the same effect?
> >
> > I see it also on fedora rawhide using reinersct (cyberjack) scard
> > readers and it repeatable.
> > The first usbserial devices likes to register the line number 255 which
> > indeed is invalid.
>
> OK, please try this patch.
>
> Regards
> Oliver
>
> --- linux-2.6.21-rc1/drivers/usb/serial/usb-serial.c.alt 2007-02-21 05:32:30.000000000 +0100
> +++ linux-2.6.21-rc1/drivers/usb/serial/usb-serial.c 2007-02-26 15:32:50.000000000 +0100
> @@ -826,7 +826,6 @@
> num_ports = type->num_ports;
> }
>
> - serial->minor = minor;
> serial->num_ports = num_ports;
> serial->num_bulk_in = num_bulk_in;
> serial->num_bulk_out = num_bulk_out;
> @@ -980,6 +979,7 @@
> dev_err(&interface->dev, "No more free serial devices\n");
> goto probe_error;
> }
> + serial->minor = minor;
>
> /* register all of the individual ports with the driver core */
> for (i = 0; i < num_ports; ++i) {
Unfortunately your fix does not work. The first one seems registered
correctly, but after that it fails again for the next one.
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Reiner SCT Cyberjack USB card reader
cyberjack 5-2.2:1.0: Reiner SCT Cyberjack USB card reader converter detected
usb 5-2.2: Reiner SCT Cyberjack USB card reader converter now attached to ttyUSB0
cyberjack 5-2.3:1.0: Reiner SCT Cyberjack USB card reader converter detected
usb-serial ttyUSB0: Error registering port device, continuing
usbcore: registered new interface driver cyberjack
drivers/usb/serial/cyberjack.c: v1.01 Matthias Bruestle
drivers/usb/serial/cyberjack.c: REINER SCT cyberJack pinpad/e-com USB Chipcard Reader Driver
Andreas
next prev parent reply other threads:[~2007-03-03 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 2:37 usbserial not working/oops on removal Kevin Fenzi
2007-03-03 6:45 ` Oliver Neukum
2007-03-03 7:12 ` Kevin Fenzi
2007-03-03 7:19 ` Andreas Laumann
2007-03-03 10:38 ` Oliver Neukum
2007-03-03 13:27 ` Andreas Laumann [this message]
2007-03-03 15:33 ` Oliver Neukum
2007-03-03 20:15 ` Andreas Laumann
2007-03-03 20:43 ` Oliver Neukum
2007-03-03 21:05 ` Andreas Laumann
2007-03-03 21:59 ` Andreas Laumann
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=1172928441.3710.8.camel@justine.inexnet.de \
--to=al@authentidate.de \
--cc=kevin@scrye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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;
as well as URLs for NNTP newsgroup(s).