linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: vb <vb@vsbe.com>
To: linuxppc-embedded@ozlabs.org
Subject: Accessing peripheral bus devices on 460GT
Date: Wed, 6 Aug 2008 22:52:53 -0400	[thread overview]
Message-ID: <f608b67d0808061952g3d1b658bp7179e3990c5b105b@mail.gmail.com> (raw)

I am trying to bring up a 2.6.25 based system on a 460GT platform. I
am using the OF tree cloned off canyonblands.dts, and I am not sure if
something is missing in the tree, or in the kernel, or I am doing
something stupid.

The problem is that I don't seem to be able to access any peripheral
device activated by cs1, 2, 3 (I have not tried touching the NOR flash
(cs0) just yet). If I don't touch any peripherals the system can
netbboot or diskboot all the way to the linux prompt.

But unfortunately, the damn peripherals have to be touched :-)

I do invoke ioremap_nocache(<phys addr>, <addr range size>), and it
returns a virtual address. The thing is that as soon as I try
accessing the device off this pointer an exception is thrown. From
u-boot  I can access the <phys addr>..+<addr range size> space no
problem.

 I see that the dts file mentions that u-boot is supposed to supply
the "ranges" property in the /plb/opb/ebc section; examining the
u-boot code for different amcc platforms shows that only the NOR flash
size is supplied there.

I guess the real question is how do I gain access to the EBC mapped
hardware configured by u-boot?

can someone please shed any light on this,

thanks a lot in advance,

Vadim

                 reply	other threads:[~2008-08-07  2:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f608b67d0808061952g3d1b658bp7179e3990c5b105b@mail.gmail.com \
    --to=vb@vsbe.com \
    --cc=linuxppc-embedded@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).