From: Sam Creasey <sammy@sammy.net>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-m68k@vger.kernel.org, linux-scsi@vger.kernel.org,
Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Subject: Re: [linux-m68k] mac scsi, ncr5380
Date: Fri, 26 Sep 2008 10:40:55 -0400 [thread overview]
Message-ID: <20080926144055.GS10918@sammy.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0809240019001.3458@loopy.telegraphics.com.au>
On Fri, Sep 26, 2008 at 06:27:05PM +1000, Finn Thain wrote:
> There is so much duplication of code for the NCR5380 drivers -- sun3,
> atari, g_NCR5380, 2.4 & 2.2 branches in the mac68k CVS -- that I don't
> know where to start looking for fixes.
>
> Thinking that the bug would be trivial, I started out writing cleanup
> patches for the existing mac_scsi.c/NCR5380.c combination. But the more I
> think about it, the less I want to go in that direction.
>
> Now I'm thinking that mac_scsi should adopt the atari core, since that
> appears to be the better maintained contender. Michael, does that sound
> sensible? Does it have working PDMA?
>
> Another thing, should we look at merging sun3_NCR5380.c and
> atari_NCR5380.c? The diff is huge, but that is because of the code style
> and formatting cleanups in atari_NCR5380.c. The functional differencess
> are few and far between.
>
> If we can get to a working, common sun3/atari/mac core, I could then look
> at minimising C preprocessor abuse in favour of a cleaner link-time/ops
> struct abstraction layer -- with some assistance from Micheal and Sam: I'm
> assuming that there is a cut somewhere that would make for a broadly
> useful interface. Does this make sense?
It makes sense, I think. I'm trying to remember what hackery I had
to do which led me to fork the driver in the first place -- I'm fairly
sure that the main differences were related to the dma controller on
the OBIO sun3's (50/60) being very picky about what bus phases you
programmed the DMA controller during, and this not working well with
the model in place in the version of atari_NCR5380 which I started
with (it's only been 9 years, you'd think I'd know this... :)
I can't actually recall what the requirments are at the moment. most
of the sun3* function calls seem to be centered around making sure DMA
is configured in the CMDOUT phase and started in the DATAIN/DATAOUT
phases (is this why I commented out merge_contiguous_buffers() in
NCR5380_transfer_dma?)
Let me know if you start making progress, I'll be happy to let ya know
anything else I can rememeber, or to try to bring a kernel up on real
hardware (I think a couple of them still boot... :)
-- Sam
next prev parent reply other threads:[~2008-09-26 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 8:27 mac scsi, ncr5380 Finn Thain
2008-09-26 14:40 ` Sam Creasey [this message]
2008-09-27 3:10 ` Michael Schmitz
2008-09-27 8:00 ` Finn Thain
2008-09-27 19:12 ` Brad Boyer
2008-09-28 11:28 ` Finn Thain
2008-09-28 18:03 ` Brad Boyer
2008-09-29 13:22 ` Finn Thain
2008-09-29 23:18 ` Brad Boyer
2008-09-30 8:40 ` Finn Thain
2008-09-29 21:03 ` Riccardo
2008-09-30 6:18 ` Finn Thain
2008-09-28 13:16 ` Boaz Harrosh
2008-09-30 8:45 ` Christoph Hellwig
2008-10-01 8:04 ` Finn Thain
2008-10-01 7:19 ` Finn Thain
2008-10-02 8:33 ` Boaz Harrosh
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=20080926144055.GS10918@sammy.net \
--to=sammy@sammy.net \
--cc=fthain@telegraphics.com.au \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schmitz@biophys.uni-duesseldorf.de \
/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