From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18045 invoked by alias); 2 Sep 2008 08:10:24 -0000 Received: (qmail 18034 invoked by uid 22791); 2 Sep 2008 08:10:23 -0000 X-Spam-Check-By: sourceware.org Received: from fg-out-1718.google.com (HELO fg-out-1718.google.com) (72.14.220.158) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Sep 2008 08:09:20 +0000 Received: by fg-out-1718.google.com with SMTP id 16so1354704fgg.44 for ; Tue, 02 Sep 2008 01:09:16 -0700 (PDT) Received: by 10.86.82.6 with SMTP id f6mr5344336fgb.53.1220342956839; Tue, 02 Sep 2008 01:09:16 -0700 (PDT) Received: from localhost ( [212.41.76.200]) by mx.google.com with ESMTPS id 12sm6712471fgg.0.2008.09.02.01.09.07 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Sep 2008 01:09:09 -0700 (PDT) Date: Tue, 02 Sep 2008 08:10:00 -0000 To: "Andrew Lunn" , "Robert Brusa" Reply-To: Bob.Brusa@gmail.com Cc: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <48B8137D.7040803@mlbassoc.com> <20080829162608.GV31987@lunn.ch> <20080901093643.GT25863@lunn.ch> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <20080901093643.GT25863@lunn.ch> User-Agent: Opera Mail/9.52 (Linux) From: Robert Brusa X-IsSubscribed: yes 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: Re: [ECOS] Fwd: AT91SAM7X-EK with TC/IP - unresolved conflicts X-SW-Source: 2008-09/txt/msg00018.txt.bz2 On Mon, 01 Sep 2008 11:36:43 +0200, Andrew Lunn wrote: > > I never said that. I just said the FreeBSD stack will not work. The > lwip stack has been shown to work on the AT91SAM7X. Go google lwip. > running through ecosconfig new at91sam7xek lwip_eth etc. seems to work. But when I try to build my previously working projects, flash support is no longer available and the cor. calls produce errors (e. g. a call to flash_program) On the other hand, when attempting to configure the same thing using configtool, there are 5 conflicts the tool is not able to resolve. From a first look at the ecc-file, it seems to be a problem that somewhere a restriction for the AT91SAM7S is required. Any adice how to overcome this hurdle? >> Is RPC supported by ecos? > > RPC is too generic a word. Do you mean Suns RPC used by NFS, RFC 1057? > Do you mean XML-RPC like http://www.xmlrpc.com/. Do you mean COBRA? > > Out of the box eCos supports none of these. However you could port > something or write your own RPC code. > - I am talking about RFC 1831 (which is the successor of 1057). I have built a small example using Suns rpcgen-tool and it worked fine using two linux-PCs linked by ethernet. Now the next step would be to port the serverapp to my AT91SAM7X target. The 2nd step then would be to "expand" this little server app to handle the routines my app requires - by hand or using e. g. rpcgen-produced templates. Is this a realistic scenario? Robert -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss