From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Muhammad Waseem <vasim98@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Linuxppc-dev Digest, Vol 81, Issue 140
Date: Fri, 27 May 2011 06:35:16 -0400 [thread overview]
Message-ID: <20110527103516.GA2557@zod.rchland.ibm.com> (raw)
In-Reply-To: <BANLkTima3uLXvF3Zri5DjDDFHAB+CZMDgg@mail.gmail.com>
On Fri, May 27, 2011 at 12:26:20PM +0500, Muhammad Waseem wrote:
>I have developed a simple polling based serial device driver for PC's serial
>port (COM1: 0x3F8) which works fine. Now I want to implement the same on
>UART # 1 of PPC440EPx (Sequoia board).
>
>By changing the base address 0x3F8 to UART# 1 base address (0xEF600400) in
>Sequoia it does not work and return all the registers contents
>from 0xEF600400 to 0xEF600407 as 0xFF.
>
>Whereas existing ttyS1 driver works for UART# 1.
>
>How can I access the UART# 1 registers in a custom serial driver under
>kernel space.
If you post your driver code, we can review it.
josh
prev parent reply other threads:[~2011-05-27 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1306461602.19013.linuxppc-dev@lists.ozlabs.org>
2011-05-27 7:26 ` Linuxppc-dev Digest, Vol 81, Issue 140 Muhammad Waseem
2011-05-27 10:35 ` Josh Boyer [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=20110527103516.GA2557@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vasim98@gmail.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 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).