This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: MicroWindows, network stack, framebuffer API
- From: "Gábor Török" <tgabor84 at gmail dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org, neundorf at kde dot org
- Date: Wed, 5 Nov 2008 04:59:41 -0800
- Subject: Re: [ECOS] Re: MicroWindows, network stack, framebuffer API
- References: <30c102240810250643w4688bfdbrf5c9970442b0c1c2@mail.gmail.com> <pnhc6xkky1.fsf@delenn.bartv.net> <30c102240810280508l946a0ecj85e7c97180ec6a4c@mail.gmail.com> <200811042318.03085.neundorf@kde.org>
Hi!
On Tue, Nov 4, 2008 at 2:18 PM, Alexander Neundorf <neundorf@kde.org> wrote:
>
> Two years ago or so I was working on this already, you can find the results
> here:
> http://www.ecosforge.net/pmwiki/index.php/Projects/EcosMicrowindows
Thanks for the information, I will have a look at it soon. Do you work
on it now, or have you finished working on it?
I wiil register on eCosForge and I can help developing it.
> I didn't manage to rip the network requirements out of the X API yet, so this
> still needs to be done.
> A socket is used for communication with the X server thread, it should be
> possible to replace this with eCos thread synchronization primitives.
I saw some code fragments in a NanoX source, that linked in the server
functions directly. I don't remember, it may have been the MW API not
NanoX, but I will have a look at it.
>
> Most of my changes are also in the main Microwindows cvs.
What are the differences between main eCos CVS and the eCosForge version of MW?
Gábor
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss