From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PXA320] How to find I/O registers, base address of ASIX ethernet chip?
Date: Mon, 8 Feb 2010 10:13:48 +0100 [thread overview]
Message-ID: <20100208091348.GC15255@pengutronix.de> (raw)
In-Reply-To: <33061265619560@webmail103.yandex.ru>
On Mon, Feb 08, 2010 at 11:59:20AM +0300, Dennis Semakin wrote:
> Hello
>
> > > In U-BOOT:
> > >
> > > MSC1 (address 0x4a00000c) - 0x0779
> > > $ md.w 0x4a00000c
> > > 4a00000c: 0779 0000 0000 0000 0000 0000 0000 0000 y...............
> > > 4a00001c: 0008 0000 0000 0000 0000 0000 0000 0000 ................
> > > 4a00002c: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> > > 4a00003c: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> > >
> > > CSADRCFG2 (address 0x4a000088) - 0032c809
> > > $ md.l 0x4a000088
> > > 4a000088: 0032c809 00020000 00020000 00000000 ..2.............
> > > 4a000098: 00000000 00000000 00000000 00000000 ................
> > > 4a0000a8: 00000000 00000000 00000000 00000000 ................
> > > 4a0000b8: 00000000 00000000 00000000 00000000 ................
> > > 4a0000c8: 00000000 00000000 00000000 00000000 ................
> >
> > Can you access 0x1000_0000 from U-Boot? Did you switch on the clock for
> > the static bus? This is also not done by the kernel currently.
> >
> > Daniel
> >
> >
>
> No, I cannot access 0x1000_0000 from U-Boot. The system hangs, when I access to this address
This sounds like a missing clock. Ah, and Daniel already asked that,
too: "Did you switch on the clock for the static bus?"
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-02-08 9:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 9:21 [PXA320] How to find I/O registers, base address of ASIX ethernet chip? Dennis Semakin
2010-02-04 12:28 ` Eric Miao
2010-02-04 13:09 ` Dennis Semakin
2010-02-04 13:24 ` Dennis Semakin
2010-02-04 13:31 ` Dennis Semakin
2010-02-05 4:26 ` Daniel Mack
2010-02-05 7:53 ` Uwe Kleine-König
2010-02-07 5:11 ` Daniel Mack
2010-02-08 6:06 ` Eric Miao
2010-02-05 8:02 ` Dennis Semakin
2010-02-07 5:13 ` Daniel Mack
2010-02-08 8:58 ` Dennis Semakin
2010-02-08 8:59 ` Dennis Semakin
2010-02-08 9:13 ` Uwe Kleine-König [this message]
2010-02-08 9:31 ` Dennis Semakin
2010-02-08 9:38 ` Dennis Semakin
2010-02-08 10:15 ` Daniel Mack
2010-02-08 12:16 ` Dennis Semakin
2010-02-08 12:49 ` Daniel Mack
2010-02-08 14:13 ` Dennis Semakin
2010-02-08 12:16 ` Dennis Semakin
2010-02-08 9:57 ` Dennis Semakin
2010-02-07 6:53 ` Mike Rapoport
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=20100208091348.GC15255@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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