From: Ralf Baechle <ralf@linux-mips.org>
To: Vivien Chappelier <vivienc@nerim.net>
Cc: "Ilya A. Volynets-Evenbakh" <ilya@theIlya.com>,
jsun@mvista.com, linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6] PCI I/O region starting from zero is valid
Date: Sat, 13 Dec 2003 04:24:59 +0100 [thread overview]
Message-ID: <20031213032459.GE22448@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0312130147150.24966-100000@melkor>
On Sat, Dec 13, 2003 at 01:54:27AM +0100, Vivien Chappelier wrote:
> PCI devices can have I/O mapped at a region starting from
> 0x0000. The O2 actually has one of its onboard SCSI controller here...
> This code looks like a incorrect copy/paste from the x86 code where this
> I/O range is used by legacy ISA.
>
> --- arch/mips/pci/pci.c 2003-11-12 16:51:09.000000000 +0100
> +++ arch/mips/pci/pci.c 2003-12-13 00:57:56.000000000 +0100
> @@ -173,10 +173,6 @@
> continue;
>
> r = &dev->resource[idx];
> - if (!r->start && r->end) {
> - printk(KERN_ERR "PCI: Device %s not available because of resource collisions\n", pci_name(dev));
> - return -EINVAL;
> - }
> if (r->flags & IORESOURCE_IO)
> cmd |= PCI_COMMAND_IO;
> if (r->flags & IORESOURCE_MEM)
>
I tend to agree with Vivien. There's another unsolved problem with
pcibios_enable_device - how many resources should it enable? Jun once
changed it to PCI_NUM_RESOURCES but that broke other systems though it
seems the logic thing to do ...
The code he wants to remove is just a safety check for PCs. It doesn't
much sense on legacy-free systems and these days less and less MIPS
systems have legacy devices.
I forgot the details but maybe removing above lines will even permit
putting back the change Jun needed, will need to test.
Ralf
next parent reply other threads:[~2003-12-13 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0312130147150.24966-100000@melkor>
2003-12-13 3:24 ` Ralf Baechle [this message]
2003-12-13 12:15 ` [PATCH 2.6] PCI I/O region starting from zero is valid Geert Uytterhoeven
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=20031213032459.GE22448@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ilya@theIlya.com \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=vivienc@nerim.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