LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Charles Krinke <ckrinke@istor.com>
Cc: Randy Brown <rbrown@istor.com>,
	Vahid Fereydounkolahi <vahidf@istor.com>,
	Chris Carlson <ccarlson@istor.com>,
	Kevin Smith <ksmith@istor.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Accessing 8541 registers from user space
Date: Wed, 16 May 2007 19:36:43 -0500	[thread overview]
Message-ID: <5C1556B6-714A-4D64-AA35-B4BA539F333F@kernel.crashing.org> (raw)
In-Reply-To: <9F3F0A752CAEBE4FA7E906CC2FBFF57C06A210@MERCURY.inside.istor.com>


On May 16, 2007, at 4:59 PM, Charles Krinke wrote:

> I have a need to be able to read and write the gpio data registers  
> PDATC
> and PDATD from a user space program.
>
> We have a userspace program that succesfully mmaps an offset in / 
> dev/mem
> and reads/writes registers in a CPLD at 0xFF00_0000.
>
> The issue seems to be that when I mmap /dev/mem to 0xE000_0D50 to read
> the PDATC register, Linux-2.6.17.11 just locks up.
>
> Can anyone shed a little light on why this could be happening?

One theory is you aren't reading PDATC at the right offset.  Not sure  
what happens if you read a non-existent register offset.

I'm think you want 0xe009_0d50.

- k

      reply	other threads:[~2007-05-17  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 14:25 BDI2000 configuration file for MPC8313E-RDB Frank Prepelica
2007-05-16 20:37 ` Leonid
2007-05-16 21:59   ` Accessing 8541 registers from user space Charles Krinke
2007-05-17  0:36     ` Kumar Gala [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=5C1556B6-714A-4D64-AA35-B4BA539F333F@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=ccarlson@istor.com \
    --cc=ckrinke@istor.com \
    --cc=ksmith@istor.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rbrown@istor.com \
    --cc=vahidf@istor.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