From: "David S. Miller" <davem@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Tom Gall <tom_gall@vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Going beyond 256 PCI buses
Date: Fri, 15 Jun 2001 08:38:48 -0700 (PDT) [thread overview]
Message-ID: <15146.11272.896877.462646@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.05.10106151041590.32503-100000@callisto.of.borg>
In-Reply-To: <15145.3254.105970.424506@pizda.ninka.net> <Pine.LNX.4.05.10106151041590.32503-100000@callisto.of.borg>
Geert Uytterhoeven writes:
> Well, those resource conflicts shouldn't be there in the first place. They
> should be handled by the OS.
I agree, completely.
But this doesn't solve the issue of reserving resources inside the
X server. Ie. making sure one driver doesn't take the register area
another driver is using.
You still need to get the controller number into the resources to do
that properly.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-06-15 15:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 10:02 Tom Gall
2001-06-13 17:17 ` Albert D. Cahalan
2001-06-13 18:29 ` Tom Gall
2001-06-14 14:14 ` Jeff Garzik
2001-06-14 15:15 ` David S. Miller
2001-06-14 17:59 ` Jonathan Lundell
2001-06-14 20:50 ` Jonathan Lundell
2001-06-14 14:24 ` David S. Miller
2001-06-14 14:32 ` Jeff Garzik
2001-06-14 14:42 ` David S. Miller
2001-06-14 15:29 ` Jeff Garzik
2001-06-14 15:33 ` Jeff Garzik
2001-06-14 18:01 ` Albert D. Cahalan
2001-06-14 18:47 ` David S. Miller
2001-06-14 19:04 ` Albert D. Cahalan
2001-06-14 19:12 ` David S. Miller
2001-06-14 19:41 ` Jeff Garzik
2001-06-14 19:57 ` David S. Miller
2001-06-14 20:08 ` Jeff Garzik
2001-06-14 20:14 ` David S. Miller
2001-06-14 21:30 ` Benjamin Herrenschmidt
2001-06-14 21:46 ` Jeff Garzik
2001-06-14 21:48 ` David S. Miller
2001-06-14 21:57 ` Benjamin Herrenschmidt
2001-06-14 22:12 ` David S. Miller
2001-06-14 22:29 ` Benjamin Herrenschmidt
2001-06-14 22:49 ` David S. Miller
2001-06-14 23:35 ` Benjamin Herrenschmidt
2001-06-14 23:35 ` VGA handling was [Re: Going beyond 256 PCI buses] James Simmons
2001-06-14 23:42 ` David S. Miller
2001-06-14 23:55 ` James Simmons
2001-06-15 15:14 ` Pavel Machek
2001-06-15 2:06 ` Albert D. Cahalan
2001-06-15 8:52 ` Matan Ziv-Av
2001-06-14 21:35 ` Going beyond 256 PCI buses David S. Miller
2001-06-14 21:46 ` Benjamin Herrenschmidt
2001-06-16 21:32 ` Jeff Garzik
2001-06-16 23:29 ` Benjamin Herrenschmidt
2001-06-15 8:42 ` Geert Uytterhoeven
2001-06-15 15:38 ` David S. Miller [this message]
2001-06-14 19:03 ` David S. Miller
2001-06-14 20:56 ` David S. Miller
2001-06-14 15:13 ` Jonathan Lundell
2001-06-14 15:17 ` Jeff Garzik
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=15146.11272.896877.462646@pizda.ninka.net \
--to=davem@redhat.com \
--cc=acahalan@cs.uml.edu \
--cc=geert@linux-m68k.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom_gall@vnet.ibm.com \
/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®