Am 11. Juni 2013 07:40:29 schrieb Jim Brain <firstname.lastname@example.org>: > On 6/11/2013 12:10 AM, A. Fachat wrote: > > But, I do lament the split of development knowledge... In fact I seriously considered reusing sd2iec code. > sd2iec can be fitted to handle any block device by merely creating a new > block driver. A complete wholesale mod to send all commands to an endpoint > could also be implemented, though it would take a bit of refactoring. I > also thought sd2iec's IEEE488 support was similarly factored into its own > codebase. However, this seemed too much refactoring effort for me, esp with those calls that where in a place "as good as any". > License issues excepted, it means all of the various fastloaders, GEOS > mods, and the REL file support already in sd2iec will need to be > re-implemented in your codebase. Indeed. In fact I haven't foreseen how large XD2031 would become. But my focus is less on as much compatibility but on opening up PC resources as disk drive for the cbm and here more on the PET (my focus - can't speak for the other developers in the team). That is why you can now telnet to a tcp port with it, or LOAD a file directly from an ftp or http server. Rel file support more or less appeared because of the SuperPet's os9 requirements... That's not to say the iec bus is neglected, of course not. It fully works and is supported. Just a different focus. > I realize my position will seem biased, but it's not that. Since your code > is GPL as well, I'm free to use it, as any one is. And vice versa :-) The beauty of open source. André Message was sent through the cbm-hackers mailing listReceived on 2013-06-11 11:02:21
Archive generated by hypermail 2.2.0.