From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31798 invoked by alias); 9 Jun 2014 01:20:12 -0000 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 Received: (qmail 31785 invoked by uid 89); 9 Jun 2014 01:20:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL autolearn=no version=3.3.2 X-HELO: nm1-vm8.access.bullet.mail.bf1.yahoo.com Received: from nm1-vm8.access.bullet.mail.bf1.yahoo.com (HELO nm1-vm8.access.bullet.mail.bf1.yahoo.com) (216.109.114.79) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 09 Jun 2014 01:20:08 +0000 Received: from [66.196.81.163] by nm1.access.bullet.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 01:20:06 -0000 Received: from [98.138.226.242] by tm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 01:20:06 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.ne1.yahoo.com with NNFMP; 09 Jun 2014 01:20:05 -0000 X-Yahoo-SMTP: DAVHEHCswBBSt52LEL26uXq8GY.pd.0s2WK3iX0- X-Rocket-Received: from T23a.STS (lgm0@71.107.71.100 with plain [98.138.84.31]) by smtp113.sbc.mail.ne1.yahoo.com with SMTP; 09 Jun 2014 01:20:05 +0000 UTC Message-ID: <53950AE0.3000400@verizon.net> Date: Mon, 09 Jun 2014 01:20:00 -0000 From: Les Miklosy User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [ECOS] Opencores Ethernet with Phy X-SW-Source: 2014-06/txt/msg00000.txt.bz2 I wish to assemble an Ethernet driver based on the opencores module for low level functionality with phy support and the standalone layer for io. Looking at the ecos database (ecos-3.0) it appears only the Arm, Rattler/fcc and Moab/ppc405 PowerPC have used phy support. At the same time no other hardware family use unmodified opencores drivers (granted interfaces are similar for stop, start, can_send, send). Why have opencores drivers been so unpopular among other processor families in that regard? Why is the phy module used so seldom? Are there further issues with the choice of io layer I should know about? I chose standalone for the complement with Redboot rather than for an ECOS application. Thanks for any guidance. -Les -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss