mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>, Martin Mares <mj@ucw.cz>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Zoltan Szecsei <zoltans@geograph.co.za>,
	linux-kernel@vger.kernel.org
Subject: Re: multiple independent keyboard kernel support
Date: Mon, 12 Sep 2005 16:47:28 -0400	[thread overview]
Message-ID: <F96CD1EB-5963-49CF-9B8B-7934925BE79D@mac.com> (raw)
In-Reply-To: <200509121003.11086.bjorn.helgaas@hp.com>

On Sep 12, 2005, at 12:03:11, Bjorn Helgaas wrote:
> On Sunday 11 September 2005 4:36 pm, Helge Hafting wrote:
>> Look again.  X config files now have "IsolateDevice" and "BusID"
>> to deal with this.  At least iff you get your X from ubuntu or
>> debian testing . . .
>
> Yes, but I think IsolateDevice still isn't quite enough if you
> have VGA devices behind PCI-PCI bridges.  In other words, devices
> behind bridges still get disabled, even with IsolateDevice.
>
> And the ideal situation would be if IsolateDevice could be the
> *default*, but the X bugzilla[1] says some devices have problems
> with that.

IIRC, someone was working on a VGA arbiter and some PCI-access kernel  
code
upon which X.org could be rebuilt.  Then all the messy /dev/mem issues
relating to PCI bus smashing go away (including the need for iopl, root
privts, etc), and a properly configured system could run X.org as a  
normal
user on any attached devices that user has permission to, including  
video
cards, displays, keyboards, mice, graphics tablets, joysticks, etc.

Unfortunately the project is not exactly small, so it wasn't moving very
quickly last I remember...

Cheers,
Kyle Moffett

--
Unix was not designed to stop people from doing stupid things,  
because that
would also stop them from doing clever things.
   -- Doug Gwyn



  reply	other threads:[~2005-09-12 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 11:28 Zoltan Szecsei
2005-09-01 12:22 ` Vojtech Pavlik
2005-09-01 13:07   ` Zoltan Szecsei
2005-09-01 13:24     ` Vojtech Pavlik
2005-09-01 14:48       ` Martin Mares
2005-09-01 16:38         ` Vojtech Pavlik
2005-09-11 22:36         ` Helge Hafting
2005-09-12 16:03           ` Bjorn Helgaas
2005-09-12 20:47             ` Kyle Moffett [this message]
2005-09-13 16:20               ` Bjorn Helgaas
2005-09-11 22:34 ` Helge Hafting
2005-09-12  7:01   ` Zoltan Szecsei
2005-10-19 16:01   ` Zoltan Szecsei
2005-10-19 19:23     ` Helge Hafting
2005-09-01 13:35 Svetoslav Slavtchev
2005-09-01 14:06 ` Zoltan Szecsei

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=F96CD1EB-5963-49CF-9B8B-7934925BE79D@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=vojtech@suse.cz \
    --cc=zoltans@geograph.co.za \
    /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

all inboxes | Powered by JetHome®