linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: neorf3k <neorf3k@gmail.com>
Cc: Linux Ppc Dev List Dev List <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Problem reading and programming memory location...
Date: Wed, 13 Nov 2013 08:32:59 +0100	[thread overview]
Message-ID: <20131113083259.1b69ed18@crub> (raw)
In-Reply-To: <985685C7-0122-4D45-96D1-4412E9774A5D@gmail.com>

On Tue, 12 Nov 2013 20:23:20 +0100
neorf3k <neorf3k@gmail.com> wrote:

> we have tried to read and program an 8bit register with 32bit address.
> we have mapped it with: ioremap, kmalloc etc=E2=80=A6 and then using: out=
b,
> iowrite8 etc.. but when we write to it, the value doesn=E2=80=99t change=
=E2=80=A6
> with other memory location is ok.
> That is an 8 bit register, located at 0x10020000 in a mpc5200b
> architecture. we are using kernel 2.6.33.=20
> what could be?

0x10020000 is not in the internal register memory map, so it
is probably a device on the LocalPlus bus. Did you configure
the chip select parameters for this device and did you enable
the associated chip select?
 =20
HTH,

Anatolij

  reply	other threads:[~2013-11-13  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 19:23 Problem reading and programming memory location neorf3k
2013-11-13  7:32 ` Anatolij Gustschin [this message]
2013-11-13 13:48   ` neorf3k
2013-11-13 18:06     ` Anatolij Gustschin
2013-11-14  8:38       ` neorf3k
     [not found]         ` <20131114100917.31f674d7@crub>
2013-11-14  9:49           ` neorf3k
2013-11-15 16:27           ` neorf3k
2013-11-16 14:29             ` Anatolij Gustschin
2013-11-16 15:11               ` neorf3k
2013-11-19 10:20               ` neorf3k
2013-11-19 21:45                 ` Anatolij Gustschin
2013-11-26 18:29                   ` neorf3k

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=20131113083259.1b69ed18@crub \
    --to=agust@denx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=neorf3k@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).