Tiny Core Base > TCB Talk

xvesa vs xfbdev

<< < (2/4) > >>

tinypoodle:
Xfbdev is an X server.

Marco Trapanese:
It seems I missed something   :o

In the faq I read:


In order to use framebuffer (Xfbdev) you [...]



So I understand the Xfbdev is the framebuffer.
In fact if I follow that guide I can run my GUI application at prompt, without assert start X.

I'm a bit confused....   ???

SvOlli:

--- Quote from: Marco Trapanese on August 26, 2010, 09:35:00 AM ---
In order to use framebuffer (Xfbdev) you [...]


--- Quote ---Please also read the heading above the text: "How to use framebuffer X server?"


--- Quote from: Marco Trapanese on August 26, 2010, 09:35:00 AM ---So I understand the Xfbdev is the framebuffer.
In fact if I follow that guide I can run my GUI application at prompt, without assert start X.

--- End quote ---
No, Xfbdev is an X server drawing its contents in the framebuffer. An X server can draw on real graphics hardware, it can draw on a software interface to hardware (Xfbdev), and it can draw in a pure virtual context (Xnest, and the first vncserver). If you follow the instructions you typed in "startx" which starts the X server, on reboot the Xfbdev is started automatically, just like any other X server.
--- End quote ---

--- End quote ---

Marco Trapanese:
I typed startx to save the configuration. Then I rebooted with text flag. When I was at prompt I launched my Qt Embedded application (with -qws) and the prompt disappeared, showing a green background with my application. I exited with ctrl-alt-backspace, returning to prompt.

Then, I typed startx and the tinycore desktop appeared.

I'm just trying to understand what I did  :o

Marco Trapanese:
Anyway the question is:

do you recommend to run embedded graphical applications (on boards like beagle board or Atom-based) with the framebuffer or with an X server?
The goal is to make a turn-on-turn-off machine, with no dekstop nor multiple applications.

Navigation

[0] Message Index

[#] Next page

[*] Previous page