All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Missing Diag/Debug Registers in lsi53c895a emulation
Date: Mon, 12 Jan 2015 10:28:02 +0100	[thread overview]
Message-ID: <54B393A2.3090702@kamp.de> (raw)

Hi,

while trying to run an ASA1000V appliance I found that registers 0x09 and 0x3c-3f are read during boot up. Which
currently results in an exit(1). The appliance uses an quite ancient 2.6.29.6 Linux kernel.
These registers are mainly for diag and debug purposes so I came up with the following patch. The system works
with the following patch, but I wonder if this is a correct workaround:

diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/lsi53c895a.c
index ec92048..bce1135 100644
--- a/hw/scsi/lsi53c895a.c
+++ b/hw/scsi/lsi53c895a.c
@@ -1513,6 +1513,8 @@ static uint8_t lsi_reg_readb(LSIState *s, int offset)
          return 0x7f;
      case 0x08: /* Revision ID */
          return 0x00;
+    case 0x09: /* SOCL */
+        return 0x00;
      case 0xa: /* SSID */
          return s->ssid;
      case 0xb: /* SBCL */
@@ -1577,6 +1579,11 @@ static uint8_t lsi_reg_readb(LSIState *s, int offset)
          return s->sbr;
      case 0x3b: /* DCNTL */
          return s->dcntl;
+    case 0x3c: /* ADDER Output (Debug purpose only) */
+    case 0x3d:
+    case 0x3e:
+    case 0x3f:
+        return 0x00;
      case 0x40: /* SIEN0 */
          return s->sien0;
      case 0x41: /* SIEN1 */

Peter

             reply	other threads:[~2015-01-12  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12  9:28 Peter Lieven [this message]
2015-01-12  9:39 ` [Qemu-devel] Missing Diag/Debug Registers in lsi53c895a emulation Peter Lieven
2015-01-12  9:42   ` Paolo Bonzini
2015-01-12  9:45     ` Peter Lieven

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=54B393A2.3090702@kamp.de \
    --to=pl@kamp.de \
    --cc=pbonzini@redhat.com \
    --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.