public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: balrogg@gmail.com
Cc: OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: OMAP emulation
Date: Wed, 22 Mar 2006 07:17:06 -0800	[thread overview]
Message-ID: <20060322151704.GB5748@atomide.com> (raw)
In-Reply-To: <fb249edb0603220157p710b6091t@mail.gmail.com>

* andrzej zaborowski <balrog@zabor.org> [060322 01:57]:
> On 20/03/06, Tony Lindgren <tony@atomide.com> wrote:
> >
> > Sounds like you have already verified the memory timings. Does it work
> > properly with caches disabled?
> Unfortunately nope, for me at least. Except the slowdown, it changes
> the places where the bug appears (i.e. where the programs break) but
> it is because when I disable the caches in the config, it enables two
> new instructions in head.S. Now, if I replace these two instructions
> with any random instructions the result is the same.

Hmmm. And your root file system obviously is not corrupted and works
fine on other omaps?
 
> The QEMU effort is not wasted I think :)  My new idea is to simulate
> the Linux booting from the reset of the device, when it loads PalmOS
> (which is the OS that comes with the device in a ROM) through the
> Linux bootloader which then gradually unloads PalmOS and only then
> jumps to the kernel. This will maybe allow me to find out what
> registers is PalmOS messing with and reset those in the bootloader to
> their default values because there is plenty of registers that Linux
> doesn't touch when it's booting ( -- for example yesterday we found
> out that on Zire 71 (a different PDA based on OMAP 310) the mpu
> watchdog timer is always enabled in PalmOS and that was (correctly)
> triggering mysterious resets of the device everytime Linux took over
> the control -- until yesterday).

Yeah, it's really nice to have an omap emulator :)

Tony

      reply	other threads:[~2006-03-22 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 17:33 OMAP emulation andrzej zaborowski
2006-03-20 14:19 ` Tony Lindgren
2006-03-22  9:57   ` andrzej zaborowski
2006-03-22 15:17     ` tony [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=20060322151704.GB5748@atomide.com \
    --to=tony@atomide.com \
    --cc=balrogg@gmail.com \
    --cc=linux-omap-open-source@linux.omap.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