From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Walrond <andrew@walrond.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Dual screen framebuffer development advice
Date: Sun, 20 Jun 2004 04:25:48 +0800 [thread overview]
Message-ID: <200406200425.48378.adaplas@hotpop.com> (raw)
In-Reply-To: <200406191455.56574.andrew@walrond.org>
On Saturday 19 June 2004 21:55, Andrew Walrond wrote:
> I need to setup a machine to develop a framebuffer based application. I'd
> like to use two graphics devices; The first an ati agp chipset on the
> motherboard which will run X11 with X11's ati driver, the second a PCI card
> running a fb driver and displaying my framebuffer application.
>
> Is this possible/sensible?
Sure, it's possible and actually not hard to do. Just make sure that the
driver of your primary card is fbdev, and the secondary X11. X happens to do
a fine job of initializing non-primary cards whereas fbdev is mostly
restricted to cards initialized by the firmware.
Note: You wont' be able to see both displays simultaneously, switching from
one blanks the other. If you do want multi-seat, see the Ruby project of
linuxconsole.
As for sensible, that's up to you :-)
Tony
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
next prev parent reply other threads:[~2004-06-19 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 13:55 Dual screen framebuffer development advice Andrew Walrond
2004-06-19 20:25 ` Antonino A. Daplas [this message]
2004-11-22 21:35 ` Andrew Walrond
2004-11-22 22:14 ` Antonino A. Daplas
2004-12-08 23:02 ` Andrew Walrond
2004-12-09 9:25 ` Andrew Walrond
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 20:01 Antonino A. Daplas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406200425.48378.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).