From: Ondrej Zary <linux@rainbow-software.org>
To: Bart Hartgers <bart.hartgers@gmail.com>
Cc: linux-usb@vger.kernel.org, ark3116_driver@auctionant.de,
linux-kernel@vger.kernel.org
Subject: Re: New ark3116 driver - testers needed
Date: Sun, 23 Aug 2009 22:49:10 +0200 [thread overview]
Message-ID: <200908232249.12914.linux@rainbow-software.org> (raw)
In-Reply-To: <7eb6a4d80908230546tc246dbdq33ffadcdce9a605a@mail.gmail.com>
On Sunday 23 August 2009 14:46:16 Bart Hartgers wrote:
> Hi All,
>
> I managed to write an improved ark3116 driver after I figured out that
> it is just an 16450 UART with some USB glue logic.
>
> Compared to the old ark3116 driver it offers the following improvements:
> - cts/rts handshake support
> - break signalling
> - line error detection
>
> Since it is a big step from the previous driver, it made little sense
> to modify that one, so I created new driver, named ark316new. Also
> this means that both could coexist if the new one doesn't work for
> someone.
>
> I have no datasheet, so the driver is entirely based on reverse
> engineering, and some testing by others would be a good idea.
>
> I also tried to include the IrDA fixes for the old ark3116.c driver
> that were posted on this list recently, but I could not test if
> these work, since I don't have the proper hardware.
>
> Because of this, I would appreciate reports of both success and
> failure in using this driver.
Good work. I'll try the driver during the week with that USB-to-IrDA thing.
Added LKML to CC.
--
Ondrej Zary
next parent reply other threads:[~2009-08-23 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7eb6a4d80908230546tc246dbdq33ffadcdce9a605a@mail.gmail.com>
2009-08-23 20:49 ` Ondrej Zary [this message]
2009-08-29 21:02 ` New ark3116 driver - testers needed Ondrej Zary
2009-08-31 6:51 ` Bart Hartgers
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=200908232249.12914.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=ark3116_driver@auctionant.de \
--cc=bart.hartgers@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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