All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Commit 9c9bb6c89d4 breaks code execution from flash
Date: Thu, 13 May 2010 15:51:58 +0200	[thread overview]
Message-ID: <201005131551.58353.michael@walle.cc> (raw)
In-Reply-To: <4BEBF2AF.5010902@web.de>

Am Thursday 13 May 2010 14:38:07 schrieben Sie:
> >> Right, I came to the same conclusion based on chip I'm using for the
> >> Musicpal model. Working on a proper fix - now that I think to have found
> >> a solution for the XIP vs. mode switch conflict.
nice :) i'll try it as soon as it's ready.

> > Wait! Access to ident[0..3] is already correct as those fields are
> > stored and returned as 16-bit values. I guess you just did not pass the
> > proper IDs when registering your pflash_cfi02 instance.
> ... or you suffered from a be/le issue. In contrast to data, the ID is
> not swapped according to the byte order that was specified during init.
> Does your target byte order differ from your host?
oh sorry, i wrongly assumed id[0..3] were the bytes for the 
manufacturer/device id. using the correct 16 bit values for id0 and id2 works 
perfectly.

-- 
michael

      reply	other threads:[~2010-05-13 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 21:38 [Qemu-devel] Commit 9c9bb6c89d4 breaks code execution from flash Michael Walle
2010-04-23  7:23 ` [Qemu-devel] " Jan Kiszka
2010-05-07 20:57   ` Michael Walle
2010-05-12  7:56     ` Jan Kiszka
2010-05-12 23:02       ` Michael Walle
2010-05-13  7:38         ` Jan Kiszka
2010-05-13 10:58           ` Michael Walle
2010-05-13 11:46             ` Jan Kiszka
2010-05-13 11:57               ` Jan Kiszka
2010-05-13 12:38                 ` Jan Kiszka
2010-05-13 13:51                   ` Michael Walle [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=201005131551.58353.michael@walle.cc \
    --to=michael@walle.cc \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.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.