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: Mon, 3 Nov 2008 14:37:51 -0800 [thread overview]
Message-ID: <20081103223751.GB19432@cynthia.pants.nu> (raw)
In-Reply-To: <alpine.DEB.1.00.0811032208480.15114@zirkon.biophys.uni-duesseldorf.de>
On Mon, Nov 03, 2008 at 10:15:41PM +0100, Michael Schmitz wrote:
> > It is also possible to add SCSI buses. I have a NuBus SCSI card that has
> > a 53c9x chip of some flavor on it, although I haven't tried it and suspect
> > that it would take some work to get it supported in Linux. Having a NuBus
>
> The 53C9x won't be that hard, but you'll have to write register access code
> going through NUBUS instead of memory mapped IO. The NUBUS ethernet drivers
> should have plenty of sample code. Leaves the exercise of locating the chip
> in the slot address space :-)
Well, I did buy the card with the intent of getting a Linux driver working
at some point. It's just not that close to the top of my list. I also have
not really looked at the esp code (either the old or new version) other
than a superficial look at mac_esp.c when Finn was making some fixes. It
doesn't sound too bad from the way you describe it. If it's as easy as
taking mac_esp.c and copying it to nubus_esp.c and writing a new probe
function to detect and setup the card, that shouldn't take long. I notice
that mac_esp.c already uses nubus functions to do some of the work, and
the address space the driver uses for PDMA is in a range normally used
by the nubus code while the device registers are in regular IO space.
This could also be an excuse to dig in to nubus.c as well and get a real
device model framework there.
> > SCSI card was a good option to upgrade performance of some of the mid-range
> > systems where Apple was still using the NCR5380 but better chips were
> > available. I'm pretty sure Apple supported booting off these as long as
> > they had the correct software in the ROM on the card.
>
> Possible, but someone will just have to report what XPRAM data this would
> set. And booting Linux off these without having a way of writing the kernel
> to that bus won't make much sense.
I guess I'll try booting from the card whenever I actually put it in something.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2008-11-03 22:38 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 [this message]
2008-11-04 7:25 ` Michael Schmitz
2008-11-04 17:59 ` Brad Boyer
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=20081103223751.GB19432@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