From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: WCH CH-382 support: help with patching
Date: Wed, 09 Jul 2014 18:47:44 +0400 [thread overview]
Message-ID: <lpjkmg$uru$1@ger.gmane.org> (raw)
In-Reply-To: <87iotc6xph.wl%ml@sergej.pp.ru>
Hi,
I am just received the similar board, but it is strange that I have
different device-id, which is 3050.
Where did you get vendor driver from?
22.01.2014 15:51, Sergej Pupykin пишет:
>
> Hi,
>
> I have wch ch382 board which is mostly similar to already supported
> ch353 I think. But 382 works in PCI-E slot whereas 353 in PCI.
>
> I've written a patch and LPT looks working with
> parport_serial. (Actually it works even using "modprobe parport_pc
> io=0xe100")
>
> But I have some problems with ttyS*.
>
> Here are changes between CH353-2S1P and CH382-2S1P in vendor driver:
>
> CH353 CH382
> type 16550 16750
> IntrBar 3 0
> IntrOffset 0x0F 0xE9
> ofs1 0,0 0xC0,0xC8
>
> As I understand last line is offset to uart I/O ports, so I put 0xC0
> to pci_parport_serial_boards[].first_offset and uart_offset is 8, so
> /sys/class/tty/ttyS0/port is 0xE0C0
> /sys/class/tty/ttyS1/port is 0xE0C8
> and lspci -v reports "I/O ports at e000 [size=256]"
>
> But I cannot find where should I put interrupt parameters IntrBar and
> IntrOffset. Probably this is the reason why ttyS* don't work.
>
> Here is vendor WCH driver:
> https://home.p5n.pp.ru/~sergej/files/wch-driver.tar.gz
>
> My patch is in attachment.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-09 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:51 WCH CH-382 support: help with patching Sergej Pupykin
2014-07-09 14:47 ` Matwey V. Kornilov [this message]
2014-10-14 15:13 ` Sergej Pupykin
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='lpjkmg$uru$1@ger.gmane.org' \
--to=matwey.kornilov@gmail.com \
--cc=linux-serial@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).