From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26973 invoked by alias); 16 Jun 2014 11:02:43 -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 26956 invoked by uid 89); 16 Jun 2014 11:02:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wg0-f47.google.com Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 16 Jun 2014 11:02:39 +0000 Received: by mail-wg0-f47.google.com with SMTP id k14so5319469wgh.18 for ; Mon, 16 Jun 2014 04:02:36 -0700 (PDT) X-Received: by 10.180.228.39 with SMTP id sf7mr26276809wic.26.1402916556366; Mon, 16 Jun 2014 04:02:36 -0700 (PDT) Received: from smtp.gmail.com ([217.153.153.214]) by mx.google.com with ESMTPSA id e6sm33254530eem.44.2014.06.16.04.02.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Jun 2014 04:02:35 -0700 (PDT) From: Jerzy Dyrda To: Andrew Hannam Cc: ecos-discuss@ecos.sourceware.org, Ilija Kocho =?utf-8?B?W9CY0LvQuNGY0LAg0JrQvtGH0L5d?= Date: Mon, 16 Jun 2014 11:02:00 -0000 Message-ID: <2178604.bjHe4ojyF8@inteldesktop.site> User-Agent: KMail/4.10.5 (Linux/3.7.10-1.32-desktop; KDE/4.10.5; x86_64; ; ) In-Reply-To: <001001cf8907$e21e32c0$a65a9840$@inmarket.com.au> References: <5752197.rmWza1iyYx@inteldesktop.site> <001001cf8907$e21e32c0$a65a9840$@inmarket.com.au> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-IsSubscribed: yes Subject: Re: [ECOS] RE: New features required on Cortex-M platform X-SW-Source: 2014-06/txt/msg00010.txt.bz2 Hello Andrew, On Monday 16 of June 2014 12:08:24 Andrew Hannam wrote: > 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). > > > 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. Exactly. First time when I meet wit uGFX my thought was this is what I want to have in eCos - small deeply embedded GUI. > I would be happy to work with you to create a port of uGFX for ecos. It will be a honor for me but please look at topic regarding uGFX license: 1) https://sourceware.org/ml/ecos-devel/2014-06/msg00001.html > > License seems to be compatible and due its nature porting on new platform > > I'm afraid it's not compatible with eCos licence. IMO it doesn't even > comply with Open Source Definition http://opensource.org/definition 2) https://sourceware.org/ml/ecos-devel/2014-06/msg00002.html > The licence disallows commercial use. Most of eCos use is commercial, > eCos being a part of products that usually include some intellectual > property, often other than just software. > > You can link uGFX with eCos, but we can't let uGFX in main eCos tree. To be port to eCos could be accepted by eCos maintainers it have to be clarified licenses compatibility. Best regards, jerzy > -----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 : [snip] > 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. [snip] -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss