Re: Standard way of graphics in Linux
- From: Herbert Kleebauer <klee@xxxxxxxxx>
- Date: Thu, 14 Sep 2006 11:09:35 +0200
Bjoern Schliessmann wrote:
Herbert Kleebauer wrote:
This was my first idea. But when I looked at a framebuffer-howto
documentation, I got aware that you first have to compile the
kernel with framebuffer support. This means (if I interpret it
correct), that the graphics program will not run on Linux
installation with a kernel compiled without framebuffer support.
Yes.
You could also compile a kernel without IDE support, but who needs
this?
Then please enlighten the ignoramus. Where in Linux is the hardware
dependent code for the graphics card located? In the kernel and X
or svgalib uses the framebuffer device to access the graphics card
(but has itself no hardware dependent code)? This would mean, that
in any Linux with X or svgalib installed, the kernel is compiled with
framebuffer support. Or is the hardware specific code for the graphics
card part of X or svgalib and I can use only one of them at a time, either
framebuffer support or X or svgalib.
And what happens when I directly access the framebuffer on
a system with KDE installed.
Why would you use the framebuffer directly?
Because when the framebuffer device is available in any system
with X or svgalib and even in some systems without X or svgalib,
than this would be the method to make a program executable on
most Linux systems.
How can my program peaceful coexist with the graphics display of
KDE. This all isn't a problem in Windows, but I just don't see it
how to do it in Linux.
I can't quite believe that you always access the framebuffer
directly in Windows -- why would that be convenient (or even
possible in Windows NT and higher)?. What's wrong about the native
APIs?
In Windows I have GDI which is available in ANY 32 bit Windows.
And I'm looking for the counterpart in Linux which is available
in ANY Linux installation (on a 32 bit x86 PC mit a graphics card).
And I have no problem to go down to the framebuffer device level if
this is available in any system and can be used in a way so it
can peaceful coexist with other graphic applications like KDE.
But as a result of all the answers here, I think the only way
to go is, to rely on the existence of X.
.
- Follow-Ups:
- Re: Standard way of graphics in Linux
- From: Bjoern Schliessmann
- Re: Standard way of graphics in Linux
- References:
- Standard way of graphics in Linux
- From: Herbert Kleebauer
- Re: Standard way of graphics in Linux
- From: Bjoern Schliessmann
- Re: Standard way of graphics in Linux
- From: Herbert Kleebauer
- Re: Standard way of graphics in Linux
- From: Wolfgang Draxinger
- Re: Standard way of graphics in Linux
- From: Herbert Kleebauer
- Re: Standard way of graphics in Linux
- From: Bjoern Schliessmann
- Re: Standard way of graphics in Linux
- From: Herbert Kleebauer
- Re: Standard way of graphics in Linux
- From: Bjoern Schliessmann
- Standard way of graphics in Linux
- Prev by Date: Re: Standard way of graphics in Linux
- Next by Date: Re: Standard way of graphics in Linux
- Previous by thread: Re: Standard way of graphics in Linux
- Next by thread: Re: Standard way of graphics in Linux
- Index(es):
Relevant Pages
|