From: Paolo Bonzini <pbonzini@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Hannes Reinecke <hare@suse.de>,
Matthew Wilcox <willy@linux.intel.com>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [PATCH] lsi53c895a: Add missing registers and workaround for OS/2 Warp SYM8XX.ADD driver
Date: Thu, 30 Sep 2010 10:07:43 +0200 [thread overview]
Message-ID: <4CA4454F.30402@redhat.com> (raw)
In-Reply-To: <1285823254-6699-1-git-send-email-nab@linux-iscsi.org>
On 09/30/2010 07:07 AM, Nicholas A. Bellinger wrote:
> case 0x06: /* SDID */
> - if ((val& 0xf) != (s->ssid& 0xf))
> - BADF("Destination ID does not match SSID\n");
> + /*
> + * This workaround is required by the SYM8XX.ADD driver for OS/2 Warp.
> + */
> + if ((val& 0xf) != (s->ssid& 0xf)) {
> + DPRINTF("Destination ID does not match SSID, val: %02x"
> + " s->ssid: %02x, fixing up val\n", val, s->ssid);
> + val = s->ssid;
> + }
> s->sdid = val& 0xf;
> break;
I don't think the write is bogus, as the manual says "Writing these bits
set the SCSI ID of the intended initiator or target during SCSI
reselection or selection phases, respectively".
The value is never used by the device model, only read/written according
to SCRIPTS and register read/writes. How does the OS/2 driver use it?
Have you tried, just removing the "if" without replacing it?
Paolo
next prev parent reply other threads:[~2010-09-30 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 5:07 [Qemu-devel] [PATCH] lsi53c895a: Add missing registers and workaround for OS/2 Warp SYM8XX.ADD driver Nicholas A. Bellinger
2010-09-30 8:07 ` Paolo Bonzini [this message]
2010-09-30 21:29 ` [Qemu-devel] " Nicholas A. Bellinger
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=4CA4454F.30402@redhat.com \
--to=pbonzini@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).