I think that scc support would be a key selling point for less technical users looking for casual gaming without the hassle of coming roms on flash cards
In the end none is going to port chrome under msx so rom transfer will be the main purpose of the network interface
I do not think that SCC is a must. I think that keeping the price as low as possible, would give the GR8NET more changes of success.
its a great hardware thing! produce it!
I do not think that SCC is a must.
As shown in the video this interface seems designed mainly to launch Roms via a network. If this is the case the SCC chip is important and also the transfer rate. It must be able to launch a maximum of Rom.
If it is an ordinary network interface, the important is of course the functions related to the network, the transfer rate, the UNAPI support and low price. The launch of many ROM type is useless.
Looked at Nestor's documents @sourceforge, understood nothing.
Why not just publish list of needed calls with defined inputs and outputs? Is there such standard list for me to implement?
These documents you should look at: Ethernet UNAPI specification, TCP/IP UNAPI specification. They describe extended BIOS calls according to the UNAPI specification (which builds on EXTBIO). I’m sure konamiman or others who’ve implemented it are willing to assist with the details if needed. UNAPI adds a lot of value to the cartridge in terms of software interoperability, so I would definitely aim to support it. Personally I care for it more than SCC support.
Here's first version is manual.
As soon it's produced I certainly want gr8net.Don't implement SCC if I want music or games with sound use some other hardware .Still want an GR8BIT
Is it compatible with the w5100 ? If so is it possible to order such device ?
if so we could use it in SymbOS as well
Here's first version is manual.
Privjet Eugeny, I watched the video and I am very impressed by this new hardware! As I am currently working on ethernet implementations as well (currently DenYoNet support in SymbOS) I am quite interested in your solution.
What I would like to know: Is the TCP/IP stack implemented on hardware or software side? In the manual it seems, that you support 2 sockets, which can be each TCP (server/client), UDP or IPRaw, is this correct?
@EdoZ: It's probably not W5100 compatible.
PS: Oh, and I would like to order 2 of them!