All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <shahamit@gmail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RFI doesn't branch off?
Date: Wed, 25 Aug 2004 15:50:33 +0530	[thread overview]
Message-ID: <cghp5t$omm$1@sea.gmane.org> (raw)
In-Reply-To: 877aabc40408240724500bb006@mail.gmail.com


Amit Shah wrote:

>
> Hi all,
>
> I have a strange issue with a custom board running a 750GX on a
> Marvell 64360 bridge. I transferred control to the uImage via u-boot
> (which I had to modify for my board-specific UART and SDRAM inits,
> also disabling PCI).
>
> Using the UART that's initialized by u-boot, I put some putchar()s in
> head.S to figure out where the kernel was freezing. It seems 'rfi' in
> mmu_off doesn't jump off to '__after_mmu_off' as expected. I also put
> some pattern into SDRAM before an after mmu_off. I just see the
> pattern (via a PCI interface) put before mmu_off.
>
> The contents of SRR0 correctly point to __after_mmu_off just before
> the 'rfi'. However, the 'rfi' documentation says the value of SRR0 is
> concatenated with '0x0b00'. I don't think this should be done.
> Anyways, since this code is supposed to work, I'm not sure why it
> isn't working.

If I keep the DR enabled in MSR, the RFI goes back properly... disabling DR
causes some randomness.

>
> Can any u-boot initializations be causing this? I guess not, I've not
> touched any CPU-specific settings in u-boot.
>
> Can anyone give me some pointers?

--
Amit Shah
http://amitshah.nav.to/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-25 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:24 RFI doesn't branch off? Amit Shah
2004-08-25 10:20 ` Amit Shah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-05 17:34 Saari, James

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='cghp5t$omm$1@sea.gmane.org' \
    --to=shahamit@gmail.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.