Re: Uthernet programming question

[ol.sc@web.de (Oliver Schmidt)]

Hi,

>Right, I understand that the sky is the limit when you can do bare-
>metal programming on the Uthernet side.  However, under the control of
>a mammoth OS like OSX, Windows or Linux, what sort of constraints is
>one likely to run in to?  I remember that the Nintendo DS implemented
>some sort of proprietary MAC-based communication method, but in order
>to talk to the DS from a PC you had to have a specific wireless card
>and replace the driver, etc.  Is it possible to do bare-metal
>programming like this without having to go as far as writing drivers
>in a PC world?

Still I don't know why you would want to do that - as I already
pointed out in my first posting of this thread. Anything "below" UDP
will cause major pain. However if you want to know - check out...

For *UX:
http://contiki.cvs.sourceforge.net/viewvc/*checkout*/contiki/contiki-2.x/cpu/native/net/tapdev.c

For Win32:
http://contiki.cvs.sourceforge.net/viewvc/*checkout*/contiki/contiki-2.x/cpu/native/net/wpcap.c

They show the "standard techniques" for "MAC-based communication" (as
you called it).

These techniques are used in emulators / virtual machines etc.

Best, Oliver