public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Martin Mares <mj@ucw.cz>, Richard Henderson <rth@twiddle.net>,
	"Wiedemeier, Jeff" <Jeff.Wiedemeier@hp.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.5] VGA IO on systems with multiple PCI IO domains
Date: Wed, 12 Mar 2003 11:08:58 -0800	[thread overview]
Message-ID: <20030312190858.GE26826@sgi.com> (raw)
In-Reply-To: <20030129190647.A689@jurassic.park.msu.ru>

On Wed, Jan 29, 2003 at 07:06:47PM +0300, Ivan Kokshaysky wrote:
> On Tue, Jan 28, 2003 at 06:23:15PM +0100, Benjamin Herrenschmidt wrote:
> > Disabling VGA dynamically depending on the machine have been a real pain
> > until now. With that change, it will now just be a matter for our PPC
> > implementation of pci_request_legacy_resource() to fail on machines
> > where VGA memory can't be reached.
> 
> Here's updated version of yesterday's patch that makes this possible.
> - pci_request_legacy_resource() is supposed to return two error codes:
>   -ENXIO (no such device or address), which must be treated as fatal;
>   -EBUSY, returned by request_resource() in the case of resource conflict,
>   like i386 case where the startup code reserves certain low memory regions
>   including video memory. This error can be ignored for now (at least in the
>   vgacon driver), because resource start/end fields are correctly adjusted
>   anyway.
> - Fixed bug wrt adjusting static struct resource (thanks to Jeff for
>   finding that). The vgacon can be started twice: early on startup and,
>   if this fails because we assumed the wrong bus, after PCI init when we
>   actually located the VGA card. However, static VGA resources are already
>   "fixed" after the first try, so the second attempt fails as well.
> - Make no_vga case to release VGA resources.

I like this patch, any chance of it getting in?  James, maybe you can
push it in your next update to Linus?  It may help our platform as
well, which is ia64 with lots of PCI busses...

Thanks,
Jesse

  parent reply	other threads:[~2003-03-12 18:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 15:13 [patch 2.5] VGA IO on systems with multiple PCI IO domains Ivan Kokshaysky
2003-01-26 21:45 ` Martin Mares
2003-01-26 23:40   ` Benjamin Herrenschmidt
2003-01-27  9:46     ` Martin Mares
2003-01-27 10:40       ` Ivan Kokshaysky
2003-01-27 17:55         ` Benjamin Herrenschmidt
2003-01-27 22:17           ` Ivan Kokshaysky
2003-01-28  9:32             ` Geert Uytterhoeven
2003-01-28 10:24               ` Ivan Kokshaysky
2003-01-28 10:27                 ` Geert Uytterhoeven
2003-01-28 10:40                   ` Ivan Kokshaysky
2003-01-28 17:10                   ` Ivan Kokshaysky
2003-01-28 17:23                     ` Benjamin Herrenschmidt
2003-01-28 17:33                       ` Ivan Kokshaysky
2003-01-29 16:06                       ` Ivan Kokshaysky
2003-01-29 18:15                         ` James Simmons
2003-02-05 11:12                           ` Ivan Kokshaysky
2003-03-12 19:08                         ` Jesse Barnes [this message]
2003-01-27 10:12     ` Ivan Kokshaysky

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=20030312190858.GE26826@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=Jeff.Wiedemeier@hp.com \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=rth@twiddle.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