From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9348 invoked by alias); 8 Aug 2009 07:10:31 -0000 Received: (qmail 9338 invoked by uid 22791); 8 Aug 2009 07:10:30 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-gx0-f222.google.com (HELO mail-gx0-f222.google.com) (209.85.217.222) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 08 Aug 2009 07:10:23 +0000 Received: by gxk22 with SMTP id 22so3269811gxk.0 for ; Sat, 08 Aug 2009 00:10:21 -0700 (PDT) Received: by 10.90.116.15 with SMTP id o15mr1689787agc.67.1249715421078; Sat, 08 Aug 2009 00:10:21 -0700 (PDT) Received: from smtp.gmail.com ([72.14.241.8]) by mx.google.com with ESMTPS id 10sm1622134agd.73.2009.08.08.00.10.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 08 Aug 2009 00:10:20 -0700 (PDT) Date: Sat, 08 Aug 2009 07:10:00 -0000 From: Sergei Gavrikov To: Uwe Kindler Cc: ecos-devel@sourceware.org Subject: Re: Just enough OS for eCos Message-ID: <20090808071018.GA8926@ubuntu.local> References: <4A7D19C3.3020504@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A7D19C3.3020504@web.de> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-08/txt/msg00011.txt.bz2 Uwe Kindler wrote: > Hello Sergei, Hello Uwe, > That is really a good idea. If I could put some things on the wish list > that I would like to see in such an image ;O) Just quick thoughts before I run away. It's time for gardering, I leaved a message on twitter (`sgavrikov', it's me). Why I tell about ubuntu-vm-builder. Using it, it's possible to stand up core JeCos VM machine and then (the builder lets us do it) to run any post install scripts (no login yet, no vmplayer yet!). So, all can be maintained as a few bash scripts. No bloat images. Because, I have not place to maintain bloat MB images, thus, bitbucket (I use it) lets me to use uploads until 150M. > 1. Precompiled toolchains for all architectures (or special JeCos for > each architecture?) It can be discussed. I would start with minimal toolset for i386-elf and even (I think) I would found a place for the first image under 50M. > 2. The eCos Config GUI tool > I know that a lot of people use the command line tools. But especially > for eCos beginners that download the VM image for eCos evaluation the > GUI tool is easier to understand, to use and it helps to understand the > eCos configuration system. And I know that there are also experienced > eCos users (like me) that prefer the GUI tool. Well, Lets call it Just eCos GUI OS image. Hm, X-server... Well, it's possible for me stand up differ kinds of JeCos using the scripts around the builder. > 3. A working docbook installation. > I did not even try to build the eCos dosumentation on a Windows machine > and always switched to a Unbuntu VM to do this job. JeCos DocBook :-) > 4. A GUI debugger > I have to admit, I'm not a command line guru and I prefer GUI tools. I > think if somone is familar with all the command line tools then he also > has a running eCos linux environment. So it would be great to have a GUI > debugger. I prefer Eclipse with Zylin CDT plugin. JeCos Eclipse. > 6. A working synthetic target to play with eCos without real hardware This is exactly what I thought about (with DHCPD, tap interfaces, may be eCos synthetic serial ports, I use that brilliant from Savin Zlobec). > If you need some help testing stuff on a Windows XP machine I could help. Thank you Uwe, I promise that first image I give you for a testing ;-) Regards, Sergei > Regards, Uwe >