From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4574 invoked by alias); 30 Apr 2007 11:08:11 -0000 Received: (qmail 4564 invoked by uid 22791); 30 Apr 2007 11:08:10 -0000 X-Spam-Check-By: sourceware.org Received: from anchor-post-35.mail.demon.net (HELO anchor-post-35.mail.demon.net) (194.217.242.85) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Apr 2007 12:08:08 +0100 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-35.mail.demon.net with esmtp (Exim 4.42) id 1HiTjO-000DDp-GO; Mon, 30 Apr 2007 11:07:51 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id C39001386AA; Mon, 30 Apr 2007 12:07:20 +0100 (BST) To: manesh , ecos-discuss@ecos.sourceware.org References: <1177582674.805294.203270@s33g2000prh.googlegroups.com> <20070426133443.GA22158@lunn.ch> <1177738903.263455.239890@l77g2000hsb.googlegroups.com> <1177753990.919543.45310@y80g2000hsf.googlegroups.com> <1177926816.728845.292060@c35g2000hsg.googlegroups.com> <1177930381.251419.318920@y5g2000hsa.googlegroups.com> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Mon, 30 Apr 2007 11:08:00 -0000 In-Reply-To: <1177930381.251419.318920@y5g2000hsa.googlegroups.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: Fwd: Sending raw packets on eCos X-SW-Source: 2007-04/txt/msg00165.txt.bz2 Please keep the discussion on the message board. manesh 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