Please keep the discussion on the message board.
manesh <[EMAIL PROTECTED]> writes: > > The host's IP address should be allocated either statically, or via > > DHCP. In the former case it is fixed for the network, in the latter > > the DHCP thread will keep it alive. I don't see any need to continue > > to probe for it with ARP requests. > > > > > Can I use any functions of the built in support? > > > > I don't think so, > > Thank you for the info..... I'm still interested to know what you are trying to achieve here. > So I believe the frames should be sent as raw ethernet > frames...All the handling should be done in the application. > As I ran through the archives there were some > suggestions to use eth_drive_write() and eth_drive_read() found in > eth_drv.c. I think these are internal functions used by eCos, which > cannot be used in our application. > Please if you can mention the names of the API's for > raw ethernet I/O it would be very helpful.. You have already named them above. Those are the only APIs available. However, they are closely linked in to the BSD stack and it will be hard to use them from application level. -- Nick Garnett eCos Kernel Architect eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
