From: Lada 'Ray' Lostak <ray@unreal64.net>
To: Stephen Pelc <stephen@mpeltd.demon.co.uk>
Cc: linux-assembly <linux-assembly@vger.kernel.org>
Subject: Re: Embeded
Date: Wed, 10 Aug 2005 14:16:49 +0200 [thread overview]
Message-ID: <42F9F031.9050105@unreal64.net> (raw)
In-Reply-To: <42F9D825.24163.1960BE71@localhost>
> Have a look at Philips LP2138/48 or Atmel AT91SAM7S256. These
> are 60 or 30 MHz ARM cores with up 512k Flash and 32k RAM.
> Forget about Linux and do the O/S yourself. Then it will fit. We
> run a multi-threaded web server on a Philips LPC2106 with 1288k
> Flash and 64k RAM and an external Ethernet chip.
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.
R.
next prev parent reply other threads:[~2005-08-10 12:16 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 ` Lada 'Ray' Lostak [this message]
2005-08-10 15:49 ` Embeded Stephen Pelc
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=42F9F031.9050105@unreal64.net \
--to=ray@unreal64.net \
--cc=linux-assembly@vger.kernel.org \
--cc=stephen@mpeltd.demon.co.uk \
/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).