From: Michael Schmitz <schmitzmic@gmail.com>
To: "Ingo Jürgensmann" <ij@2012.bluespice.org>
Cc: Thorsten Glaser <tg@mirbsd.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Wouter Verhelst <w@uter.be>,
linux-m68k@vger.kernel.org
Subject: Re: [PATCH 00/11] Atari Ethernet/USB patch series - for upstream and debian-kernel
Date: Sat, 30 Mar 2013 14:37:29 +1300 [thread overview]
Message-ID: <515641D9.5090503@gmail.com> (raw)
In-Reply-To: <670fbbcf44fecccc2e7c66ebfcdb4d19@muaddib.hro.localnet>
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
next prev parent reply other threads:[~2013-03-30 1:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 6:37 [PATCH 00/11] Atari Ethernet/USB patch series - for upstream and debian-kernel Michael Schmitz
2013-03-25 6:37 ` [PATCH 01/11] m68k/atari: ROM port ISA adapter support Michael Schmitz
2013-03-25 6:37 ` [PATCH 02/11] m68k/irq: Add handle_polled_irq() for timer based soft interrupts Michael Schmitz
2013-03-25 6:37 ` [PATCH 03/11] m68k/atari: use dedicated irq_chip for timer D interrupts Michael Schmitz
2013-03-25 6:37 ` [PATCH 04/11] m68k/atari: EtherNAT - platform device and IRQ support code Michael Schmitz
2013-03-25 6:37 ` [PATCH 05/11] m68k/atari: EtherNEC - add platform device support Michael Schmitz
2013-03-25 6:37 ` [PATCH 06/11] m68k/atari: EtherNAT - ethernet support - new driver (smc91x) Michael Schmitz
2013-03-25 6:37 ` [PATCH 07/11] m68k/atari: EtherNEC - ethernet support - new driver (ne.c) Michael Schmitz
2013-03-25 6:37 ` [PATCH 08/11] m68k/atari: EtherNAT - add interrupt chip definition for CPLD interrupts Michael Schmitz
2013-03-25 6:37 ` [PATCH 09/11] m68k: Implement ndelay() based on the existing udelay() logic Michael Schmitz
2013-03-25 6:37 ` [PATCH 10/11] m68k/atari: USB - add platform devices for EtherNAT/NetUSBee ISP1160 HCD Michael Schmitz
2013-03-25 6:37 ` [PATCH 11/11] m68k/atari: USB - add ISP1160 USB host controller support Michael Schmitz
2013-03-25 17:53 ` [PATCH 00/11] Atari Ethernet/USB patch series - for upstream and debian-kernel Thorsten Glaser
2013-03-25 21:25 ` Michael Schmitz
2013-03-26 8:12 ` Wouter Verhelst
2013-03-27 7:02 ` Michael Schmitz
2013-03-27 8:19 ` Geert Uytterhoeven
2013-03-28 22:40 ` Michael Schmitz
2013-03-27 8:57 ` Ingo Jürgensmann
2013-03-28 4:53 ` Michael Schmitz
2013-03-28 21:17 ` Christian T. Steigies
2013-03-28 22:36 ` Michael Schmitz
2013-03-28 23:10 ` Christian T. Steigies
2013-03-29 1:09 ` Michael Schmitz
2013-03-29 8:22 ` Christian T. Steigies
2013-03-29 7:56 ` Geert Uytterhoeven
2013-03-29 8:06 ` Christian T. Steigies
2013-03-29 8:30 ` Geert Uytterhoeven
2013-03-29 18:46 ` Michael Schmitz
2013-03-29 19:33 ` Christian T. Steigies
2013-03-29 21:38 ` Thorsten Glaser
2013-03-29 22:47 ` Christian T. Steigies
2013-03-29 23:24 ` Michael Schmitz
2013-03-30 0:00 ` Ingo Jürgensmann
2013-03-30 0:11 ` Ingo Jürgensmann
2013-03-30 1:37 ` Michael Schmitz [this message]
2013-03-30 9:34 ` Ingo Jürgensmann
2013-03-30 10:23 ` Geert Uytterhoeven
2013-03-30 7:23 ` Wouter Verhelst
2013-03-30 9:23 ` Christian T. Steigies
2013-03-30 8:14 ` Andreas Schwab
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=515641D9.5090503@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=ij@2012.bluespice.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
--cc=w@uter.be \
/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