public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Dan Olson <dano@agora.rdrop.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: Future of ELKS
Date: Fri, 21 May 2004 06:08:33 -0300	[thread overview]
Message-ID: <40ADC711.7060605@conectiva.com.br> (raw)
In-Reply-To: <20040520224825.I3312@agora.rdrop.com>

Dan Olson wrote:

>>>	3) Include IP support. Again, it is available for hackers, and only a
>>>few interfaces are supported (slip?, ppp?), and are a bit hidden and the
>>>routes are very, very hard-coded. Ethernet support, at least for some
>>>cards (NE2000, that common 8bit 3com whose name i can not remember,...)
>>>would be really great.
>>>      
>>>
>>Is on the TODO since a while :)
>>    
>>
>
>Great, that's exactly what I'd love to see, support for a NE2000 or 3C503
>(Etherlink II, how could you forget ?:) and a few apps like telnet and
>ftp.
>
>  
>
Does anybody here considered porting uIP to ELKS? 
http://www.sics.se/~adam/uip/ I've been talking with friends about
the work I've been doing on factoring net/ code in 2.5/2.6 and how it 
could relate to 2.6-tiny (http://www.selenic.com/tiny-about/),
i.e. making it possible to disable lots of features that aren't strictly 
required to reduce the size footprint of networking
support, Matt already managed to boot linux-tiny (2.6) with as little as 
2MB of ram, more can be done and in fact several
folks are contributing patches for CONFIG_TINY with several patches 
making its way to mainline.

That, and the fact that we already have mm/nommu.c in 2.6 makes the 
future look bright for an eventual merge of ELKS into
mainline, as I discussed with Eduardo :-)

- Arnaldo


  reply	other threads:[~2004-05-21  9:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 20:55 Future of ELKS Miguel Bolanos
2004-05-20  3:39 ` I'm in Void
2004-05-20 14:47   ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15   ` Miguel Bolanos
2004-05-20 15:37     ` Eduardo Pereira Habkost
2004-05-20 16:06       ` Andrey Romanenko
2004-05-21  5:51         ` Dan Olson
2004-05-20 17:30       ` Javier Sedano
2004-05-21  8:32         ` Gábor Lénárt
2004-05-21 14:15           ` Jody
2004-05-24  9:29             ` Gábor Lénárt
2004-05-24 18:20               ` Alan Cox
2004-05-20 23:43       ` David Given
2004-05-21  1:04         ` Stefan de Konink
2004-05-21  3:39           ` Chad Page
2004-05-29 16:58             ` Gregg C Levine
2004-05-21  5:55         ` Dan Olson
2004-05-21  6:08         ` Jody
2004-05-21 13:24         ` Eduardo Pereira Habkost
2004-05-21 16:30           ` David Given
2004-05-21 16:59             ` Michael McConnell
2004-05-22 12:12               ` David Given
2004-05-22 17:29                 ` Chad Page
2004-05-21 18:38             ` Jody
2004-05-22  8:53               ` jb1
2004-05-22 17:00                 ` Chad Page
2004-05-24  9:42               ` Gábor Lénárt
2004-05-20 16:54     ` Javier Sedano
2004-05-21  5:50     ` Dan Olson
2004-05-21  9:08       ` Arnaldo Carvalho de Melo [this message]
2004-05-21 10:24         ` Alan Cox
2004-05-24 12:20         ` Gábor Lénárt
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano

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=40ADC711.7060605@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=dano@agora.rdrop.com \
    --cc=linux-8086@vger.kernel.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