From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23861 invoked by alias); 14 Oct 2009 08:30:38 -0000 Received: (qmail 23851 invoked by uid 22791); 14 Oct 2009 08:30:37 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-px0-f202.google.com (HELO mail-px0-f202.google.com) (209.85.216.202) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Oct 2009 08:30:32 +0000 Received: by pxi40 with SMTP id 40so1155406pxi.24 for ; Wed, 14 Oct 2009 01:30:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.153.29 with SMTP id f29mr659077wfo.294.1255509030661; Wed, 14 Oct 2009 01:30:30 -0700 (PDT) In-Reply-To: <4AD57670.9020705@siva.com.mk> References: <4AD57670.9020705@siva.com.mk> Date: Wed, 14 Oct 2009 08:30:00 -0000 Message-ID: From: Mandeep Sandhu To: Ilija Stanislevik Cc: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 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] Ethernet on top of SPI X-SW-Source: 2009-10/txt/msg00083.txt.bz2 On Wed, Oct 14, 2009 at 12:27 PM, Ilija Stanislevik wrote: > Hi, > > We are developing hardware based on STM32. For Ethernet we use > Microchip's ENC424J600, connected on one of the STM32's SPI buses. > > Our intention is to develop an Ethernet driver for ENC424J600 on top of > the SPI driver. We also intend to make this Ethernet-over-SPI general > regarding SPI hardware, but it seems that there are some obstacles there. We have a similar requirement, where we are going to connect a wireless ethernet controller, over SPI, to the AT91SAM7X SoC. Do you have plans to conribute back your ethernet-over-SPI driver? Regards, -mandeep > > The polarity and phase of STM32's SPI should be adjusted to the > requirements of ENC424J600. In the SPI's API there is no get/set-config > support for this. The configtool has no provision to set this either. > The only way to adjust this is to poke the driver's private data > structure. This means that our Ethernet driver must be written > specifically for STM32's SPI. > > Also, I have found no provision to refer SPI driver by device name, > another reason to stick the Ethernet driver to specific SPI hardware. > > Am I right with above conclusions? Of course, if there is no other > solution, we will live with an Ethernet driver married to our SPI hardware. > > Anyway, are there any rules/directions on SPI's API regarding hardware > independence? > > Thank you, > > Ilija Stanislevik > > SIvA doo > ul. Zejnel Ajdini 5 > MK-1060 Skopje > Macedonia > > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss