Re: NCR53c720

[Rene B. <re...@we...>]

On 2003.09.29 15:33 Matthew Wilcox wrote:
> ... 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?
>=20
> Now that ncr53c8xx is non-PCI only, it should cause the absolute minimu=
m
> 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.
>=20
> Are any APUS people interested in working on this?

Hello!

I'm the one who getting the 53c770 driver working on APUS. The driver is=20
based on the code from the ncr53c8xx driver which I found on a 2.4.16=20
kernel (maybe it was an other kernel version, I'm not really sure=20
anymore). In newer kernels the ncr53c8xx drivers are replaced by sym53c8x=
x=20
which uses a different and more complicated architecture.
In my opinion, the best is to create a seperate 53c720/770 driver based o=
n=20
the 53c770 from APUS or ncr53c8xx. I guess the 53c770 from APUS should=20
work (with some changes) on a 720 (or similar), because the 770 was=20
designed to replace the 720. But I don't know anything about 735 and 755.
But the APUS driver is a really big "patchwork", has some problems and=20
needs a clean-up. And I haven't worked on the driver since a year due to=20
lack of time, sorry.

I still have lack of time, but if there are any questions, I will help. I=
t=20
will be nice to have a native 720/770 driver... And maybe, if someone=20
tries to port this driver to a PA, I have to go for it...


Ciao, Ren=E8