From: Brad Boyer <flar@allandria.com>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Joshua Juran <jjuran@gmail.com>,
Laurent Vivier <laurent@lvivier.info>,
Finn Thain <fthain@telegraphics.com.au>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: I'm back on linux-m68k
Date: Tue, 4 Nov 2008 09:59:55 -0800 [thread overview]
Message-ID: <20081104175954.GA31150@cynthia.pants.nu> (raw)
In-Reply-To: <alpine.DEB.1.00.0811040818320.2519@zirkon.biophys.uni-duesseldorf.de>
On Tue, Nov 04, 2008 at 08:25:31AM +0100, Michael Schmitz wrote:
> The new esp code is much cleaner and should be easier to adapt to a new bus
> model (I won't deny Nubus might not have quirks of its own there - bus width
> may be an issue, bytes may come spaced by null bytes, you name it, Apple
> thought of it).
The generic nubus code already has some of the bus width problems handled
because it needs to be able to read the ROM chips. It is something of a
pain since it has to support nearly arbitrary arrangements of byte lanes.
> No idea how PDMA would work - may there is a DMA chip even?
Well, I do know that some NuBus cards have real DMA. The problem is that
it's always card specific. There is never a bus-level DMA controller. I
would hope that a high performance SCSI card would have that, but I've
only seen explicit mention of it on video cards. I'll probably try PIO
first, then try to see if it does DMA. It's possible the card just has
a bunch of local memory for buffers like some ethernet cards.
> > This could also be an excuse to dig in to nubus.c as well and get a real
> > device model framework there.
>
> The best excuse :-)
Now I just have to find the time.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2008-11-04 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 9:38 I'm back on linux-m68k Joshua Juran
2008-10-15 14:20 ` Finn Thain
2008-10-15 19:24 ` Tony Mantler
2008-10-15 23:05 ` Laurent Vivier
2008-10-16 0:44 ` Finn Thain
2008-10-16 6:05 ` Laurent Vivier
2008-10-16 6:42 ` Finn Thain
2008-10-16 9:44 ` Joshua Juran
2008-11-03 11:40 ` Joshua Juran
2008-11-03 12:01 ` Geert Uytterhoeven
2008-11-03 19:47 ` Brad Boyer
2008-11-03 21:15 ` Michael Schmitz
2008-11-03 22:37 ` Brad Boyer
2008-11-04 7:25 ` Michael Schmitz
2008-11-04 17:59 ` Brad Boyer [this message]
2008-11-04 8:05 ` Joshua Juran
2008-11-04 18:37 ` Riccardo
2008-11-08 9:00 ` Joshua Juran
2008-11-08 13:12 ` Finn Thain
2008-11-08 16:14 ` Joshua Juran
2008-11-09 2:05 ` 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=20081104175954.GA31150@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=jjuran@gmail.com \
--cc=laurent@lvivier.info \
--cc=linux-m68k@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