|
From: Michel <mic...@ii...> - 2001-10-07 23:46:07
|
On Sun, 2001-10-07 at 21:08, Rene Brothuhn wrote: > I`m working on the UW-SCSI driver and I`ll give you some information=20 > about it`s state. The 53c770 chip is detected and configured by the=20 > driver and then the driver makes some tests, which works fine. The 4k=20 > on-chip RAM is used for SCSI-SCRIPTS and the chip can execute SCRIPTS at=20 > on-chip RAM and also at system-memory. The LED is working, which is=20 > switched on and off by SCRIPTS in on-chip RAM when the scsi-bus is=20 > selected or reselected. Also the driver is reacting on IRQ`s and calls=20 > by the generic SCSI driver. After booting, you can find some information=20 > about the driver in /proc/scsi/53c770. Wow, this sounds very promising, keep up the good work! > And there is the problem, the generic driver tries to detect devices on=20 > the scsi-bus and fails. I don`t know whats wrong here, maybe its another=20 > cache related problem. Or endianness? Just to cover the usual suspects. :) > But by the way, I also thinking about to buy a G-Rex board and if I have=20 > the time and money I will try to get it running on APUS. But there are 2=20 > problems. First we probably need some information how we can scan the=20 > G-Rex PCI-bus (maybe from Mr. Dellert). As the other Rene mentioned in his post, it might only be a matter of knowing the addresses of PCI config and memory space. But of course vendor supplied information would always be appreciated. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |