* opening the framebuffer device
@ 2005-07-11 11:47 subramanyam yenugonda
2005-07-12 12:55 ` Helge Hafting
0 siblings, 1 reply; 2+ messages in thread
From: subramanyam yenugonda @ 2005-07-11 11:47 UTC (permalink / raw)
To: linux-kernel
Hi All!
How to open the frame buffer device if user has
multiple monitors on single video card.
Thanks in advance.
~YSM
__________________________________________________________
Free antispam, antivirus and 1GB to save all your messages
Only in Yahoo! Mail: http://in.mail.yahoo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: opening the framebuffer device
2005-07-11 11:47 opening the framebuffer device subramanyam yenugonda
@ 2005-07-12 12:55 ` Helge Hafting
0 siblings, 0 replies; 2+ messages in thread
From: Helge Hafting @ 2005-07-12 12:55 UTC (permalink / raw)
To: subramanyam yenugonda; +Cc: linux-kernel
subramanyam yenugonda wrote:
>Hi All!
>
>How to open the frame buffer device if user has
>multiple monitors on single video card.
>
>Thanks in advance.
>~YSM
>
>
You open the _correct_ framebuffer device.
Linux support multiple framebuffer devices, e.g.
/dev/fb0 /dev/fb1 /dev/fb2 ...
The matrox G550 support this, set the correct kernel config options
and you get both /dev/fb0 and /dev/fb1 (for the second head.)
This is the way to go if you want _independent_ monitors.
Some other drivers create a large framebuffer that spans several
monitors - ideal for the common case of one big desktop spread
across several monitors. In those cases, you open /dev/fb0,
and find the different monitor bitmaps at different offsets inside that
file.
Helge Hafting
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-07-12 12:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-07-11 11:47 opening the framebuffer device subramanyam yenugonda
2005-07-12 12:55 ` Helge Hafting
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 NNTP newsgroup(s).