From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linux-serial@vger.kernel.org, jacmet@sunsite.dk
Subject: Re: [RFC][PATCH] Xilinx uartlite serial driver
Date: Fri, 29 Sep 2006 15:57:51 -0400 [thread overview]
Message-ID: <451D7ABF.1010103@dlasys.net> (raw)
In-Reply-To: <20060913100110.1e33d885@localhost.localdomain>
Olof Johansson wrote:
> On Wed, 13 Sep 2006 15:39:09 +0200 Peter Korsgaard <jacmet@sunsite.dk> wrote:
>
>
>>>>>>> "Peter" == Peter Korsgaard <jacmet@sunsite.dk> writes:
>>>>>>>
>> Olof> 2. There seems to be some timeout issues with tx_empty.
>>
>> Peter> Huh, that's odd - I haven't noticed that. I'll test it again and get
>> Peter> back to you.
>>
>> Ahh, found it - I didn't update the uart timeout in set_termios so it
>> used a very long timeout. Please give the updated patch a try.
>>
>
> Looks good. Thanks.
>
Peter;
I am trying to switch from my driver to yours - as it appears yours is
on the way to getting accepted.
I have been dropping my issues/comments as I go onto the list as I
encounter problems.
You need an "early_serial_setup()" routine inside the
CONFIG_SERIAL_UARTLITE_CONSOLE code.
#if defined(CONFIG_SERIAL_UARTLITE_CONSOLE)
int __init
early_serial_setup(struct uart_port *port)
{
if (port->line >= ARRAY_SIZE(ulite_ports))
return -ENODEV;
ulite_init_ports();
ulite_ports[port->line].port = *port;
ulite_ports[port->line].port.ops = &ulite_pops;
return 0;
}
#endif
ulite_init_ports() loops through all the ports in ulite_ports and sets
up the port data - similiar to your code in ulite_probe().
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too
numerous to list.
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction."
Albert Einstein
next prev parent reply other threads:[~2006-09-29 20:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 14:23 [RFC][PATCH] Xilinx uartlite serial driver Peter Korsgaard
2006-05-11 22:20 ` Russell King
2006-05-16 9:48 ` Peter Korsgaard
2006-05-16 12:09 ` Sylvain Munaut
2006-05-16 12:53 ` Russell King
2006-05-16 13:03 ` Peter Korsgaard
2006-06-02 16:47 ` Russell King
2006-05-16 13:03 ` Sylvain Munaut
2006-05-16 13:07 ` Peter Korsgaard
2006-08-22 15:13 ` Peter Korsgaard
2006-09-12 14:33 ` Olof Johansson
2006-09-13 5:56 ` Peter Korsgaard
2006-09-13 13:39 ` Peter Korsgaard
2006-09-13 15:01 ` Olof Johansson
2006-09-29 19:04 ` David H. Lynch Jr.
2006-09-29 19:57 ` David H. Lynch Jr. [this message]
2006-10-04 15:45 ` Peter Korsgaard
2006-10-06 4:14 ` David H. Lynch Jr.
2006-09-30 9:25 ` David H. Lynch Jr.
2006-10-04 16:01 ` Peter Korsgaard
2006-10-06 4:15 ` David H. Lynch Jr.
2006-10-03 10:27 ` David H. Lynch Jr.
[not found] ` <451CDA3D.2060109@dlasys.net>
2006-10-04 15:41 ` Peter Korsgaard
2006-10-06 4:13 ` David H. Lynch Jr.
2006-10-06 4:14 ` David H. Lynch Jr.
2006-10-06 4:14 ` David H. Lynch Jr.
2006-10-19 23:06 ` Olof Johansson
2006-10-20 12:22 ` Peter Korsgaard
2006-09-28 10:14 ` David H. Lynch Jr.
2006-10-04 15:34 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2006-10-13 14:12 David H. Lynch Jr.
2006-10-13 14:45 ` Peter Korsgaard
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=451D7ABF.1010103@dlasys.net \
--to=dhlii@dlasys.net \
--cc=jacmet@sunsite.dk \
--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).