linux-kernel - Re: [PATCH 4/5] e1000 : Make Intel e1000 driver legacy I/O port free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <86802c440611222216u629835fepe2a39d4d34d9fefb@mail.gmail.com>
Date:	Wed, 22 Nov 2006 22:16:07 -0800
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	"Auke Kok" <auke-jan.h.kok@...el.com>
Cc:	"Matthew Wilcox" <matthew@....cx>,
	"Arjan van de Ven" <arjan@...radead.org>,
	"Hidetoshi Seto" <seto.hidetoshi@...fujitsu.com>,
	"Linux Kernel list" <linux-kernel@...r.kernel.org>,
	linux-pci@...ey.karlin.mff.cuni.cz, "Greg KH" <greg@...ah.com>,
	"Grant Grundler" <grundler@...isc-linux.org>,
	"Andrew Morton" <akpm@...l.org>, e1000-devel@...ts.sourceforge.net,
	linux-scsi@...r.kernel.org,
	"Kenji Kaneshige" <kaneshige.kenji@...fujitsu.com>
Subject: Re: [PATCH 4/5] e1000 : Make Intel e1000 driver legacy I/O port free

On 11/22/06, Auke Kok <auke-jan.h.kok@...el.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/