From: "Christophe Coutand" <ccoutand@stmi.com>
To: "ricky wu" <rickleaf.wu@gmail.com>,
"eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] emboslab update ecos's code to arm qemu and synthetic
Date: Fri, 08 Apr 2011 09:56:00 -0000 [thread overview]
Message-ID: <D6050C555CC56940A7AF32652283027603DABD77@mail2.STMIRV01.COM> (raw)
In-Reply-To: <BANLkTim5LN2CA6yxwYSfBG=Ra1JqpKSn1Q@mail.gmail.com>
Hi Ricky,
Thanks for the update. Are all the graphic libraries in services\gfx\*
safe to use in commercial products or are there any special licenses to
be careful about?
Christophe
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of ricky wu
Sent: 8. april 2011 10:53
To: eCos Disuss
Subject: [ECOS] emboslab update ecos's code to arm qemu and synthetic
Dear all:
We have update ecos code to MINI2440 QEMU and synthetic
http://emboslab.hg.sourceforge.net/hgweb/emboslab/ecos-emboslab/rev/9fcc
1bff0f13
1. add touch driver for MINI2440 qemu.
2. add touch driver for synthetic
3. add new graphics library flnx (FLTK for nano-x) as an ecos package
4. fix microwindows nano-x issue, now can be run on MINI2440 QEMU or
synthetic platform
5. enable microwindows MWIN function
6. add pw graphics library
7. add PNG library
8. add jpeg-6b library
9. fix mini2440 qemu lcd driver color issue
--
Ricky Wu
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2011-04-08 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 8:53 ricky wu
2011-04-08 9:56 ` Christophe Coutand [this message]
2011-04-08 10:28 ` Stanislav Meduna
2011-04-11 6:55 ` [ECOS] " ricky wu
2011-04-11 6:56 ` ricky wu
2011-04-11 13:02 ` ricky wu
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=D6050C555CC56940A7AF32652283027603DABD77@mail2.STMIRV01.COM \
--to=ccoutand@stmi.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rickleaf.wu@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).