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 have finished upgrading Elgar back in August already... ;)
Good thing you found time now :-)
What you will need in any case is a bootable and networked system on the IDE disk. Another thing that might be useful is the 2.6 kernel - do you still have source for that one? The old driver might report useful information about how the ESP is configured if we add a bit of verbosity to it.I'm right now running Elgar on 3.2.0-3-amiga on IDE and the apt-get dist-upgrade is on its way. So, in a few days (or more likely end of November/begin of December) Elgar will be available on the net.
Good - my ssh connects to elgar work fine. I'll have to get a new ssh key installed by you it seems.
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 kHz monitor. That'll make it easier for NMMN when machines will be moved back to their datacenter. No more CRT monitors. :)I would have thought the flat panels are more picky with their timing ranges - nice to know that.
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?
Cheers, Michael