From: Boszormenyi Zoltan <zboszor@freemail.hu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to use an USB<->serial adapter?
Date: Fri, 22 Aug 2003 09:02:42 +0200 [thread overview]
Message-ID: <3F45C012.9080903@freemail.hu> (raw)
In-Reply-To: <20030821170822.GA3584@kroah.com>
Greg KH wrote:
> On Thu, Aug 21, 2003 at 02:44:18PM +0200, Boszormenyi Zoltan wrote:
>
>>Hi,
>>
>>I am experimenting with a Prolific USB<->RS232 adaptor. We have
>>in-house developments that need serial communication and there
>>are more and more mainboards that provide only one RS232 connector.
>>(We would need more in one machine...)
>>So we decided to try an usb-serial converter. The one we bought
>>was happily recognized by a RedHat 9 system but I couldn't get
>>two-way communication over this converter.
>
>
> Which kernel version are you using?
RH9 errata kernel 2.4.20-19.9, I also tried 2.6.0-test3-mm3.
On a sidenote, I also tried its driver on W98SE, WinXP.
Same result with the MinGW compiled test programs.
> I didn't run your test programs, but are you sure you got the hardware
> flow control settings correct? How about testing the device with
Hmm, how comes the same settings *work* on real 16550?
Even under Win*, with the MinGW compiled testprograms...
> minicom, as that is a program that is known to work properly with these
> devices (along with lots of other ones, but that's a good place to
> start.)
I tried it now, thanks. Same thing happens. I set up two different
minirc, /etc/minirc.dfl using /dev/ttyS0 and /etc/minirc.usb
for /dev/ttyUSB0. In one terminal, I typed 'minicom', in another
'minicom usb'. In the 'minicom usb' what I type, appears in the
other window, but keys typed in the 'minicom' do not appear in
'minicom usb'.
I am starting to be convinced that it is a hardware flaw.
I will try to replace it.
>>setserial produces an error:
>>
>># setserial /dev/ttyUSB0
>>Cannot get serial info: Invalid argument
>
>
> Yes, setserial does not work with the majority of the usb-serial
> drivers, patches gladly accepted to fix this :)
I wasn't prepared to this answer. ;-)
>
> thanks,
>
> greg k-h
--
Best regards,
Zoltán Böszörményi
---------------------
What did Hussein say about his knife?
One in Bush worth two in the hand.
next prev parent reply other threads:[~2003-08-22 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 12:44 How to use an USB<->serial adapter? Boszormenyi Zoltan
2003-08-21 17:08 ` Greg KH
2003-08-22 7:02 ` Boszormenyi Zoltan [this message]
2003-08-22 12:05 ` Boszormenyi Zoltan
2003-08-21 23:18 ` Daniel Egger
2003-08-25 6:24 ` Boszormenyi Zoltan
2003-08-25 10:19 ` Daniel Egger
2003-08-27 9:33 ` Boszormenyi Zoltan
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=3F45C012.9080903@freemail.hu \
--to=zboszor@freemail.hu \
--cc=greg@kroah.com \
--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