public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Stanislevik <ilijas@siva.com.mk>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Ethernet on top of SPI
Date: Wed, 14 Oct 2009 06:58:00 -0000	[thread overview]
Message-ID: <4AD57670.9020705@siva.com.mk> (raw)

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.

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

             reply	other threads:[~2009-10-14  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  6:58 Ilija Stanislevik [this message]
2009-10-14  8:30 ` Mandeep Sandhu
2009-10-14 16:52   ` Ilija Stanislevik
2009-10-14 10:01 ` Bart Veer
2009-10-14 16:57   ` Ilija Stanislevik
2009-10-14 11:10 ` Chris Holgate
2009-10-14 16:57   ` Ilija Stanislevik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD57670.9020705@siva.com.mk \
    --to=ilijas@siva.com.mk \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).