From: Matthew Wilcox <willy@debian.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Matthew Wilcox <willy@debian.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
parisc-linux@parisc-linux.org,
linux-apus-devel@lists.sourceforge.net
Subject: [parisc-linux] Re: NCR53c720
Date: Mon, 29 Sep 2003 14:33:17 +0100 [thread overview]
Message-ID: <20030929133317.GP24824@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0309291434260.17812-100000@serv>
On Mon, Sep 29, 2003 at 02:53:16PM +0200, Roman Zippel wrote:
> Hi,
>
> On Mon, 29 Sep 2003, Geert Uytterhoeven wrote:
>
> > > Are there any Amiga cards that are 720 based?
> >
> > I don't know for sure. Probably not (cfr. above).
>
> The ppc boards have a 770. In the APUS tree we currently have a modified
> ncr53c8xx driver, that sort of seems to work. The biggest problem seems to
> be the incoherent memory interface.
... Ah ;-) So where do I find the APUS tree? From digging around on
the web (man, there's a lot of broken links in the APUS faq ...), it
seems to be its own sourceforge project that hasn't switched to working
on 2.6 yet, is this correct?
Now that ncr53c8xx is non-PCI only, it should cause the absolute minimum
of wailing & gnashing of teeth to convert it to use the non-coherent
dma device API. It would benefit PA-RISC too as we have two models
(735 and 755) that have NCR720 chips and a non-coherent architecture.
Right now, they use the 53c700 driver, but it'd be better to use the
ncr53c8xx driver, of course.
Are any APUS people interested in working on this?
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next parent reply other threads:[~2003-09-29 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0309291116250.7432-100000@vervain.sonytel.be>
[not found] ` <Pine.LNX.4.44.0309291434260.17812-100000@serv>
2003-09-29 13:33 ` Matthew Wilcox [this message]
2003-09-29 13:45 ` [parisc-linux] Re: NCR53c720 Geert Uytterhoeven
2003-09-29 16:24 ` Roman Zippel
2003-09-29 16:27 ` Matthew Wilcox
2003-09-29 20:55 ` Grant Grundler
2003-09-29 21:00 ` James Bottomley
2003-09-30 17:23 ` Grant Grundler
2003-09-29 21:25 ` Rene Brothuhn
2003-09-30 2:21 ` Matthew Wilcox
2003-09-30 8:21 ` Geert Uytterhoeven
2003-09-30 13:47 ` James Bottomley
2003-09-30 13:59 ` Matthew Wilcox
2003-09-30 15:32 ` James Bottomley
2003-09-30 19:03 ` Grant Grundler
2003-09-30 13:59 ` Rene Brothuhn
2003-09-30 14:32 ` Matthew Wilcox
2003-10-07 20:22 ` Rene Brothuhn
2003-09-30 14:55 ` Roman Zippel
2003-10-07 20:24 ` Rene Brothuhn
2004-05-04 7:22 Joel Soete
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=20030929133317.GP24824@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-apus-devel@lists.sourceforge.net \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=parisc-linux@parisc-linux.org \
--cc=zippel@linux-m68k.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