This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: MicroWindows, network stack, framebuffer API
Is it OK if I add an option to use the generic fb driver and write the
required code to do this?
What about updating to a newer MicroWindows and removing the
requirement for the network? Maybe I can do this also.
I think many devices would benefit from these 3 modifications.
Gábor
On 10/28/08, Bart Veer <bartv@ecoscentric.com> wrote:
>>>>>> "tgabor" == =?ISO-8859-1?Q?G=E1bor T=F6r=F6k?= <tgabor84@gmail.com>
>>>>>> writes:
>
> tgabor> Does the MicroWindows package support the eCos framebuffer
> tgabor> API? Has anybody any experience with these packages
> tgabor> together?
>
> The MicroWindows port was done a long time ago, well before the
> generic framebuffer support was added. Instead MicroWindows currently
> uses its own drivers, see the package's CDL and its src/drivers
> subdirectory. AFAIK there are no plans to update MicroWindows to use
> the generic framebuffer support.
>
> Bart
>
> --
> Bart Veer eCos Configuration Architect
> eCosCentric Limited The eCos experts http://www.ecoscentric.com/
> Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
> Registered in England and Wales: Reg No 4422071.
>
--
Sent from Gmail for mobile | mobile.google.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss