linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Xilinx UART Lite 2.6.18 driver
Date: Mon, 16 Oct 2006 21:49:43 +0200	[thread overview]
Message-ID: <873b9oqbvs.fsf@slug.be.48ers.dk> (raw)
In-Reply-To: <4532A1D1.4040006@dlasys.net> (David H. Lynch, Jr.'s message of "Sun, 15 Oct 2006 17:02:09 -0400")

>>>>> "David" == David H Lynch <dhlii@dlasys.net> writes:

Hi,

 >> I'm still not convinced that DCR access and variable register
 >> offsets are needed - But it can always be added (through a
 >> seperate struct in platform_data) - Patches are welcome.

 David>     It does not matter whether you or I are convinced. It
 David> matters whether there are people that need it.  Xilinx has a
 David> reference design that uses DCR. While I have never tripped
 David> over an actual implimentation that uses DCR there are others
 David> on this list that have.

Those people are welcome to add it then. Benh recently posted some
patches with a dcr abstraction that could probably make it pretty
clean to add.

 David>     Right now I can not get your driver to work. I spent alot
 David> of time trying to fix it and got nowhere.  I can not get it to
 David> receive at all, and I can not get it to send after switching
 David> from the console driver without dropping characters. I am very
 David> busy with other things right now and it is going to be a long
 David> time before I have time to look at your driver again.

Sorry to hear. We are using it in several designs without problems and
it also worked for Oluf. I'm afraid I won't be able to help you
anymore unless you provide more details.

 David>     But what matters is not whether the changes are intrusive,
 David> but whether they produce a better result.

Sorry, I don't agree. Maintainability is very important.

 David>     I am glad somebody is using your driver and finding it
 David> works. But we are all better served by fixing the failure
 David> cases.

Yes, please do or provide enough details for me to reproduce it.

 David>     It is not particularly odd at all. The UartLite despite
 David> its simplicity is worse than a normal driver - different FPGA
 David> implimentations can vary. Normal drivers for fixed inflexible
 David> hardware often do not work accross differing implimentations,
 David> why would you expect something like UartLite to be invariant ?

It's no worse than Xilinx 8250 core. There's only 1 implementation of
the uarlite IP core - Xilinx's.

 David>     I would also ask what data rates you and others with
 David> Working UartLites are using ?  The cases I am dealing with run
 David> at 57600 and 115200 respectively - it is not that odd for
 David> driver problems to manifest themselves only or more frequently
 David> at high baud rates.

We're using 115200 for most designs, but one design is using it at
1mbit.

 David>     Without being difficult - don't hold your breath. It is
 David> something I would like to do, but I do not have infinite time.

Ok.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2006-10-16 19:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 20:49 [PATCH] Xilinx UART Lite 2.6.18 driver David Bolcsfoldi
2006-10-10 22:04 ` Grant Likely
2006-10-11 22:06 ` David H. Lynch Jr.
2006-10-12 10:34 ` Peter Korsgaard
2006-10-12 21:12   ` David Bolcsfoldi
2006-10-13  5:21     ` David Bolcsfoldi
2006-10-13  7:04       ` David H. Lynch Jr.
2006-10-13  7:22         ` Peter Korsgaard
     [not found]           ` <45329C42.3030000@dlasys.net>
2006-10-16 19:42             ` Peter Korsgaard
2006-10-13  7:11       ` Peter Korsgaard
2006-10-15 23:48         ` David Bolcsfoldi
2006-10-20 19:41           ` Peter Korsgaard
2006-10-27 15:03             ` Peter Korsgaard
2006-10-28  3:29               ` David H. Lynch Jr.
2006-10-30  8:23                 ` Peter Korsgaard
2006-10-31 17:26                   ` David H. Lynch Jr.
2006-10-30 19:45               ` David Bolcsfoldi
2006-11-06 15:44                 ` Peter Korsgaard
2006-10-13  6:48     ` David H. Lynch Jr.
2006-10-13  7:15       ` Peter Korsgaard
2006-10-15 21:02         ` David H. Lynch Jr.
2006-10-16 19:49           ` Peter Korsgaard [this message]
2006-10-16 19:52           ` Peter Korsgaard
2006-10-13  7:08     ` 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=873b9oqbvs.fsf@slug.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=dhlii@dlasys.net \
    --cc=linuxppc-embedded@ozlabs.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).