mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Olaf Hering <olh@suse.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Paul Mackeras <paulus@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: reserve legacy io regions on powermac
Date: Wed, 21 Jul 2004 19:08:56 +0200	[thread overview]
Message-ID: <A688227A-DB38-11D8-9CDF-000A95A4DC02@kernel.crashing.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0407211746200.8147@waterleaf.sonytel.be>

>>>> I think the simplest fix for 2.6 is a request_region of the 
>>>> problematic
>>>> areas.
>>>
>>> Note that this is still all workarounds... Nothing prevents you (and 
>>> some
>>> people actually do that) to put a PCI card with legacy serial ports 
>>> on it
>>> inside a pmac....
>>
>> Sure, but will that use the same io ports? I dont have one to verify 
>> it.
>
> If it's a `clean' PCI card, it will use the PCI BARs, and there's no 
> problem.

There is nothing that prevents the OF to allocate addresses in the 
"legacy"
range to the PCI cards.  In fact, the normal strategy is to allocate
starting at zero, and going upward, so 0x60 (which is one of the 
"disallowed"
addresses in Olaf's patch) is pretty easy to hit.


Segher


  reply	other threads:[~2004-07-21 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  9:12 Olaf Hering
2004-07-21 14:51 ` Benjamin Herrenschmidt
2004-07-21 14:56   ` Olaf Hering
2004-07-21 15:48     ` Geert Uytterhoeven
2004-07-21 17:08       ` Segher Boessenkool [this message]
2004-07-21 20:07   ` Jesse Barnes
2004-07-22  8:21     ` Segher Boessenkool
2004-07-23 14:21   ` Olaf Hering
2004-07-23 16:44 ` Olaf Hering
2004-07-22  0:59 Albert Cahalan

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=A688227A-DB38-11D8-9CDF-000A95A4DC02@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=paulus@samba.org \
    /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®