Thanks for the structured reply,
that allows me to inline my answers again ;)
Shachar Kaufman wrote:
> Niels, thanks a lot for the answers!
>
> Allow me to follow up (and with your permission I won't do it inline
> to avoid clutter):
>
> 1. df_dok - I understand CPU usage metrics. What I want to know (and I
> guess I could dig in the benchmark code) is how the bar graph, shown
> for each accelerated operation at the end of the benchmark, is
> normalized.
>
It is not. It is just a representation of the Mpixels/sec or KChars/sec
output, full-screen will be around 500. You can only compare it with
future runs of the same benchmark.
> 2. Input - when I say that I don't have Linux input support I mean
> that while I have serial, USB and PS/2 (emulated) support in the
> serial console, in network terminals and under X, I don't have kernel
> support for the new input architecture ("linux input",
> http://atrey.karlin.mff.cuni.cz/~vojtech/input/
> <http://atrey.karlin.mff.cuni.cz/%7Evojtech/input/>, also see the
> inputdrivers/linux_input in directfb 1.3 source package). Since my
> input devices work fine on the other software environments I'm
> guessing it's a configuration issue that I'm having. In any case I
> tried the df_input example and from it I learned that my USB keyboard
> does in fact work but the keys are all messed up. Hopefully this would
> ring a bell for you. My mouse doesn't seem to work at all in DFB.
>
hm.. PS2 mouse should be ok.
If you are just using the keyboard driver below, than your USB keyboard
is opened via /dev/tty0, maybe that's causing some problems. Sorry,
doesn't ring a bell.
Alternatively, you can try to add linux-input-devices=... to your
directfbrc, if you know your nodes.
> 3. I'm using devmem and DFB seems to select "DirectFB/Input: Keyboard
> 0.9" as the input device. Also note I'm running DFB application from
> an SSH terminal, and DFB doesn't seem to react to the terminal
> keyboard. The output of dfbinfo is:
> ---------
> Screen (00) Screen (primary screen)
> Caps:
>
> Layer (00) GFX layer (primary layer)
> Type: GRAPHICS
> Caps: SURFACE SCREEN_LOCATION SCREEN_POSITION SCREEN_SIZE
>
>
> Input (00) Keyboard (primary keyboard)
> Type: KEYBOARD
> Caps: KEYS
> Min. Keycode: 0
> Max. Keycode: 127
This is the default keyboard driver.
It will simply open /dev/tty0, and then performs some nice tcsetattr stuff.
Guess no network supported here..
> ---------
>
> 4. I've asked here about surface/layer/region after reading the
> material on the directfb.org <http://directfb.org> website as well as
> what I managed to find on the web including the wiki. I'm still a bit
> confused. Hopefully your explenation of the common usecase will allow
> me to move forward but if you could say more on this that would be
> awsome. For instance, from what you've said I wonder - why does DFB
> need a surface manager to allocate buffers if there are only 3 buffers
> allowed per layer?
>
A surface manager is used to manage surfaces, not buffers. You can not
manage buffers separately.
The concept is layered.
At the top is the screen - what you are watching.
Below are the layer(s) - these are normally the display layers of your
hardware.
Then you get the surfaces. Surfaces are flexible, so they can be tied to
a layer - one surface to one layer - or they can be used as a generic
drawing canvas. Example: you create a surface, fill it with tux.png, and
then blit from this surface to a layer surface as much penguins as you
like (df_andi). A surface manager can manage these surfaces. In a
complex system you can have multiple types of memory, like GPU, CPU,
different memory speeds; you can define a surface manager for each of
these cases, and DirectFB will, when a surface is created by the user,
look for the optimal manager to query for a surface (+buffer(s)).
> Thanks again,
> s
>
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
