On 12/27/2012 03:04 PM, Ingo Jürgensmann wrote:
Am 11.11.2012 um 10:23 schrieb Geert Uytterhoeven :
On Sun, Nov 11, 2012 at 4:45 AM, schmitz
wrote:
Geert - is enumerating the entire Zorro devices list still the correct way
to probe for devices? Are device probes initiated by the zorro driver
Am 11.11.2012 um 10:23 schrieb Geert Uytterhoeven :
> On Sun, Nov 11, 2012 at 4:45 AM, schmitz
> wrote:
>> Geert - is enumerating the entire Zorro devices list still the correct way
>> to probe for devices? Are device probes initiated by the zorro driver code,
>> or do I need to declare a platfor
Am 15.11.2012 um 04:48 schrieb schmitz :
> Christian T. Steigies wrote:
>> Is it running stable? I think I had upgraded one of crest/kullervo already
>> but the machine was becoming unresponsive after some hours/days. Not
>> something to return to NMMN.
> Unresponsive with regards to network, or
On Mon, 19 Nov 2012, schmitz wrote:
> No length field - must have relied on the ESP interrupt to terminate the
> transfer.
I think that for PIO, it doesn't matter. On the other hand, if there is a
DMA controller on the board, a schematic would probably answer your
question, and PIO doesn't ma
Hi!
Yesterday I googled a little bit about Amiga and DMA. There are some
docs from the Hardware Reference Manual that have details about DMA
transfer within the chipset and everyone mentioned the length of the
transfer. Even some caveats were listed, for example that the last 3
bits of every
Finn,
I've seen that - the old Amiga drivers only set the DMA start address
but no transfer length, no idea whether that will work for command data.
As far as the low level driver dma routines are concerned, they only get
called by the ESP core and they are always passed a transfer length
On Sun, 18 Nov 2012, schmitz wrote:
> I've seen that - the old Amiga drivers only set the DMA start address
> but no transfer length, no idea whether that will work for command data.
As far as the low level driver dma routines are concerned, they only get
called by the ESP core and they are al
Finn,
On Thu, 15 Nov 2012, schmitz wrote:
It should be reasonably easy if the new core ESP driver can be convinced
to send SCSI command data by programmed I/O (the old drivers set that
flag, but it has disappeared from the new core).
The Mac ESP driver has been ported successfully though
On Thu, 15 Nov 2012, schmitz wrote:
> It should be reasonably easy if the new core ESP driver can be convinced
> to send SCSI command data by programmed I/O (the old drivers set that
> flag, but it has disappeared from the new core).
>
>
> The Mac ESP driver has been ported successfully though
On Sun, Nov 18, 2012 at 09:14:16AM +1300, schmitz wrote:
> On that note - can you test another iteration of the EtherNAT USB
> driver for me? The interrupt enable/disable muste have been broken
> in the last tests we ran.
>
> Not that it makes much of a difference on my hardware, but I suspect
> t
Christian,
On Sun, Nov 11, 2012 at 05:48:45PM +1300, schmitz wrote:
Ingo,
Someone has to provide the patches in the first place. I remember
looking into what would be required to port the CS driver(s) to
the ESP core driver and it did not appear to be terribly
complicated. That project
Christian T. Steigies wrote:
Seems I misremembered - that was for the Blizzard 2060 driver (one
of Christian's Amigas has such a card). The two should be similar
enough to restart from there.
Yes, please, I think thats what stopped me from upgrading aahz (A2k).
I still have a mail from la
Christian T. Steigies wrote:
Is it running stable? I think I had upgraded one of crest/kullervo already
but the machine was becoming unresponsive after some hours/days. Not
something to return to NMMN.
Unresponsive with regards to network, or totally dead?
Network might suffer from IRQ watch
On 2012-11-12 10:49, Christian T. Steigies wrote:
Kullervo should work without any problems as it's an A3000 and
Arrakis is the same, which runs happily on 3.2.0-3-amiga.
Is it running stable? I think I had upgraded one of crest/kullervo
already
but the machine was becoming unresponsive after s
On Sun, Nov 11, 2012 at 12:18:14PM +0100, Ingo J?rgensmann wrote:
> On 2012-11-11 11:57, Christian T. Steigies wrote:
>
> >But I also have crest and kullervo (A3k and A4k) with SCSI
> >drivers, that
> >probably do not work anymore in current kernels.
>
> Kullervo should work without any problems
On 2012-11-11 11:57, Christian T. Steigies wrote:
But I also have crest and kullervo (A3k and A4k) with SCSI drivers,
that
probably do not work anymore in current kernels.
Kullervo should work without any problems as it's an A3000 and Arrakis
is the same, which runs happily on 3.2.0-3-amiga.
On Sun, Nov 11, 2012 at 05:48:45PM +1300, schmitz wrote:
> Ingo,
> >Someone has to provide the patches in the first place. I remember
> >looking into what would be required to port the CS driver(s) to
> >the ESP core driver and it did not appear to be terribly
> >complicated. That project got shelv
Hi Michael,
On Sun, Nov 11, 2012 at 4:45 AM, schmitz
wrote:
> Geert - is enumerating the entire Zorro devices list still the correct way
> to probe for devices? Are device probes initiated by the zorro driver code,
> or do I need to declare a platform device?
The old Amiga NCR53C9x drivers still
On 2012-11-11 04:45, schmitz wrote:
Good - my ssh connects to elgar work fine. I'll have to get a new ssh
key installed by you it seems.
Just send it to me...
BTW, as a completely unrelated side note: I discovered that new
flatscreen TV boxes make up a good replacement for old Amiga 50 Hz/15
Ingo,
Someone has to provide the patches in the first place. I remember
looking into what would be required to port the CS driver(s) to the
ESP core driver and it did not appear to be terribly complicated. That
project got shelved when RL got a bit too busy, though.
Seems I misremembered - that
Ingo,
Someone has to provide the patches in the first place. I remember
looking into what would be required to port the CS driver(s) to the
ESP core driver and it did not appear to be terribly complicated. That
project got shelved when RL got a bit too busy, though.
Same here. Otherwise I would
On 2012-11-10 05:10, schmitz wrote:
What I might can do to help here: upgrading the box to unstable,
compiling test kernel, applying patches and see if it works...
Someone has to provide the patches in the first place. I remember
looking into what would be required to port the CS driver(s) to t
Ingo,
On 2012-11-09 07:19, Geert Uytterhoeven wrote:
[SCSI] remove m68k NCR53C9x based drivers
The CyberStorm/CyberStorm II/Blizzard 1230/2060/Fastlane/Oktagon SCSI
drivers should be resurrected using the newer esp_scsi core, like was
already done for Mac ESP and Sun3x SCSI.
What I might
On 2012-11-09 07:19, Geert Uytterhoeven wrote:
[SCSI] remove m68k NCR53C9x based drivers
The CyberStorm/CyberStorm II/Blizzard 1230/2060/Fastlane/Oktagon SCSI
drivers should be resurrected using the newer esp_scsi core, like was
already done for Mac ESP and Sun3x SCSI.
What I might can do
On Thu, Nov 8, 2012 at 7:07 PM, Ingo Jürgensmann
wrote:
> I finally found some spare time to upgrade elgar to unstable. Problem is: the
> machine is a Amiga 4000 with an Cyberstorm Mk 1 with SCSI module.
> Unfortunately there seems no support in recent kernel for this kind of SCSI
> card.
Yep
Ingo J�rgensmann dixit:
>Side note: basically the same problem popped up in 2008:
><20080625082429.gq5...@2004.bluespice.org> ;-)
Without the code and the kconfig option, there’s nothing
_I_ can do, sorry. But since the kernel guys are probably
reading here… maybe you get lucky.
bye,
//mirabilos
Hi!
In August I picked up the autobuilder elgar from NMMN in Hamburg in order to
upgrade it and make it available again as an autobuilder.
I finally found some spare time to upgrade elgar to unstable. Problem is: the
machine is a Amiga 4000 with an Cyberstorm Mk 1 with SCSI module. Unfortunate
27 matches
Mail list logo
