From: Peter Korsgaard <jacmet@sunsite.dk>
To: Olof Johansson <olof@lixom.net>
Cc: rmk+serial@arm.linux.org.uk, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Xilinx uartlite serial driver
Date: Wed, 13 Sep 2006 07:56:03 +0200 [thread overview]
Message-ID: <87ejugxqbw.fsf@slug.be.48ers.dk> (raw)
In-Reply-To: <20060912093301.77f75bfb@localhost.localdomain> (Olof Johansson's message of "Tue, 12 Sep 2006 09:33:01 -0500")
>>>>> "Olof" == Olof Johansson <olof@lixom.net> writes:
Hi Olof, thanks for looking into the driver..
Olof> In my opinion there's a few pieces missing:
Olof> 1. There's no early boot console support for PPC. There's another
Olof> uartlite patch that's floating around that has this, very useful for
Olof> early bringup tasks. I'd like to see this expanded to include that as
Olof> well (the regular part of the other driver seems more or less broken
Olof> though, so this is a better base driver). That shouldn't stop this part
Olof> of the driver to go in though, just possible future work.
True. The board I have an uartlite on also has a 8250 so it hasn't
been an issue for me so far - But it would indeed be a nice
addition. Adding new stuff to arch/ppc at this moment isn't that
sensible, so perhaps it makes most sense to wait til 4xx is supported
under arch/powerpc?
Olof> 2. There seems to be some timeout issues with tx_empty. If I boot a
Olof> regular distro with getty, etc, I get veeeery slow console output right
Olof> when init starts up. Adding a small default timeout in the init of the
Olof> uart code seems to help -- the hanging thread seems to be sleeping in
Olof> uart_wait_until_sent(). I picked a value of '5', seems ok. (Also,
Olof> without this fix, getty won't start on the port for some reason, it
Olof> sits in the same timeout forever, or at least for a very long time).
Huh, that's odd - I haven't noticed that. I'll test it again and get
back to you.
Olof> 3. It would be useful to demonstrate how to hook up the device all the
Olof> way through to the board port (i.e. add a config option and include it
Olof> in the ml403 platform code or similar). It's not hard, but it'd make it
Olof> easier for whomever comes next. Of course, with 4xx hopefully soon
Olof> moving over to arch/powerpc, this would be taken care of through the
Olof> device tree instead.
Yes - Afaik none of the Xilinx boards comes with uartlites
configured so it's not usable out-of-the-box, but you can ofcause do a
setup with the proper #ifdefs like the 8250 stuff in virtex.c.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2006-09-13 5:56 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 [this message]
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.
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=87ejugxqbw.fsf@slug.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rmk+serial@arm.linux.org.uk \
/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).