linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Knutsson <tobias.knutsson@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: writel hangs system
Date: Fri, 13 Feb 2009 07:30:48 +0100	[thread overview]
Message-ID: <ccb913ac0902122230t12e2977dw2bf720e4710b1438@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40902121318i65ec44edtf119a6ad2d4d1570@mail.gmail.com>

There seems to be some magic force linked to this mailing list.
Whenever I post a question, the matter seems to resolve itself. :)

In order to stay as consistent as possible with the old 2.4 kernel, I
used the same mapping that they had:

0x50000000 - 0x6000000000 for memory
0x60000000 - 0x6100000000 for I/O

When I changed it to the default that was in the lite5200b device tree
I could access the memory regions as well.

Thanks for your help!

On Thu, Feb 12, 2009 at 22:18, Grant Likely <grant.likely@secretlab.ca> wro=
te:
> On Tue, Feb 10, 2009 at 6:07 AM, Tobias Knutsson
> <tobias.knutsson@gmail.com> wrote:
>> Hello,
>>
>> I'm in the process of porting a PCI-driver for a dsp-board from 2.4 to
>> 2.6. The probing of the driver goes well, IRQs are setup, resources
>> are claimed and remapped without any problems. Reading from I/O
>> regions also works well. However, when i try to read or write to a
>> memory region using readl/writel, the system instantly hangs. No
>> stacktrace or anything, it just stops.
>
> Hmmm.  Not good.  Are you able to access the memory regions from the
> U-Boot console?
>
> g.
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
>



--=20

H=E4lsningar/Regards
Tobias Knutsson

      reply	other threads:[~2009-02-13  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 13:07 writel hangs system Tobias Knutsson
2009-02-12 21:18 ` Grant Likely
2009-02-13  6:30   ` Tobias Knutsson [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=ccb913ac0902122230t12e2977dw2bf720e4710b1438@mail.gmail.com \
    --to=tobias.knutsson@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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).