public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Andrew Hannam" <andrewh@inmarket.com.au>
To: "'eCos Discussion'" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] First try eCos port for uGFX
Date: Wed, 02 Jul 2014 02:23:00 -0000	[thread overview]
Message-ID: <004801cf959c$a80fac70$f82f0550$@inmarket.com.au> (raw)

I have implemented a first attempt at an eCos port for uGFX.

Unfortunately I have run out of time for now as I have to spend time on some
other work.
I wanted to put this up here in case someone in the eCos community would
like to continue that process to get a full working port and package
together for uGFX under eCos.

Where it is at...
 - The eCos port can be found in the eCos branch of the uGFX git repository
at https://bitbucket.org/Tectu/ugfx.git
 - The uGFX GOS module port should be complete but is probably not
implemented very well. Eg currently it assumes the C runtime
    is initialised to use functions such as malloc() and free().
- There is a board interface file
"boards/addons/gdisp/board_framebuffer_eCos.h" that should interface the
uGFX
   library using the uGFX framebuffer driver to the eCos framebuffer device.
This file should be copied into the
   users project and renamed "board_framebuffer.h". Alternatively any of the
other uGFX display drivers
   can be used.
- Code is written but has not been compiled or tested. Unfortunately I have
not yet got the eCos tools working on my
   machine (Win8.1 x64, 64 bit Cygwin). I suspect I need to install 32 bit
Cygwin but currently have run out of time.
- No packaging has been started yet. It looks like all the uGFX compile
options could very easily be added to
   make a "full featured" eCos package as the options system looks
relatively compatible.

If no-one is able to take it up, I hope in the next few weeks I will be able
to get back to it.

Regards,
Andrew.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2014-07-02  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  2:23 Andrew Hannam [this message]
2014-07-03 22:26 ` Jerzy Dyrda
     [not found]   ` <004b01cf9711$8313b9e0$893b2da0$@inmarket.com.au>
2014-07-06 20:04     ` Jerzy Dyrda
2014-07-06 23:34       ` Andrew Hannam

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='004801cf959c$a80fac70$f82f0550$@inmarket.com.au' \
    --to=andrewh@inmarket.com.au \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).