Jump to content

sgstair

Premium Members
  • Posts

    203
  • Joined

  • Last visited

Posts posted by sgstair

  1. Hello!

     

    Can you tell us anything about what the dswifi memory footprint will be like?

     

    Thanks,

    Mike

     

    Hiya, Right now the ds wifi memory footprint is just under 40k, and sgIP memory usage is also just about 40k (note though, dynamic memory is presently being used on a per-connection basis)

     

    So, I don't think it's unreasonable to say that the entire package should use around 96k of ram under normal conditions. This can be tweaked and tuned, and I'll probably drop the amount of memory a while after the first revision has been out for a while. (when I get a chance to play around with some apps and figure out just how much is actually being used.)

     

    -Stephen

  2. Eh, I tend more towards being shy - I don't really like being around people.

     

    On the other hand though, I have more than my share of projects to work on, so I don't really have time to mess around with the rest of the world anyway.

     

    -Stephen

  3. no offense but thats not really a video its just about 6 different pictures being showed for about 2 or 3 seconds each with music

     

    Oy, I do take offense because this video does provide the detail for anyone who wants to to completely pick it apart (which was the intention) - it goes through several stages yes, but you can see exactly what it's doing and to call it just 6 pictures... just means you didn't but glance at it.

     

    ...

    -Stephen

  4. Okay, Will the wifi settings be permanent?

    Er, Maybe...

    I mean how would they be stored?

    That hasn't been decided yet.

    A.ini file (not GBA Flash cart compatible unless appended)?

    Probably not a good idea

    SRAM (not for GBAMP)?

    ...Maybe..

    Or will they have to be entered in everytime?

    Well, we'll try to avoid this :D

    Could you figure out how to read them from the firmware chip?

    Yes, once we get some games that *store* them to the firmware chip.

    Reading/understanding them is a piece of cake, but predicting how Nintendo is going to store them is very difficult indeed.

    So, at least initially the settings will probably not be stored. Once the Nintendo wifi connection is released the code may be modified to use it's data, or something else entirely could be done.

    At the moment though, whether the settings are saved or not is *entirely* up to the person writing the application.

     

    -Stephen

  5. Well uh, I won't add this to the faq until I release my documentation..... but, it's complicated.

    Reeeeeally complicated...

     

    the DS Wifi is a custom hardware register set integrated onto the main DS chip with all the other hardware (video, sound, etc) - it contains some dedicated ram and a huge register map (over 100 registers) and is tied in to the interrupt system, and has serial connections to 2 chips in the RF daughterboard.

     

    Mainly what is required to use the wifi, is a whole lot of init and some basic understanding of how a few important parts of the hardware work. The ds hardware does a lot of the work for you, but it's unclear just how much it does, that will require very extensive testing to figure out and I haven't managed to get through anywhere near all the possibilities yet. At the core of what I consider to be the "important" parts of wifi is a hardware FIFO/circular buffer in the attached memory chunk, the hardware system of sending data(register and interrupt based), and the hardware interfaces to the two external chips.

     

    well, now you're going to ask for more information, but that'd take much longer to explain, so it's best just to wait for my documentation which I promise is comprehensive about the topics I know about, specificly the ones that are important. At the rate I'm presently going, it shouldn't be long, either.

     

    -Stephen

  6. I think you misunderstand the problem :)

    Basicly all nintendo code uses the same wifi code to talk to the hardware, In this case we'd actually be looking for an entirely different feature in a completely different part of the code. It's not going to be practical to reverse engineer nintendo's TCP/IP stack when we have one of our own ;)

     

    -Stephen

  7. It is a nightmare, but it is doable - it's very similar to the kind of work I've been doing to figure out the hardware in the first place (albeit probably easier)

     

    -Stephen

  8. Nah, there never was an overall completion....

     

    Plus I don't think of things in terms of being "complete overall" - my projects never get done, I just choose to stop them at a reasonable level :P

     

    I'm documenting the completion on the current feature set I'm working on, which I think is a reasonable approach, because the feature set required will change from time to time.

     

    -Stephen

  9. The only real disadvantage to using a router is if you don't know how to set it up, it'll be less secure... It of course won't be as easy as the usb stick, but it's also has other advantages.

     

    Whatever, it's your money - pay a little more or learn a little more :)

     

    -Stephen

×
×
  • Create New...