Perhaps then it's time to fork some stuff then. There's active development in getting ArcEm to support RISC OS better at the moment - I'm not aware of anyone who's using NetBSD putting in a lot of effort. We already have hostfs support in there which is through a module hack (excellent work by those involved). I think getting the Internet module hack in there would be good, and a lot less effort and (one assumes) slow down than trying to emulate a network card. Particularly in getting ArcEm more noticed/immediately usable.
I understand the idea of keeping it pure, but then users (at least from the mail I receive for the Mac OS X ArcEm port) want features not purity. I see nothing wrong with adding module based short cuts for RISC OS in ArcEm, these can be conditionally enabled through #defines or such if necessary. It doesn't negate doing a pure emulation of network hardware at some point, but it would seem the easier route given the limited developer resources. Perhaps there even needs to be some kind of fork - a pure version of ArcEm and a RISC OS enhanced version. I appreciate I'm a very minor contributed to the project, but having chatted with flibble and rjek about it (I'll master real life names at some point) this seems to be the obvious immedate path. -- Michael On 2/27/06, Ralph Corderoy <[EMAIL PROTECTED]> wrote: > > Hi Matthew, > > Off-list you wrote: > > I have also been experimenting with implementing networking in a > > couple of different ways: Either emulating a real network card (an > > Ether1 looks promising), or writing a RISC OS module that implements > > DCI4, and passes network packets directly to the Host. I haven't got > > very far with either of these ideas yet, as I have been working on > > other things. > > I'd prefer emulating a real network i/f podule since that would support > other OS better, e.g. NetBSD. > > http://www.netbsd.org/Ports/acorn26/ > > I think it would be nice for arcem to continue to support Linux/ARM26 > and NetBSD would be nice to add. > > However, I thought in the past that a RISC OS module presenting a DCI4 > interface may be easier and have a copy of > > DCI-4 Functional Specification > Drawing Number: 0284,036/FS > 25 Jul 2000 Issue 4 > > if that's of help. > > Cheers, > > > Ralph. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > arcem-devel mailing list > arcem-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/arcem-devel > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
