From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Auke Kok" <auke-jan.h.kok@intel.com>
Cc: "Matthew Wilcox" <matthew@wil.cx>,
"Arjan van de Ven" <arjan@infradead.org>,
"Hidetoshi Seto" <seto.hidetoshi@jp.fujitsu.com>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz, "Greg KH" <greg@kroah.com>,
"Grant Grundler" <grundler@parisc-linux.org>,
"Andrew Morton" <akpm@osdl.org>,
e1000-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org,
"Kenji Kaneshige" <kaneshige.kenji@jp.fujitsu.com>
Subject: Re: [PATCH 4/5] e1000 : Make Intel e1000 driver legacy I/O port free
Date: Wed, 22 Nov 2006 22:16:07 -0800 [thread overview]
Message-ID: <86802c440611222216u629835fepe2a39d4d34d9fefb@mail.gmail.com> (raw)
In-Reply-To: <456476B0.70705@intel.com>
On 11/22/06, Auke Kok <auke-jan.h.kok@intel.com> wrote:
> I think we want to condense the USE_IOPORT flag together with the other hardware
two cases
1. the IO port is not allocated by firmware, but
pci_assign_unassigned_resources will get that allocated.
2. the IO port is allocated by firmware, the bar will be retrieved by
pcibios_resource_survey.
so acctully the device already get the bar allocated in any case.
So what the purpose of this patch? the /poc/ioports hide ioport for the driver?
It seems need to add some pci_quirk to clear the bar for 2, and skip
the resource allocation for 1.
YH
prev parent reply other threads:[~2006-11-23 6:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 8:06 Hidetoshi Seto
2006-11-22 8:56 ` Arjan van de Ven
2006-11-22 13:54 ` Matthew Wilcox
2006-11-22 16:11 ` Auke Kok
2006-11-23 6:16 ` Yinghai Lu [this message]
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=86802c440611222216u629835fepe2a39d4d34d9fefb@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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®