public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: 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: 28 Jan 2003 18:23:15 +0100	[thread overview]
Message-ID: <1043774595.536.4.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030128201057.A690@jurassic.park.msu.ru>

On Tue, 2003-01-28 at 18:10, Ivan Kokshaysky wrote: 
> Here's the patch that converts vgacon.c to pci_request_legacy_resource().
> Tested on i386 and a single-bus alpha (alpha specific bits not included
> here).
> 
> Note that it breaks ppc, as VGA_MAP_MEM() is removed...

Ok, if I understand properly, all we have to do on PPC is to implement a
pci_request_legacy_resource() that will do the right thing for legacy
VGA memory as well ?

Then, please, check the return value of pci_request_legacy_resource()
for getting to the VGA memory. Some machines (typically PowerMacs)
simply don't give you a way to generate PCI cycles to those low memory
addresses (you can't do VGA on those).

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.

Ben.




  reply	other threads:[~2003-01-28 17:13 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 [this message]
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
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=1043774595.536.4.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=Jeff.Wiedemeier@hp.com \
    --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