From: Christian Plessl <cplessl@ee.ethz.ch>
To: Rafael RodrÃÂguez Velilla <rrv@tid.es>,
ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Microwindows on eCos
Date: Fri, 02 Mar 2001 03:48:00 -0000 [thread overview]
Message-ID: <5.0.2.1.0.20010302123056.00a93540@imap.ee.ethz.ch> (raw)
In-Reply-To: <3A9F77B0.8EDEDE6D@tid.es>
>What is all this of microwindows?
>
> Maybe I'm interested on it. Does it allows you to use all the development
>facilities of WindowsCE? Does it works with eCos?
The name Microwindows is leading you to a wrong track. Microwindows is used
for creating a graphics subsystem i.e. providing support for device
independent graphics routines and graphic device drivers. The project comes
in 2 flavors: NanoX and Microwindows. Based on the same libraries providing
graphic primitives, NanoX provides a X-windows like API whereas
Microwindows provides a more Windowslike API.
To my knowledge there is no generic graphics device layer in eCos yet. One
can argue whether the graphics subsystem shall be part of the kernel, like
in Microsofts Windows, or not, as with Unix running X-windows, where the
X-server is just an ordinary server application providing its services to
X-clients.
Microwindows is written that way, that you need to provide a module which
implements low-level support for graphics i.e. provide a framebuffer device
driver. If you have written this driver, you should be able to compile
microwindows and link it to your ecos application.
BTW: Has anybody implemented framebuffer support for VGA cards for the i386
target? I had a quick look on this, but initialization of the VGA card is
quite cumbersome especially when running in protected mode. I could not
find any good documentation on this.
Greetings,
Chris
--
Christian Plessl <cplessl@ee.ethz.ch>
next prev parent reply other threads:[~2001-03-02 3:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 14:34 Rosimildo daSilva
2001-03-02 1:53 ` wangwei
2001-03-02 2:42 ` Rafael RodrÃguez Velilla
2001-03-02 2:57 ` Martin van Veen
2001-03-02 3:48 ` Christian Plessl [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-27 17:05 Antoine.Amirault
2003-07-17 15:59 [ECOS] MicroWindows " Chris Garry
2003-07-17 16:17 ` Bob Koninckx
2003-07-17 16:43 ` Chris Garry
2003-07-18 4:40 ` Jonathan Larmour
2003-07-18 15:51 ` Chris Garry
2003-04-06 8:05 [ECOS] Microwindows " fairy
2003-04-07 22:17 ` Jonathan Larmour
2001-04-12 14:36 宋宜叡
2001-04-13 6:55 ` Gary Thomas
2001-03-02 6:05 Rosimildo daSilva
2001-01-16 2:46 ö¼¼Ãü
2001-02-28 17:47 ` wangwei
2001-03-01 4:01 ` Robin Farine
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=5.0.2.1.0.20010302123056.00a93540@imap.ee.ethz.ch \
--to=cplessl@ee.ethz.ch \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=rrv@tid.es \
/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).