From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yinghai <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] PCI changes for 2.6.34
Date: Sun, 28 Feb 2010 13:19:35 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002281314110.3637@localhost.localdomain> (raw)
In-Reply-To: <33223F6C-10BD-4671-937D-6D5E4956DD3F@kernel.org>
On Sun, 28 Feb 2010, Yinghai wrote:
>
> Maybe we need to put back pci=try=num back
> And set pci_try_num=1 by default
Well, why does your patch trigger any changes at all in the first place?
The old situation was fine. All the resources were mapped.
Sure, there were ROM resources that aren't even enabled, but that is
_normal_. Iirc, several graphics chips actually alias the ROM resources
with the regular memory-mapped IO resource, ie you can't even map both of
them at the same time at some separate address, because the hardware
shares address decoding resources.
There's a reson PCI ROM resources are treated specially by the kernel.
And as far as I can see, all the other resources are already allocated
even without your patch. So there is some fundamental _bug_ there. This is
not about enabling/disabling your patch, this is about your patch
apparently simply being wrong.
But maybe I'm missing something.
Linus
next prev parent reply other threads:[~2010-02-28 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:39 Jesse Barnes
2010-02-28 20:34 ` Linus Torvalds
2010-02-28 20:46 ` Linus Torvalds
2010-02-28 21:11 ` Yinghai
2010-02-28 21:19 ` Linus Torvalds [this message]
2010-02-28 22:41 ` Yinghai Lu
2010-02-28 23:49 ` [git pull] PCI changes for 2.6.34 - pci rom rom fail list Yinghai Lu
2010-03-01 6:28 ` Jesse Barnes
2010-03-01 16:05 ` Linus Torvalds
2010-03-01 16:35 ` Jesse Barnes
2010-03-01 17:38 ` Jesse Barnes
2010-02-28 23:51 ` [git pull] PCI changes for 2.6.34 -- pci_try_num Yinghai Lu
2010-03-01 1:16 ` [git pull] PCI changes for 2.6.34 Arjan van de Ven
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=alpine.LFD.2.00.1002281314110.3637@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.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®