From: Hamish Marson <hamish@travellingkiwi.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xinerama after Modular X upgrade
Date: Sat, 15 Apr 2006 10:51:33 +0100 [thread overview]
Message-ID: <4440C225.8000809@travellingkiwi.com> (raw)
In-Reply-To: <358eca8f0604041501l5b6f89deh28439f97622ad507@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mick wrote:
> On 03/04/06, Kurt Guenther <kurtg@serent.com> wrote:
>
>> Mick wrote:
>>
>>> Shouldn't the second device have a different BusID No?
>>> Something like 1:0:1
>>
>> Yes, if you have two different devices. It's a laptop, so the
>> video has two ports for same device. It worked fine under xorg
>> 6.? .
>>
>> --Kurt
>
>
> Hmm, I don't know then. :-(
>
> If I remember correctly mine has one device (i.e. one video card)
> but two ports, which are identified differently. Perhaps its worth
> giving it a try.
Some (All? Sorry, covering arse here) cards (e.g. Saphire radeon 9600
- - whch uses an rv350 chip) have two PCI id's covering the same
physcial card. I originally asked about this back when the r300
project started. Apparently Windows requires the two pci id's in order
to see the two CRT controllers that the cards have.
X ignores it & accesses everything via the first pci id. (In fact IIRC
X doesn't even work through the second head pci id at all, so don't
even try to use it).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEQMIl/3QXwQQkZYwRAnKmAKCrwOXquJYFm1Y/BOp6NZxSkmyxBwCfWspY
rwnciC7U6G1MLrZIeCm95Ek=
=upPe
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-04-15 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 17:27 [gentoo-user] Xinerama after Modular X upgrade Kurt Guenther
2006-04-01 17:34 ` Kurt Guenther
2006-04-02 13:33 ` Mick
2006-04-03 11:26 ` Kurt Guenther
2006-04-04 22:01 ` Mick
2006-04-15 9:51 ` Hamish Marson [this message]
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=4440C225.8000809@travellingkiwi.com \
--to=hamish@travellingkiwi.com \
--cc=gentoo-user@lists.gentoo.org \
/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