32 bit EtherH?
Andrew Daniel (376) 76 posts |
Can any of you C programmers out there say if the code here. could be used as the basis for a gpl NIC driver to replace the 26 bit one? |
Sprow (202) 1158 posts |
There are some Linux drivers which may serve as a reference starting point. You might also consider contacting Design IT to see if they’re prepared to release the sources to ROOL under, say, the BSD licence. |
Colin Ferris (399) 1814 posts |
Would the 32bit version used in the A9 work? |
Theo Markettos (89) 919 posts |
I don’t think the A9 uses the EtherH module, does it? The various ANT/Atomwide ethernet cards use an ISA bus NE2000 clone (NS8390), which (thankfully) no later hardware uses. Omega emulates it, but that’s not 32 bit. The Linux etherh.c code isn’t much use except for writing a driver from scratch. The existing module is written in C, so 32 bitting the binary version would be tedious. Unless you can get hold of Design IT’s sources, or ask them to recompile it. |
Colin Ferris (399) 1814 posts |
If the sources are not forth-comming – having a look at the module code – to see how difficult it would be to 32bit. |
Steve Revill (20) 1361 posts |
Well, you’ve got ARMalyser or SID (supplied with the DDE) available to help analyse the code and look for non-32-bit bits. |
Colin Ferris (399) 1814 posts |
My RPC uses EtherX (Assembler). |
Andrew Daniel (376) 76 posts |
I see EtherH and other NIC modules are now in CVS. Well done and thank you to all concerned. |
Wouter Rademaker (458) 197 posts |
They are for download: http://www.riscosopen.org/content/downloads/other-zipfiles ,bottom of the page. When will the replacement EtherB EPROM be available? |
Sprow (202) 1158 posts |
I think ROOL are burning the midnight oil for the London show, so hopefully in the next week and a half. |
Jess Hampshire (158) 865 posts |
Posting from a SA RPC, running slightly modified Pi distro, with softload (modified) and these modules. So far it seem to work quite happily. |
Wouter Rademaker (458) 197 posts |
I have two EtherLan 600, an old and an newer one. The newer one can be reprogrammed, but the older can’t because the program doesn’t like the flash chip, 27c020, the newer one has a 29c020. What should I do? |
Sprow (202) 1158 posts |
A 27C020 is an EPROM, so can’t be reprogrammed in field. Is it in a socket? If it is, it can be swapped for a flash device. The only problem there is the chip will start out blank so can’t be detected by the flash programmer. If you need a preprogrammed flash part, I’d need to know which EtherH model it is and its current MAC address, plus some money tokens to ship it to you. |
Wouter Rademaker (458) 197 posts |
It has a square chip in a socket, same size as on my other EtherLan 600 model AEH78E © i-cubed ltd 1994 p/n 600.000 REV.2 1 Podule8 AUNMsgs 0.06 EtherH interface statistics eh0: Interface driver : eh16 MAC address send by e-mail |
Andrew Wickham (2067) 18 posts |
Downloaded the zip-file last night and (as far as I can tell) successfully reflashed the NIC – ROMModules shows the expected version numbers. Then “FX162,187,0”. However, trying to boot 4.39 (Adjust ROMs) fails just after the toolbox-unplug stage, with an error that !Reporter tells me is in the Utility module. From experiments with unplugging individual modules in the NIC, I suspect an issue between the SharedCLibrary 5.59 and Utility 4.39 – having had issues with a recent version of the !System update that was resolved by going back to CLib 5.56. UPDATE for reference: working from a clean 4.39 !Boot, overlaying Plingsystem.zip and then adding back extras seems to have done the trick. Looking at the contents of my previous !Boot, I must have tried a RO5 soft-load and so there was a confusion of ROL and ROOL modules. I now have a “32!Boot” folder created from harddisc4.zip which becomes “!Boot” when I do want to use RO5, while the RO4.39 one become “26!Boot” – ROL+addons and ROOL should now not get confused! EtherH on the NIC is active, and all seems well; I will transfer modules as I encounter need for them, and try to keep better track of module version and relevant OS version. |