From: Peter Korsgaard <jacmet@sunsite.dk>
To: John Williams <john.williams@petalogix.com>
Cc: monstr@seznam.cz, Josh Boyer <jwboyer@linux.vnet.ibm.com>,
Grant Likely <grant.likely@secretlab.ca>,
linux-serial@vger.kernel.org,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Subject: Re: Uartlite driver
Date: Mon, 12 May 2008 09:43:58 +0200 [thread overview]
Message-ID: <87lk2garwh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1210545557.5798.267.camel@localhost> (John Williams's message of "Mon\, 12 May 2008 08\:39\:17 +1000")
>>>>> "John" == John Williams <john.williams@petalogix.com> writes:
Hi,
John> The uartlite register set is 32 bits wide - that's what the datasheet
John> says, and that's how we should interact with it. I really don't
John> understand why this commit was reverted.
John> Who uses the uartlite driver for anything other than the uartlite?
Me (the author of uartlite.c). We have designs where we needed more
uarts, but didn't have any more room/ I/O pins on the virtex, so we
have implemented an uartlite compatible interface in a S3E connected
through a 16bit bus.
Not exactly brilliant hw design, but it works and it keeps the sw
support to a minimum.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-05-12 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 14:01 Uartlite driver Michal Simek
2008-05-11 22:39 ` John Williams
2008-05-12 4:31 ` Grant Likely
2008-05-12 6:15 ` Michal Simek
2008-05-15 14:31 ` David H. Lynch Jr.
2008-05-15 16:39 ` Stephen Neuendorffer
2008-05-16 7:41 ` Peter Korsgaard
2008-05-15 14:45 ` Uartlite driver & CONFIG_CONSOLE_POLL David H. Lynch Jr.
2008-05-16 7:47 ` Peter Korsgaard
[not found] ` <482E5BD0.1080306@dlasys.net>
2008-05-18 19:04 ` Peter Korsgaard
2008-05-12 7:43 ` Peter Korsgaard [this message]
[not found] <3454.6513-24750-698925460-1197275267@seznam.cz>
2007-12-12 15:31 ` uartlite driver Grant Likely
2007-12-12 20:14 ` Michal Simek
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=87lk2garwh.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-serial@vger.kernel.org \
--cc=monstr@seznam.cz \
--cc=stephen.neuendorffer@xilinx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.