Ingo,
Generic questions first - what is the best strategy to make Zorro
boards work with platform device utilizing drivers?
Should I go and add code to amiga/platform.c to enumerate all Zorro
devices and add platform devices for those,
or revert to looking up Zorro device data in the SCSI driver probe
function? Geert?
I've seen the following output on elgar:
schmitz@elgar:~$ cat /proc/bus/zorro/devices
00 21400c00 00e90000 00010000 d1
01 0877c900 00ea0000 00010000 c1
The 21400c00 is product code I presume - what's the d1? Which of the
two is the SCSI board?
That's easy to answer:
elgar:~# lszorro -vv
00: Phase 5 Blizzard 1220/CyberStorm [Accelerator and SCSI Host Adapter]
Type: Zorro II
Address: 00e90000 (00010000 bytes)
Serial number: 00000000
Slot address: 00e9
Slot size: 0001
Thanks - I forgot about lszorro :-)
Slot address is just the top two bytes of the base address - the d1 and
c1 part of the proc output is meaningless?
If you do - what SCSI board does crest use? Can you test kernels or
possibly just modules there for me?
Crest is using the same card as Elgar, IIRC: Cyberstorm Mk1
Christian, please correct me if I'm wrong.
So we have cyberstorm, cyberstormII and blz2060 drivers to port? What is
the difference between the cyberstorm ones?
DMA setup looks fairly similar to me (blz2060 is a bit different there).
Looks to me as though we should be able to get
away with a single ESP front end driver, perhaps set the DMA functions
different based on the model?
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
