public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Status of the FB drivers on m68k
Date: Sat, 14 Oct 2017 13:23:44 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1710141310400.3@nippy.intranet> (raw)
In-Reply-To: <f65ab00c-8dad-f7a4-cba8-14c6d9fe3ce8@gmail.com>

On Sat, 14 Oct 2017, Michael Schmitz wrote:

> > - Michael Schmitz' ESP driver fixes for the Cyberstorm SCSI
> 
> Finn's fixes actually, and no guarantee what I have in mind will 
> actually work.
> 

Just to clarify, Michael and I did reach a solution (i.e. don't attempt 
2-byte DMA transfers) after we kicked around various theories for years, 
and tested some of them with Stan's help, and fixed some mac_esp and 
esp_scsi bugs along the way. But someone still has to write the code for 
zorro_esp. The code is easily adapted from mac_esp, now that mac_esp works 
properly, since you only have to implement the the transfer_size < 
FIFO_SIZE case or even just the write != 0 case. I can help with this 
patch if need be.

-- 

  reply	other threads:[~2017-10-14  2:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:32 Status of the FB drivers on m68k John Paul Adrian Glaubitz
2017-10-11  7:24 ` Geert Uytterhoeven
2017-10-11 11:09   ` Christian T. Steigies
2017-10-11 12:01   ` John Paul Adrian Glaubitz
2017-10-13 15:45     ` Michael Schmitz
2017-10-14  2:23       ` Finn Thain [this message]
2017-10-14  6:40         ` John Paul Adrian Glaubitz

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=alpine.LNX.2.00.1710141310400.3@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitzmic@gmail.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