linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Egbert Eich <eich@suse.de>
To: Zoltan Boszormenyi <zboszor@dunaweb.hu>
Cc: Xserver development <xorg@freedesktop.org>,
	fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Who is stomping PCI config space?
Date: Fri, 4 Mar 2005 12:21:39 +0100	[thread overview]
Message-ID: <16936.17603.208177.829376@xf14.local> (raw)
In-Reply-To: zboszor@dunaweb.hu wrote on Thursday, 3 March 2005 at 23:08:44 +0100

Zoltan Boszormenyi writes:
 > Hm. Someone other than a Linux-ruby user finally complaining. :-)
 > Try patching XFree or XOrg with the proper patch
 > 
 > http://www.ltn.lv/~aivils/files/080_pci_isolate_device_feature.diff
 > 
 > for XFree, or
 > 
 > http://www.ltn.lv/~aivils/files/Xorg-6.7.0-isolate_device.patch
 > 
 > for XOrg, it's applicable for XOrg-6.8.x, too.
 > 
 > Then add
 >           Option         "SingleCard" "on"
 > to your Section "ServerLayout".
 > 

This patch adds another wart to the resource broker ;-)
But it may actually help the people who need this advanced 
feature and know what they are doing.
I have thought about putting something like this in but was
discouraged when I saw users trying out every single option
and then complaining that it didn't work.

I would rather go with something 'automatic'. This would be
a resource broker outside of X.

Still I'm inclined to adding something like this to the code
however I'm reluctant to document it so well ;-)

Cheers,
	Egbert.

      parent reply	other threads:[~2005-03-04 11:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 19:03 Who is stomping PCI config space? Jon Smirl
2005-03-03 23:07 ` Benjamin Herrenschmidt
2005-03-04  0:15   ` Jon Smirl
2005-03-04  3:03     ` Jon Smirl
2005-03-04  6:40       ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-04 12:07         ` Egbert Eich
2005-03-04 17:35           ` Jon Smirl
2005-03-04 22:42             ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 19:06               ` Egbert Eich
2005-03-05 22:42                 ` Benjamin Herrenschmidt
2005-03-07 11:19                   ` Egbert Eich
2005-03-08  3:21                     ` Benjamin Herrenschmidt
2005-03-05 17:33             ` Egbert Eich
2005-03-04 17:58           ` Jon Smirl
2005-03-04 22:45             ` Benjamin Herrenschmidt
2005-03-05 19:07               ` Egbert Eich
2005-03-05 22:43                 ` Benjamin Herrenschmidt
2005-03-04 22:27           ` Benjamin Herrenschmidt
2005-03-05 18:26             ` Egbert Eich
2005-03-05 22:39               ` Benjamin Herrenschmidt
2005-03-07 11:05                 ` Egbert Eich
2005-03-04 12:02       ` Egbert Eich
2005-03-04 11:25   ` Egbert Eich
2005-03-04 22:16     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 17:36       ` Egbert Eich
2005-03-04 11:12 ` Egbert Eich
2005-03-04 22:51   ` Benjamin Herrenschmidt
     [not found] ` <42278AEC.4080706@dunaweb.hu>
2005-03-04 11:21   ` Egbert Eich [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=16936.17603.208177.829376@xf14.local \
    --to=eich@suse.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=xorg@freedesktop.org \
    --cc=zboszor@dunaweb.hu \
    /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).