linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ormund Williams <ormundw@brainlink.com>
To: Linux PPC embedded <linuxppc-embedded@lists.linuxppc.org>,
	Linux PPC embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: UART configuration problems
Date: Mon, 15 Jan 2001 16:13:04 -0500	[thread overview]
Message-ID: <3A6367E0.1D9499FE@brainlink.com> (raw)
In-Reply-To: 008201c07eec$52fd7da0$4a1f76d8@washington


Navin Boppuri wrote:
>
> Hello Ormund,
>
> >From your mail, I can make out that you worked on the MAX3100 uart before.
> Can you please tell me how I can do a read from the buffer? I am confused as
> to how to read the buffer without overwriting it with the following data.
> How much delay is the right delay? Please help, I am kinda stuck here.
>
I have no experience with the 823, my interest in PPC-Linux is for a
future project using the IBM 403GC, I am familiar with the 3100 from
another project.

I had already sent you the following steps for reading the FIFO without
loosing characters, you must read the entire FIFO to clear it.

Here are the steps to take:

        1. Read 16bit data from 3100
        2. Check R (bit 15) to see if there is data in FIFO
        3. If R is set: check Framing Error (bit 10)
           and Parity, if used (bit 8), read the character (bit 0-7)
        4. Do the above 3 three steps till R is clear
        5. Set delay for 60 x baud rate period
           (for 9600bps 8-n-1: 6250 micro seconds)

I am assuming that you are not using the interrupt pin on the 3100.

I see that you have written a driver for SPI can you send me a copy?
TIA.

--
Ormund

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-15 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12 18:06 UART configuration problems Navin Boppuri
2001-01-13  2:30 ` Ormund Williams
2001-01-15 12:11   ` Navin Boppuri
2001-01-15 21:13     ` Ormund Williams [this message]

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=3A6367E0.1D9499FE@brainlink.com \
    --to=ormundw@brainlink.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).