From: "Andrew Hannam" <andrewh@inmarket.com.au>
To: "'Jerzy Dyrda'" <jerzdy@gmail.com>
Cc: "'eCos Discussion'" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] First try eCos port for uGFX
Date: Sun, 06 Jul 2014 23:34:00 -0000 [thread overview]
Message-ID: <007101cf9972$d2cf0da0$786d28e0$@inmarket.com.au> (raw)
In-Reply-To: <CABmKEG8+S55PG1xfo0i6QEPx4rqzXmeLsE8j2rmMbUdKvAMG9g@mail.gmail.com>
> Thank you. Regarding porting to eCos : SUCCESS.
> Now I'm able to run few demos under eCos synthetic fremabuffer.
Well done!
> There are 2 or 3 very small fix to add like :
I will add them to the repository today and merge them into the main branch now that you have confirmed it works.
> I asked about Linux frame-buffer because initially I had a problem with dependencies. After I had used Linux Makefile I manage to build.
Can you please send me your makefile and I will create a new boards/base/eCos directory based on your makefile.
> Now is the question how you would like to provide uGFX :
> 1) as a application in eCos meaning
> 2) or add to tree as a eCos package?
Ideally moving forward it would be great to do it as an eCos package. This would enable the closest interaction with eCos. In the mean-time at least it will run as an application.
Any assistance I can provide please let me know.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2014-07-06 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 2:23 Andrew Hannam
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 [this message]
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='007101cf9972$d2cf0da0$786d28e0$@inmarket.com.au' \
--to=andrewh@inmarket.com.au \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jerzdy@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).