qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] ESP: misc fixes
Date: Sat, 29 Nov 2008 16:54:19 +0100	[thread overview]
Message-ID: <493165AB.9050300@reactos.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

Hi,

Attached patches fix a few problems with ESP scsi card emulation.


Misc fixes (esp_1_misc.diff)
- Fix internal fifo size (16 bytes), according to 
http://www.ibiblio.org/pub/historic-linux/early-ports/Sparc/NCR/NCR53C9X.txt
- Fix values of STAT_MI and STAT_MO
- Give a scsi ID to adapter, and prevent this ID to be used by devices
- Prevent fifo overrun in esp_mem_writeb
- Add a ESP_ERROR macro, and use it where appropriate


Fix configuration 2 register (esp_2_cfg2.diff):
According to 
http://www.ibiblio.org/pub/historic-linux/early-ports/Sparc/NCR/NCR53C9X.txt 
, "Any bit pattern written to this register
may be read back and should be identical"


Fix command len detection (esp_3_cmdlen.diff)
When command is not DMA, TCMID and TCLO registers are not filled. Use 
command buffer len instead


Fix 'enable selection' command (esp_4_ensel.diff)
Indicate success after 'enable selection' command


Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>


These patches have been tested on Sparc SS-5 and on Mips Magnum emulations.

Hervé

[-- Attachment #2: esp_4_ensel.diff --]
[-- Type: plain/text, Size: 403 bytes --]

[-- Attachment #3: esp_1_misc.diff --]
[-- Type: plain/text, Size: 3531 bytes --]

[-- Attachment #4: esp_2_cfg2.diff --]
[-- Type: plain/text, Size: 581 bytes --]

[-- Attachment #5: esp_3_cmdlen.diff --]
[-- Type: plain/text, Size: 801 bytes --]

             reply	other threads:[~2008-11-29 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 15:54 Hervé Poussineau [this message]
2008-11-29 16:51 ` [Qemu-devel] [PATCH] ESP: misc fixes Blue Swirl
2008-11-29 17:30 ` Blue Swirl

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=493165AB.9050300@reactos.org \
    --to=hpoussin@reactos.org \
    --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 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).