From: F. H. <fh...@at...> - 2000-09-17 14:49:06
|
This is what I get with the latest hacking on the PUP SCSI. This is forcing the driver into MMIO mode. It fails two of the three cache tests. I need to figure out why. BTW I used 5 and 7 as the swapper values because I thought the 1 and 2 might give a misleading result. They didn't... BTW Richard Hirst (spelling?) has modified the sym53c8xx driver to work with a 53c720 chip on some HP hardware. I know the 53c720 chips is a very close relative or predecessor to the 53c770 chip. The only thing is is that the interface to the driver is through a special 'zalon' chip. I may try applying his patch and see if I can get that driver to do anything. Nothing like parallel development on two drivers that don't work. :) Trying to detect PuP SCSI... ncr53c8xx: 53c770 detected ncr53c770-0: rev=0x00, base=0xf40000, io_port=0x0, irq=12 new NCB[2932] @c02f2000. Storing input new SCRIPT[3772] @c3f33000. new SCRIPTH[3708] @c3f32000. np: ID: 770 REV: 0 FEA: 15382 CLCK: 5 OF: 10 Initialize timer paddr: f40000 paddr2: 0 io_port: 0 Peparing... stuff: 10 5 192 32 1 set verbose: myaddr: 0 myaddr: 7 myaddr: 7 ncr53c770-0: ID 7, Fast-20, Parity Checking verbose:5 ncr53c770-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/c0/20/00/00/04 ncr53c770-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/82/20/00/08/24 no on-board ram scripth: c3f32000 p_scripth: bf32000 script: c3f33000 p_script: bf33000 Resetting for snoop test offset: c istat: 0 SCSI reset istat: 40 cleared istat: 0 test: aabbff11 aabbff11 offset: c virt_to_phys(np): 82f2000 np: c02f2000 ncr_cache: 00000000 pc: 0bf32e50 np->ncr_cache: 00000005 nc_dsp: 0bf32e5c offset: 00000014 offset: 00000014 CACHE TEST FAILED: host wrote 5, ncr read 0. CACHE TEST FAILED: ncr wrote 7, host read 5. CACHE INCORRECTLY CONFIGURED. ncr53c770-0: detaching... -- Fred |
From: Michel <dae...@st...> - 2000-09-17 16:58:42
|
"F. Heitkamp" schrieb: > CACHE TEST FAILED: host wrote 5, ncr read 0. > CACHE TEST FAILED: ncr wrote 7, host read 5. > CACHE INCORRECTLY CONFIGURED. This looks like the CPU only writes to and reads from cache. Maybe you should map the memory as uncacheable? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
From: Geert U. <ge...@li...> - 2000-09-17 18:01:31
|
On Sun, 17 Sep 2000, Michel [iso-8859-1] Dänzer wrote: > "F. Heitkamp" schrieb: > > CACHE TEST FAILED: host wrote 5, ncr read 0. > > CACHE TEST FAILED: ncr wrote 7, host read 5. > > CACHE INCORRECTLY CONFIGURED. > > This looks like the CPU only writes to and reads from cache. Maybe you should > map the memory as uncacheable? Or you wrote to a different place than the NCR expects, so the result in memory wasn't modified. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: F. H. <fh...@at...> - 2000-09-17 22:14:33
|
On Sun, Sep 17, 2000 at 08:01:03PM +0200, Geert Uytterhoeven wrote: > On Sun, 17 Sep 2000, Michel [iso-8859-1] Dänzer wrote: > > "F. Heitkamp" schrieb: > > > CACHE TEST FAILED: host wrote 5, ncr read 0. > > > CACHE TEST FAILED: ncr wrote 7, host read 5. > > > CACHE INCORRECTLY CONFIGURED. > > > > This looks like the CPU only writes to and reads from cache. Maybe you should > > map the memory as uncacheable? > > Or you wrote to a different place than the NCR expects, so the result in > memory wasn't modified. It is beyond me how the structure is aligned in memory. I wish I could draw a nice picture of where things should be but I don't know enough about the memory layout of the Amiga or Linux. Yes. It apears that the scratcha register which had a non zero value in it, had a zero written to it, however the value the was in the ncr_cache variable was unchanged. So the script did not access the proper location. Here is the script section: 3679 }/*-------------------------< SNOOPTEST >-------------------*/,{ 3680 /* 3681 ** Read the variable. 3682 */ 3683 SCR_COPY (4), 3684 NADDR(ncr_cache), 3685 RADDR (scratcha), 3686 /* 3687 ** Write the variable. 3688 */ 3689 SCR_COPY (4), 3690 RADDR (temp), 3691 NADDR(ncr_cache), 3692 /* 3693 ** Read back the variable. 3694 */ 3695 SCR_COPY (4), 3696 NADDR(ncr_cache), 3697 RADDR (temp), 3698 }/*-------------------------< SNOOPEND >-------------------*/,{ > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geertOlinux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- Fred |
From: Geert U. <ge...@li...> - 2000-09-18 16:05:54
|
On Sun, 17 Sep 2000, F. Heitkamp wrote: > On Sun, Sep 17, 2000 at 08:01:03PM +0200, Geert Uytterhoeven wrote: > > On Sun, 17 Sep 2000, Michel [iso-8859-1] Dänzer wrote: > > > "F. Heitkamp" schrieb: > > > > CACHE TEST FAILED: host wrote 5, ncr read 0. > > > > CACHE TEST FAILED: ncr wrote 7, host read 5. > > > > CACHE INCORRECTLY CONFIGURED. > > > > > > This looks like the CPU only writes to and reads from cache. Maybe you should > > > map the memory as uncacheable? > > > > Or you wrote to a different place than the NCR expects, so the result in > > memory wasn't modified. > > It is beyond me how the structure is aligned in memory. > I wish I could draw a nice picture of where things should > be but I don't know enough about the memory layout of > the Amiga or Linux. > > Yes. It apears that the scratcha register which had a > non zero value in it, had a zero written to it, however > the value the was in the ncr_cache variable was unchanged. > So the script did not access the proper location. Here is > the script section: Is it possible cpu_to_scr(), scr_to_cpu(), ncr_offb() and ncr_offw() are wrong? Perhaps it would help if you could find a script created by the AmigaOS driver? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |