linux-kernel - Re: Simple UART driver help and TTY questions

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <489A1CEF.4060302@gmail.com>
Date:	Wed, 06 Aug 2008 23:51:43 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Ira Snyder <iws@...o.caltech.edu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Simple UART driver help and TTY questions

On 08/06/2008 11:46 PM, Ira Snyder wrote:
> On Wed, Aug 06, 2008 at 11:11:00PM +0200, Jiri Slaby wrote:
>> conOn 08/05/2008 06:33 PM, Ira Snyder wrote:
>>> static void tiny_config_port(struct uart_port *port, int flags)
>>> {
>>> 	FUNC_ENTER();
>>         if (flags & UART_CONFIG_TYPE)
>>                 port->type = PORT_16550A;
>>
>>> }
>> According to the straces, you get -EIO from ioctl and read which most 
>> likely means TTY_IO_ERROR bit set due to tiny_port->type = PORT_UNKNOWN 
>> (i.e. 0). Try the above.
> 
> Not quite, but it got me on the right track. I needed to set port->type
> before calling uart_add_one_port().

Ah,
.flags          = ASYNC_BOOT_AUTOCONF
I guess?

+ I'm sure you will need to set up more entries of your uart_port structure.
--
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/