From: Jerzy Dyrda <jerzdy@gmail.com>
To: Andrew Hannam <andrewh@inmarket.com.au>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] First try eCos port for uGFX
Date: Sun, 06 Jul 2014 20:04:00 -0000 [thread overview]
Message-ID: <CABmKEG8+S55PG1xfo0i6QEPx4rqzXmeLsE8j2rmMbUdKvAMG9g@mail.gmail.com> (raw)
In-Reply-To: <004b01cf9711$8313b9e0$893b2da0$@inmarket.com.au>
Hello Andrew,
2014-07-04 0:52 GMT+02:00 Andrew Hannam <andrewh@inmarket.com.au>:
> Hi Jerzy,
>
> Thanks for your assistance with this. Please feel free to message me directly any questions you have.
> Hopefully I have already completed the eCos framebuffer interface for you.
Thank you. Regarding porting to eCos : SUCCESS.
Now I'm able to run few demos under eCos synthetic fremabuffer.
There are 2 or 3 very small fix to add like :
diff --git a/boards/addons/gdisp/board_framebuffer_eCos.h
b/boards/addons/gdisp/board_framebuffer_eCos.h
index 80c9147..e8e4613 100644
--- a/boards/addons/gdisp/board_framebuffer_eCos.h
+++ b/boards/addons/gdisp/board_framebuffer_eCos.h
@@ -28,7 +28,7 @@
// SET THIS HERE!!!
// This must also match the pixel format above
- #define FRAMEBUF 640x480x16
+ #define FRAMEBUF fb0
static void board_init(GDisplay *g, fbInfo *fbi) {
// Initialize the frame buffer device - we assume
everything is going to succeed.
and uGFX works under eCos as a application.
>If you want a Linux frame-buffer type interface have a look in the "boards/base/Linux-framebuffer" directory for the board_framebuffer.h in there.
I asked about Linux frame-buffer because initially I had a problem
with dependencies. After I had used Linux Makefile I manage to build.
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?
Best regards,
jerzy
> -----Original Message-----
> From: Jerzy Dyrda [mailto:jerzdy@gmail.com]
> Sent: Friday, 4 July 2014 8:26 AM
> To: Andrew Hannam
> Cc: eCos Discussion
> Subject: Re: [ECOS] First try eCos port for uGFX
>
> Hello Andrew,
>
> 2014-07-02 4:23 GMT+02:00 Andrew Hannam <andrewh@inmarket.com.au>:
>> I have implemented a first attempt at an eCos port for uGFX.
> Thank you.
>
> [snip]
>
>> 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.
> I was mostly interested in thus I feel obligated to contribute.
> Initially I would like add similar structure compering to Linux_framebuffer.
> In eCos nomenclature it means uGFX wit ones of demos will be treated as application and linked against eCos tree.
--
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:[~2014-07-06 20:04 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 [this message]
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=CABmKEG8+S55PG1xfo0i6QEPx4rqzXmeLsE8j2rmMbUdKvAMG9g@mail.gmail.com \
--to=jerzdy@gmail.com \
--cc=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).