From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14179 invoked by alias); 16 Jun 2014 02:08:58 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 12007 invoked by uid 89); 16 Jun 2014 02:08:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: gateway15.websitewelcome.com Received: from gateway15.websitewelcome.com (HELO gateway15.websitewelcome.com) (69.56.148.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 16 Jun 2014 02:08:45 +0000 Received: by gateway15.websitewelcome.com (Postfix, from userid 5007) id D368E85858DD3; Sun, 15 Jun 2014 21:08:42 -0500 (CDT) Received: from ham03.websitewelcome.com (unknown [173.192.100.229]) by gateway15.websitewelcome.com (Postfix) with ESMTP id BE14085858DAF for ; Sun, 15 Jun 2014 21:08:42 -0500 (CDT) Received: by ham03.websitewelcome.com (Postfix, from userid 666) id BC2FB9A77E2C0; Sun, 15 Jun 2014 21:08:39 -0500 (CDT) X-Spam-Flag2999: NO X-Spam-Level2999: &&& X-Spam-Status2999: "No, score=3.5 required=5.0 tests=BAYES_99 autolearn=no version=3.3.1 Received: from audi.websitewelcome.com (audi.websitewelcome.com [192.185.82.126]) by ham03.websitewelcome.com (Postfix) with ESMTP id 365719A77E295 for ; Sun, 15 Jun 2014 21:08:39 -0500 (CDT) Received: from [220.233.45.122] (port=51628 helo=xlat) by audi.websitewelcome.com with esmtpa (Exim 4.82) (envelope-from ) id 1WwMLc-0002FZ-VI; Sun, 15 Jun 2014 21:08:38 -0500 From: "Andrew Hannam" To: "'Jerzy Dyrda'" , "'eCos Discussion'" References: <5752197.rmWza1iyYx@inteldesktop.site> In-Reply-To: <5752197.rmWza1iyYx@inteldesktop.site> Date: Mon, 16 Jun 2014 02:08:00 -0000 Message-ID: <001001cf8907$e21e32c0$a65a9840$@inmarket.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-BWhitelist: no X-Exim-ID: 1WwMLc-0002FZ-VI X-Source-Sender: (xlat) [220.233.45.122]:51628 X-Source-Auth: andrewh@inmarket.com.au X-Email-Count: 2 X-Source-Cap: aW5zeXM7aXRhbGxiaXo7YXVkaS53ZWJzaXRld2VsY29tZS5jb20= Subject: [ECOS] RE: New features required on Cortex-M platform X-SW-Source: 2014-06/txt/msg00008.txt.bz2 As one of the primary developers of uGFX I have been watching the ecos mail-lists for a long time but have never implemented an ecos system yet (just due to being caught up on other projects such as uGFX). I would be happy to work with you to create a port of uGFX for ecos. As per one of your follow-up Emails relating to uGFX versus Qt: Some of the advantages of uGFX versus Qt: - uGFX is designed for small memory footprint systems (ie. embedded systems), Qt is not and therefore has a very large footprint. - uGFX works equally well on systems without a framebuffer. Qt requires a framebuffer (and the related RAM requirements) - uGFX is a full multi-threaded GUI, you can draw from any thread regardless on which thread the object was created. Qt has only limited support for multi-threaded applications. - uGFX has support for many LCD controllers and supports custom wiring connections to your micro. Qt assumes a full graphics/windows layer is already available (usually X). - uGFX includes other sub-systems like audio, toggle switch input devices, analogue dials, ROM based file system etc. Qt does not. Some disadvantages of uGFX versus Qt: - uGFX has a different API to Qt. More programmers are familiar with Qt. - uGFX has only restricted support for overlapping windows (container windows are however supported). uGFX is in short designed for embedded systems while Qt has a desktop based design. uGFX aims to provide a cross-platform way of writing embedded GUI applications. For example, most of the uGFX demos can be run on any uGFX supported operating system without changing a single line of code. This means you can prototype and debug your application on Windows or Linux and then very simply move it to your embedded board. Regards, Andrew (aka inmarket) -----Original Message----- From: Jerzy Dyrda [mailto:jerzdy@gmail.com] Sent: Saturday, 14 June 2014 1:15 AM To: eCos Discussion Subject: Fwd: New features required on Cortex-M platform Hello all, During developing some application on Cortex-M controller I realized that is missing some vital components in current version of eCos system (from my point of view) i.e : 1) HTTP server - AHTTPD doesn't support lwIP stack what causes that it's useless. I'm planing to modify it thus any kind of advises are welcome. 2) Small embedded GUI working directly on display. From my side I propose uGFX -> http://ugfx.org/ License seems to be compatible and due its nature porting on new platform shouldn't be complicated even for me :) I'm also planning to add support and again any kind of comments advices or warnings are expecting. 3) SD bus support. I know that I can use SD card in SPI mode but on some board like STM32F4DISCOVERY SD card i only available on SD bus. It's high time to add this miss part of system. Best regards, jerzy -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss