linux-kernel - Re: [PATCH]8250_pci: Add additional WCH CH352 device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Mar 2013 09:11:21 +0800
From:	Wang YanQing <udknight@...il.com>
To:	gregkh@...uxfoundation.org, swarren@...dotorg.org, jslaby@...e.cz,
	alan@...ux.intel.com, arnd@...db.de, paul.gortmaker@...driver.com,
	damm@...nsource.se, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH]8250_pci: Add additional WCH CH352 device

On Sat, Mar 02, 2013 at 05:45:55PM +0800, Wang YanQing wrote:
> This patch fix a problem XScale port
> detect code in autoconfig_16550a treat
> 16550A port as XScale port, caused by
> CH352 device use the 6th bit(UART_IER_UUE)
> in IER as a enhance function make this bit
> w/r.
> 
> for the below device:
> "
> 01:08.0 Serial controller: Device 4348:3253 (rev 10) (prog-if 02 [16550])
> 	Subsystem: Device 4348:3253
> 	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> 	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> 	Interrupt: pin A routed to IRQ 20
> 	Region 0: I/O ports at e010 [size=8]
> 	Region 1: I/O ports at e000 [size=8]
> 	Kernel driver in use: serial
> "
> [Note: I haven't test this patch, because I can't
> access the hardware now, but it should be right]
> 
I have tested it this morning, it works.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/