On Monday 23 April 2007, Greg KH wrote:
>On Sat, Apr 21, 2007 at 09:07:51PM -0400, Gene Heskett wrote:
>> Hi guys;
>>
>> I am using one of these as the interface between belkins upsd daemon and
>> the ups, This particular one says its a radio shack model according to
>> lsusb -v: ==
>> Bus 002
On Sat, Apr 21, 2007 at 09:07:51PM -0400, Gene Heskett wrote:
> Hi guys;
>
> I am using one of these as the interface between belkins upsd daemon and the
> ups, This particular one says its a radio shack model according to lsusb -v:
> ==
> Bus 002 Device 003: ID 1453:4026 Radio Shack 26-183
Hi guys;
I am using one of these as the interface between belkins upsd daemon and the
ups, This particular one says its a radio shack model according to lsusb -v:
==
Bus 002 Device 003: ID 1453:4026 Radio Shack 26-183 Serial Cable
Device Descriptor:
bLength18
bDescriptorT
On Sat, 3 Mar 2007 08:24:00 +0100, Oliver Neukum wrote:
>Am Freitag, 2. März 2007 22:12 schrieb Adam J. Richter:
>> When I plug in a pl2303-based usb serial device, the device is
>> supposed to appear as /dev/tts/USB0 (character device 188, 0).
>> However, under kernels that I have tried from
Am Freitag, 2. März 2007 22:12 schrieb Adam J. Richter:
> When I plug in a pl2303-based usb serial device, the device is
> supposed to appear as /dev/tts/USB0 (character device 188, 0).
> However, under kernels that I have tried from 2.6.20-git3 through
> 2.6.21-rc2-git1, /dev/tts/USB is crea
When I plug in a pl2303-based usb serial device, the device is
supposed to appear as /dev/tts/USB0 (character device 188, 0).
However, under kernels that I have tried from 2.6.20-git3 through
2.6.21-rc2-git1, /dev/tts/USB is created, and
attempting to open that file returns a "no such devic
Greg,
Did you receive this test email? I wrote a reply to your email to me /
the list and it bounced from the list and I wasn't sure why, I wrote the
list admin but it said he is on vacation in the uk. :) I signed up with
my work address so I can still post, but anyway, to say the least a bit
On Wed, Dec 27, 2006 at 01:38:52PM -0600, nick thompson wrote:
> Hi,
> Basically, in a nutshell, if I cat a text file to /dev/ttyS0, and have
> a null modem setup going to /dev/ttyUSB0 (the pl2303x) the first time I
> cat it, it goes through fine. However, the 2nd and 3rd etc it is missing
> the f
Pete Zaitcev wrote:
> On Thu, 28 Dec 2006 15:38:49 -0600, nick thompson <[EMAIL PROTECTED]> wrote:
>
>
>> So, the driver they released that was for RH 7,8,9, some rar file, was
>> it a bad driver? Or a closed source module?
>>
>
> I didn't look into it.
>
>
>> As well, thanks so much fo
On Thu, 28 Dec 2006 15:38:49 -0600, nick thompson <[EMAIL PROTECTED]> wrote:
> So, the driver they released that was for RH 7,8,9, some rar file, was
> it a bad driver? Or a closed source module?
I didn't look into it.
> As well, thanks so much for your suggestions. I am going crazy trying to
>
Pete,
So, the driver they released that was for RH 7,8,9, some rar file, was
it a bad driver? Or a closed source module?
As well, thanks so much for your suggestions. I am going crazy trying to
figure this out, because one character dropped isn't much, but as you
can imagine, it sure could get dr
On Thu, 28 Dec 2006 14:22:43 -0600, nick thompson <[EMAIL PROTECTED]> wrote:
> in one xterm, I open minicom edit it to use USB0, etc. In the other
> xterm, I cat a text file that is nothing but 1234567890 to ttyS0. It
> goes through fine, many times. Then I exit minicom, restart minicom, and
> in
Greg,
This is happening on RHEL4 kernel 2.6.9-42 I believe. SMP and non SMP.
I can give a better explanation:
I have a null modem cable going from ttyS0 (the regular serial port on
the box) to ttyUSB0
in one xterm, I open minicom edit it to use USB0, etc. In the other
xterm, I cat a text file tha
On 12/27/06, nick thompson <[EMAIL PROTECTED]> wrote:
> Hi,
> Basically, in a nutshell, if I cat a text file to /dev/ttyS0, and have
> a null modem setup going to /dev/ttyUSB0 (the pl2303x) the first time I
> cat it, it goes through fine. However, the 2nd and 3rd etc it is missing
> the first two
Hi,
Basically, in a nutshell, if I cat a text file to /dev/ttyS0, and have
a null modem setup going to /dev/ttyUSB0 (the pl2303x) the first time I
cat it, it goes through fine. However, the 2nd and 3rd etc it is missing
the first two characters. If anyone has any clues, or if there is
anything I c
On Wed, Nov 23, 2005 at 10:49:09PM +0100, Zden?k Habala wrote:
>
> hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
>
> usb 2-2: USB disconnect, address 2
>
> PL-2303 ttyUSB0: PL-2303 converter now disconnected from ttyUSB0
>
> pl2303 2-2:1.0: device disconnected
You have a flaky con
On Thu, 24 Nov 2005, Zdenek Habala wrote:
> Dear all,
>
> I have a very strange behavior of my USB to SERIAL cable for mobile phone
> NOKIA 6020. It is connected to my PC with Fedora Core 4.0 kernel
> 2.6.14-1.1637_FC4. The cable is properly recognized during boot see
> messages:
> But then, af
On Thu, 24 Nov 2005 00:00:56 +0100, "Zdenek Habala" <[EMAIL PROTECTED]> wrote:
> hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
> usb 2-2: USB disconnect, address 2
>[...]
> Do you have any clue, why it behaves like that? And what can I do against
> that ?
In my experience, it actuall
Dear all,
I have a very strange behavior of my USB to SERIAL cable for mobile phone
NOKIA 6020. It is connected to my PC with Fedora Core 4.0 kernel
2.6.14-1.1637_FC4. The cable is properly recognized during boot see
messages:
Nov 23 20:44:52 localhost kernel: usbcore: registered new drive
Hello All,
I am using two PL2303 USB to RS-485 converters connected to 2 different
PCs running Redhat 9 (2.4.20-8 kernel)
on them; and then the devices and connected together. I just want to
test data communication between
2 devices. (loop back). On both the PCs, the device is recognized
prope
Hello.
Currently the pl2303 driver have some problems with HX version
of pl2303 chip. Read or write after open operation looses
first transmited byte, sometimes device stops to work after reopen and no
data can be sent. I sniffed traffic between windows driver and the
device. Wi
Hi all,
I'm attaching a patch to fix status when using Siemens X65
mobile. This mobile use first byte instead of normal UART_STATE
byte.
--- linux-2.6.10-72032U10_12cl.pristine/drivers/usb/serial/pl2303.c
2004-12-24 19:34:44.0 -0200
+++ linux-2.6.10-72032U10_12cl/drivers/usb/seri
Hello,
It's possible to unplug usb device and do tiocmset() and tiocmget() without
valid interface in pl2303 module.
The patch below check this and return -ENODEV if interface was removed.
(the patch is against bk of 2005-04-11.)
diff -purN linux-05-04-11/drivers/usb/serial/pl2303.c
linux-05
Some days back I posted on linux-usb-users about my pl2303-based USB
serial device not working. I received one private response that it works
in linux 2.6.8, and indeed it does, perfectly.
Does anyone have a backport to kernel 2.4.x? Even the latest 2.4.28 prepatch
has the old revision of the dr
Hello,
Currently, the pl2303 driver doesn't support the TIOCINQ (or FIONREAD, same
thing) ioctl. Following is a patch to resolve that problem. Issuing an IOCTL
to the driver with one of the 2 proper requests will now place the number of
bytes waiting to be read into the ioctl argument and ret
Al Borchers wrote:
Phil Dibowitz wrote:
Al Borchers wrote:
Is
the app using ppp to connect with the phone, by any chance?
Nope ...
Then probably the app is opening the port O_NONBLOCK but not
expecting short writes.
After confirming that is indeed what they're doing, I've gone ahead and
explaine
Phil Dibowitz wrote:
OK, happy to do. Though the only other thing there is:
My appologies, the logs in my previous email were from another syncing
program that has a similar error -- though it's only backing up, so I
want to be consistent in the information I provide. Here's debug info
from mult
Al Borchers wrote:
Then probably the app is opening the port O_NONBLOCK but not
expecting short writes.
Would appear so:
userdata->fd = open(userdata->cabledev, O_RDWR|O_NONBLOCK|O_NOCTTY);
While I'm at it, I've run into another problem - after syncing A-F, I
get a "transfer interrupted," and be
Phil Dibowitz wrote:
Al Borchers wrote:
Is
the app using ppp to connect with the phone, by any chance?
Nope ...
Then probably the app is opening the port O_NONBLOCK but not
expecting short writes.
The program is called "multisync" and its the IrMC plugin that talks to
my phone, ...
Thanks for the
Al Borchers wrote:
Phil --
Phil Dibowitz wrote:
> That works.
Great news!
I would still like to understand the causes of the problem.
Can you tell me what application you were using to sync with
the phone?--I would like to look at the source code. Is
the app using ppp to connect with the phone, b
Phil --
Phil Dibowitz wrote:
> That works.
Great news!
I would still like to understand the causes of the problem.
Can you tell me what application you were using to sync with
the phone?--I would like to look at the source code. Is
the app using ppp to connect with the phone, by any chance?
-- Al
Al Borchers wrote:
I am not sure what the application is trying to do, but perhaps it
is unhappy when the pl2303 driver cannot do a write. Depending on
the situation this is not a bug--the pl2303 is just saying it can't
write now, try again later--but that may be a problem for your app.
Try this p
Phil --
Phil Dibowitz wrote:
Jul 24 00:24:37 rider kernel: drivers/usb/serial/pl2303.c: pl2303_write
- length = 64, data = 83 00 48 01 00 45 00 74 00 65 00 6c 00 65 00 63 00
6f 00 6d 00 2f 00 70 00 62 00 2f 00 6c 00 75 00 69 00 64 00 2f 00 30 00
30 00 30 00 30 00 30 00 31 00 30 00 30 00 30 00 30
Forgot a -u in my diff, so it wasn't terribly helpful... not that it
couldn't be applied by hand, but whatever.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://ww
Phil Dibowitz wrote:
Greg KH wrote:
On Fri, Jul 23, 2004 at 09:38:19PM -0500, Lonnie Mendez wrote:
Try enabling USB Serial Converter verbose debug under USB Serial
Converter support, along with USB verbose debug. Make note that the USB
Serial Converter driver needs to be compiled into the kerne
Greg KH wrote:
On Fri, Jul 23, 2004 at 09:38:19PM -0500, Lonnie Mendez wrote:
Try enabling USB Serial Converter verbose debug under USB Serial
Converter support, along with USB verbose debug. Make note that the USB
Serial Converter driver needs to be compiled into the kernel in order for
the de
On Fri, Jul 23, 2004 at 09:38:19PM -0500, Lonnie Mendez wrote:
>
> Try enabling USB Serial Converter verbose debug under USB Serial
> Converter support, along with USB verbose debug. Make note that the USB
> Serial Converter driver needs to be compiled into the kernel in order for
> the debug
Lonnie Mendez wrote:
Try enabling USB Serial Converter verbose debug under USB Serial
Converter support, along with USB verbose debug. Make note that the USB
Serial Converter driver needs to be compiled into the kernel in order for
the debugging option to show up in the kernel config menu.
Tha
Try enabling USB Serial Converter verbose debug under USB Serial
Converter support, along with USB verbose debug. Make note that the USB
Serial Converter driver needs to be compiled into the kernel in order for
the debugging option to show up in the kernel config menu.
Phil Dibowitz wrote:
So with some research I found out that the cable actually likes the
pl2303 driver (I can force the usb-generic driver to connect but then I
can't communicate -- the pl2303 driver attaches by itself and allows
communication).
However, everytime I do anything using the link,
Oliver Neukum wrote:
I tried a handful of modules but nothing would bind to it. So I'm
wondering how hard it would be to get it to bind to a port with an
existing module or new module, or if I'm completely thinking in the
wrong direction.
Short of changing a few device IDs in the code per peoep
On Tue, Jul 13, Al Borchers wrote:
> Olaf --
>
> Olaf Hering wrote:
> >Thanks Al!. Works perfectly, even with agetty.
>
> Good news! Thanks for testing it.
>
> Greg, would you accept this patch? It is the
> same code we use in the io_ti driver and similar
> to the gadget serial code.
I gues
Olaf --
Olaf Hering wrote:
Thanks Al!. Works perfectly, even with agetty.
Good news! Thanks for testing it.
Greg, would you accept this patch? It is the
same code we use in the io_ti driver and similar
to the gadget serial code.
-- Al
---
This
On Mon, Jul 12, Al Borchers wrote:
> Olaf --
>
> Olaf Hering wrote:
> >Hmm, I'm not sure how to translate that to LANG=diff
>
> Here is one such translation--a patch to 2.6.7 to add a
> circular buffer to the pl2303 USB serial driver.
>
> I tested it briefly and it solved the dropped newline
>
Olaf --
Olaf Hering wrote:
Hmm, I'm not sure how to translate that to LANG=diff
Here is one such translation--a patch to 2.6.7 to add a
circular buffer to the pl2303 USB serial driver.
I tested it briefly and it solved the dropped newline
problem--I used agetty to test it as you described
in your e
Olaf Hering wrote:
Here is a dmesg debug output, rm has an agetty connected, screen
connected via keyspan. I dont get any newlines.
> S0:12345:respawn:/sbin/agetty -L 9600 keyspan screen
agetty sttys the port to onlcr (map newline to carriage-return
newline). However, the pl2303 cannot do this; it
On Thu, Jul 08, 2004 at 07:26:51PM +0200, Olaf Hering wrote:
> > f178:~ # lsusb
> > Bus 004 Device 001: ID :
> > Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
> > Bus 003 Device 001: ID :
> > Bus 002 Device 004: ID 06cd:0104 Keyspan PDA [prerenum]
> >
> f178:~ # lsusb
> Bus 004 Device 001: ID :
> Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
> Bus 003 Device 001: ID :
> Bus 002 Device 004: ID 06cd:0104 Keyspan PDA [prerenum]
> Bus 002 Device 001: ID :
> Bus 001 Device 001: ID :
> f1
On Thu, Jul 08, Al Borchers wrote:
> Olaf --
>
> Olaf Hering wrote:
> > I have the keyspan working now, and its
> >directly connected to a PL2303 adapter on the same box.
> >writing to the PL2303 and reading from the keyspan leads to garbage
> >output. Sometimes the newline is repeated to fill t
Olaf --
Olaf Hering wrote:
> I have the keyspan working now, and its
directly connected to a PL2303 adapter on the same box.
writing to the PL2303 and reading from the keyspan leads to garbage
output. Sometimes the newline is repeated to fill the dd blocksize,
somethings I get the 'foo' filecontent
Greg,
can you help with this one? I have the keyspan working now, and its
directly connected to a PL2303 adapter on the same box.
writing to the PL2303 and reading from the keyspan leads to garbage
output. Sometimes the newline is repeated to fill the dd blocksize,
somethings I get the 'foo' file
On Tue, 22 Jun 2004 16:32:21 -0700 (PDT)
Soos Gergely <[EMAIL PROTECTED]> wrote:
> After the
> PL-2303 ttyUSB0: pl2303_write - failed submitting
> write urb, error -19
> message if I don't touch the modules, I just kill the
> pppd normally, I can reconnect.
What is the /proc/version? I do not
I don't know if you guys are working on my problem,
because I did not receive an answer, but here is some
interesting issue I just find out.
After the
PL-2303 ttyUSB0: pl2303_write - failed submitting
write urb, error -19
message if I don't touch the modules, I just kill the
pppd normally, I can
Please read bugzilla's bug 2722 girst.
Attached are two files with the logs when the error
appeared. USB debug is turned on. Kernel is 2.6.6 with
the second patch from bug 2672. (That is a Maxtor hdd
patch, it has nothing to do with the pl2303)
_
On Mon, Feb 02, 2004 at 02:32:45PM +, Paulo Marques wrote:
>
> It also as a "Linux driver" on the download page, that is a driver written
> a million years ago by prolific. I think (although I'm not sure) that the
> original drivers for Linux were written based on the one from prolific, but
On Monday 02 February 2004 12:46, Bruno THOMAS wrote:
>Paulo Marques wrote:
>> It also as a "Linux driver" on the download page, that is a driver
>> written a million years ago by prolific. I think (although I'm not
>> sure) that the original drivers for Linux were written based on
>> the one from
On Monday 02 February 2004 09:32, Paulo Marques wrote:
>Gene Heskett wrote:
>> On Thursday 29 January 2004 19:01, Greg KH wrote:
>>>On Thu, Jan 29, 2004 at 06:51:34PM -0500, Gene Heskett wrote:
It just seems that the pl2303's seriel side/end should respond to
a cts drop right at the end of
Paulo Marques wrote:
It also as a "Linux driver" on the download page, that is a driver
written a million years ago by prolific. I think (although I'm not sure)
that the original drivers for Linux were written based on the one from
prolific, but Greg can tell you for sure.
Yes, I'm interested i
Gene Heskett wrote:
On Thursday 29 January 2004 19:01, Greg KH wrote:
On Thu, Jan 29, 2004 at 06:51:34PM -0500, Gene Heskett wrote:
It just seems that the pl2303's seriel side/end should respond to
a cts drop right at the end of the currently being sent char,
instead of blindly sending the next
On Thursday 29 January 2004 19:01, Greg KH wrote:
>On Thu, Jan 29, 2004 at 06:51:34PM -0500, Gene Heskett wrote:
>> It just seems that the pl2303's seriel side/end should respond to
>> a cts drop right at the end of the currently being sent char,
>> instead of blindly sending the next x bytes into
On Wed, Jan 28, 2004 at 09:47:11PM -0500, Gene Heskett wrote:
> ---
> hub 3-2:1.0: new USB device on port 3, assigned address 4
> drivers/usb/serial/usb-serial.c: descriptor matches
> drivers/usb/serial/usb-serial.c: found interrupt in
> drivers/usb/serial/usb-serial.c: found bulk out
> drivers/usb
On Sun, Jan 25, 2004 at 03:20:39PM -0500, MUDr. TomÃÅ Hosszà wrote:
>
> open() puts automaticaly RTS to high, and there is no way how to not
> allow it. I was reading kernel sources, the code just does TIOCMBIS
> TIOCM_RTS without any condition.
Hm, well maybe we should not do this in the kernel
On Wednesday 28 January 2004 17:56, Greg KH wrote:
>On Wed, Jan 28, 2004 at 08:02:42AM -0500, Gene Heskett wrote:
>> Comments?
>
>On what? The driver loaded successfully. But do you really have a
>pl2303 device plugged in? The log messages do not show that.
>
>greg k-h
Yes, its plugged in, and
Hello.
I just wanted to write a solution for everybody who will be in front of
the same problem.
All was mystification.
open() puts automaticaly RTS to high, and there is no way how to not
allow it. I was reading kernel sources, the code just does TIOCMBIS
TIOCM_RTS without any condition.
but t
On Wed, Jan 28, 2004 at 08:02:42AM -0500, Gene Heskett wrote:
>
> Comments?
On what? The driver loaded successfully. But do you really have a
pl2303 device plugged in? The log messages do not show that.
greg k-h
---
The SF.Net email is spo
Greg;
I've noted that the dmesg contains a couple of lines regarding the
pl2303 I have, and which is normally hooked up to an old trs-80 color
computer in the basement. Its unusable due to problems in the
rts/cts emulation (I think), which may not be related to this from
dmesg:
drivers/usb/c
Hi everybody,
I am writing an application for ascension technologies minibird 3D
tracker. (www.ascension-tech.com).
from the documentation:
configured as DCE (i have for sure the correct type of cable)
RTS - if high device is switched to standby mode, if low it works
DTR - used for f
Hallo,
I had 2 problems with
drivers/usb/serial/pl2303.c in Kernel 2.4.23
First, after a frameerror, a parityerror or a overrunerror occur the driver
reports this error for all following bytes recived.
This continues as long no linestatuschange occures.
Result is a zerofilled datastream.
Second,
Marr wrote:
...
Aside: (once again, for clarity of the archives for future readers): The
pinouts Paulo mentioned above are for a DB-9 RS-232 connection, not a DB-25.
Thanks for clarifying that. I always forget about those 25-pin "extra large"
serial port connectors :)
--
Paulo Marques
Softw
On Wednesday 10 December 2003 08:38am, Paulo Marques wrote:
> Marr wrote:
> > On Monday 08 December 2003 03:59pm, Alessio Sangalli wrote:
> >>...
> >>if I connect a usb-serial adapter to my laptop, and I connect to this
> >>adapter an external serial modem, everything's perfect. But, if I
> >>conne
Marr wrote:
> On Monday 08 December 2003 03:59pm, Alessio Sangalli wrote:
>>...
>>if I connect a usb-serial adapter to my laptop, and I connect to this
>>adapter an external serial modem, everything's perfect. But, if I
>>connect another device, for example a telescope, (which happens to have
>>on
Marr wrote:
On Monday 08 December 2003 03:59pm, Alessio Sangalli wrote:
...
if I connect a usb-serial adapter to my laptop, and I connect to this
adapter an external serial modem, everything's perfect. But, if I
connect another device, for example a telescope, (which happens to have
only 3 lines c
On Monday 08 December 2003 03:59pm, Alessio Sangalli wrote:
> Hi, I wrote an email directly to "greg at kroah.com" because he's the
> author of the pl2303 driver but I think I could have some help here too
> about an issue with the pl2303 driver.
>
> if I connect a usb-serial adapter to my laptop,
Hi, I wrote an email directly to "greg at kroah.com" because he's the
author of the pl2303 driver but I think I could have some help here too
about an issue with the pl2303 driver.
if I connect a usb-serial adapter to my laptop, and I connect to this
adapter an external serial modem, everything
Has anybody successfully established connection of kgdb via PL2303?
I follow the instructions of http://kgdb.sourceforge.net/connect.html
(just replace /dev/ttyS1 with /dev/ttyUSB0). But the connection is
always failure.
I'm running 2.4.22 on host and 2.4.20-8 on target. The connection seems
w
On Wed, Nov 12, 2003 at 05:09:10PM -0800, David Meggy wrote:
> This is on an Arm7 board, using the pl2303 module, using linux
> 2.4.21-rmk1. [...]
Please try the attached.
Float failed to provide a trace, so I am not sure if he/she
has the same problem, and if so, is the patch likely to help.
--
On Fri, 2003-11-14 at 10:47, Pete Zaitcev wrote:
>
> There is no simple fix. It's not so much amount of fixing,
> but semaphores in serial must be removed, which may violate
> expectations in code, so it's bound to cause regressions.
> I've got plenty of traces, but no serial device to test.
I'd
> From: David Meggy <[EMAIL PROTECTED]>
> Date: 14 Nov 2003 07:51:54 -0800
>
> Is anyone looking at the scheduling in interrupt bug? I can provide
> traces or any other information to help debug this problem.
There is no simple fix. It's not so much amount of fixing,
but semaphores in serial mus
Is anyone looking at the scheduling in interrupt bug? I can provide
traces or any other information to help debug this problem.
David
--
David Meggy
Engineering
Technical Solutions Inc.
Unit #1 7157 Honeyman St
Delta BC Canada, V4G 1E2
www.techsol.ca
eM
On Wed, 2003-11-12 at 17:05, Greg KH wrote:
>
> Please run the oops through ksymoops and send it to us.
I've attached it. Let me know if the mailing list strips attachments,
and then I'll just e-mail it directly to you.
I also ran ksymoops on my PC with the following options
ksymoops -v vmlinu
Well here is my trace. I have the same problem. Well actually just a
snippet of the trace. It kind of keeps going for a couple of pages.
Any advice on how to fix this would be appreciated. After the long
stack dump, it goes through which function called which function, which
would require me to
On Wed, Nov 12, 2003 at 08:36:50PM +0200, Float wrote:
> Hi,
>
> pl2303 seems to be broken in 2.4.23-rc1.
>
> I got kernel panics twice after setting serial port parameters and echoing to
> the port. Presently it works OK, so there is no clear recepie for reproducing
> the bug. The following ca
On Wed, Nov 12, 2003 at 08:36:50PM +0200, Float wrote:
> pl2303 seems to be broken in 2.4.23-rc1.
> toshi:/usr/src# modprobe pl2303
> toshi:/usr/src# stty -F /dev/ttyUSB0 onlcr
> toshi:/usr/src# echo test > /dev/ttyUSB0
> Scheduling in interrupt
> kernel bug at sched.c:564!
> invalid operand:
Hi,
pl2303 seems to be broken in 2.4.23-rc1.
I got kernel panics twice after setting serial port parameters and echoing to
the port. Presently it works OK, so there is no clear recepie for reproducing
the bug. The following caused the second crash:
toshi:/usr/src# uname -srm
Linux 2.4.23-rc1 i
this patch from greg k-h fixes this problem. thx!
(the patch also works on 2.4.17 ...)
# USB: fix data toggle problem for pl2303 driver.
diff -Nru a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
--- a/drivers/usb/serial/pl2303.c Tue Sep 2 16:49:31 2003
+++ b/drivers/usb/serial/
On Tue, Aug 26, 2003 at 12:36:00PM +0200, Norbert Federa wrote:
> hi,
>
> i did again some testing with several pl2303 based adapters
> under linux-2.6.0-test4.
>
> the serial apps still have severe problems.
> i've done some more testing and it seems that the first
> byte coming to the pl2303
Mahlzeit
On Tue, Aug 26, 2003 at 12:36:00PM +0200, Norbert Federa wrote:
> the serial apps still have severe problems.
> i've done some more testing and it seems that the first
> byte coming to the pl2303 _never_ arrives in a read() from
> /dev/ttyUSB0 - except in the _first_ read after reinsert
hi,
i did again some testing with several pl2303 based adapters
under linux-2.6.0-test4.
the serial apps still have severe problems.
i've done some more testing and it seems that the first
byte coming to the pl2303 _never_ arrives in a read() from
/dev/ttyUSB0 - except in the _first_ read after
Hi!
On Sat, 30 Nov 2002, Greg KH wrote:
>
> Have you tried the latest 2.5 kernel? A number of irda changes have
> gone into there that might help out with these problems.
Yes, I have tried 2.5.50 and the situation there is somewhat worse, kernel
panics immediately when I try to run irattach. I h
On Wed, Nov 27, 2002 at 08:45:11PM +0100, Jurij Smakov wrote:
> Hi!
>
> Recently I have purchased an infamous MA-620 USB infrared adapter (based
> on pl2303 usb-to-serial converter). After a few failed attempts to make it
> work I have discovered a rather lengthy thread on this list, discussing
>
Hi!
Recently I have purchased an infamous MA-620 USB infrared adapter (based
on pl2303 usb-to-serial converter). After a few failed attempts to make it
work I have discovered a rather lengthy thread on this list, discussing
the issue preventing the pl2303 driver to operate properly for that device
On Sat, Nov 23, 2002 at 10:32:24PM -0800, Greg KH wrote:
> On Fri, Nov 22, 2002 at 08:33:47PM +0100, Magnus Månsson wrote:
> > Hey all,
> > I am having problems with my gps that has an embedded Prolific usb to serial
> > converter. For a while I ran a 2.5 kernel and I think the module worked
> > be
On Fri, Nov 22, 2002 at 08:33:47PM +0100, Magnus Månsson wrote:
> Hey all,
> I am having problems with my gps that has an embedded Prolific usb to serial
> converter. For a while I ran a 2.5 kernel and I think the module worked
> better. In 2.4 I get an oops if I remove the usb-cable and my softwar
Hey all,
I am having problems with my gps that has an embedded Prolific usb to serial
converter. For a while I ran a 2.5 kernel and I think the module worked
better. In 2.4 I get an oops if I remove the usb-cable and my software I am
using (gpsdrive) oopses the computer if I close it.
I saw in the
94 matches
Mail list logo
