linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen Pelc" <stephen@mpeltd.demon.co.uk>
To: Lada 'Ray' Lostak <ray@unreal64.net>
Cc: linux-assembly <linux-assembly@vger.kernel.org>
Subject: Re: Embeded
Date: Wed, 10 Aug 2005 16:49:10 +0100	[thread overview]
Message-ID: <42FA3006.30267.1AB80614@localhost> (raw)
In-Reply-To: <42F9F031.9050105@unreal64.net>

> Thank you, I didn't know Philips do uC too :) I know Atmel one's
> and they seems prety OK. What TCP/IP stack you are using ? There
> exists sever GPL'ed, but I have no experimence with them.
> 
> The only reason why I wanted to run linux is to use their eth
> drivers & tcp/ip stack. Nothing more.

We use our own, see
  www.mpeforth.com/powernet.htm

If you are using external Ethernet chips such as the SMSC 91Cxxx 
series, RealTek 8019AS (and other NE2000 clones) or Asix 88976, 
the drivers are pretty simple and there are plenty of code 
examples on the net. Once you know what you are doing, about 200 
lines of code.

The Ethernet controllers integrated into most CPUs tend to 
consist of a MAC unit with small buffers and a DMA engine. You 
have to manage it all yourself. They can require 1000+ lines of 
code.

What to do depends on the hardware volume and how much time you 
have.

Stephen

--
Stephen Pelc, stephen@mpeltd.demon.co.uk
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 23 80 631441, fax: +44 23 80 339691
web: http://www.mpeltd.demon.co.uk - free VFX Forth downloads

      reply	other threads:[~2005-08-10 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10  5:59 Embeded Lada 'Ray' Lostak
2005-08-10  9:34 ` Embeded Stephen Pelc
2005-08-10 12:16   ` Embeded Lada 'Ray' Lostak
2005-08-10 15:49     ` Stephen Pelc [this message]

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=42FA3006.30267.1AB80614@localhost \
    --to=stephen@mpeltd.demon.co.uk \
    --cc=linux-assembly@vger.kernel.org \
    --cc=ray@unreal64.net \
    /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 NNTP newsgroup(s).