From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: pl2303 + uhci oops
Date: Mon, 1 Sep 2003 19:28:43 +0200 [thread overview]
Message-ID: <20030901172843.GE14376@lug-owl.de> (raw)
In-Reply-To: <200309011827.50331.biker@villagepeople.it>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
On Mon, 2003-09-01 18:27:50 +0200, biker@villagepeople.it <biker@villagepeople.it>
wrote in message <200309011827.50331.biker@villagepeople.it>:
> > > Using a pl2303-based usb->serial adaptor with the uhci driver always ends
> > > with a oops.
>
> > Use 2.6.0-testX - it's fixed there:) I'm successfully using a GPS
> > receiver based on a pl2303. This one if from www.lact.de (ebay'ed).
>
> This is good, but since 99% of the people is still using 2.4.x, it would be
> nice if it was fixed there too... ^_^
> BTW, I'm very willing to help by providing any additional information that
> might be useful to solve the problem.
Well, it seems to be a common problem to serial USB devices - if they
send data right after you close(), you oops... However, I'm no longer
looking into 2.4.x. 2.6.x works almost perfectly for me (I'll need to
work out some patches for better i386 support), but 2.6.x basically _is_
more painfree than 2.4.x ATM and IMHO. At least, for my configurations.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-01 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 16:27 pl2303 + uhci oops biker
2003-09-01 17:28 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 12:00 biker
2003-09-01 14:11 ` Jan-Benedict Glaw
2003-09-02 9:28 ` Greg KH
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=20030901172843.GE14376@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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;
as well as URLs for NNTP newsgroup(s).