public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Brad Boyer <flar@allandria.com>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 33/36] m68k: drivers/scsi/mac53c94.c __iomem annotations
Date: Sat, 24 Dec 2005 22:32:30 +0000	[thread overview]
Message-ID: <20051224223230.GV27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20051224215633.GA17645@pants.nu>

On Sat, Dec 24, 2005 at 01:56:33PM -0800, Brad Boyer wrote:
> 
> This is a ppc only driver at the moment. The m68k mac version is mac_esp.
> I've been thinking about retrofitting this driver to use on the models
> that can do DMA, but that will require me to finish some of the work I
> have pending on the macio layer to get it working for nubus models.

Ah, OK...  Will move to ppc queue next time I rediff that stuff...

Speaking of mac_esp, there's a pending patch for NCR53C9x.c fixing PIO
breakage in esp_do_data().
		/* read fifo */
		for(j=0;j<fifocnt;j++)
			SCptr->SCp.ptr[i++] = esp_read(eregs->esp_fdata);

is not a good thing to do when we set .ptr to (char *)virt_to_phys_(....).

It works mostly by accident on e.g. 840AV, until you get a minimally
non-trivial memory mapping.  The same thing happens on the write side.
Fix is obvious (find phys_to_virt(SCptr->SCp.ptr) in the PIO branch
and use it).  I've put that in -bird, will show up in tonight's snapshot...

BTW, what's the situation with DMA on 840AV?  If you have any patches
to test, I've got such box and being what it is, it's not tied by any
work...

  reply	other threads:[~2005-12-24 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22  4:51 [PATCH 33/36] m68k: drivers/scsi/mac53c94.c __iomem annotations Al Viro
2005-12-24 21:56 ` Brad Boyer
2005-12-24 22:32   ` Al Viro [this message]
2005-12-24 22:44     ` Brad Boyer

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=20051224223230.GV27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=flar@allandria.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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