| commit | d42a8f464ba14467e5d45dc0eb8f789c82bd0679 | |
| author | Ben Hutchings <bhutchings@solarflare.com> | |
| Tue, 1 Jun 2010 11:32:43 +0000 (1 11:32 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Thu, 3 Jun 2010 10:27:56 +0000 (3 03:27 -0700) | ||
| tree | 5c5b597786a8fa05f38cccb856171f0f8abee031 | treesnapshot (tar.gz zip) |
| parent | fbc2e7d9cf49e0bf89b9e91fd60a06851a855c5d | commitdiff |
sfc: Get port number from CS_PORT_NUM, not PCI function number
A single shared memory region used to communicate with firmware is
mapped into both PCI PFs of the SFC9020 and SFL9021. Drivers must be
able to identify which port they are addressing in order to use the
correct sub-region. Currently we use the PCI function number, but the
PCI address may be virtualised. Use the CS_PORT_NUM register field
defined for just this purpose.
Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
A single shared memory region used to communicate with firmware is
mapped into both PCI PFs of the SFC9020 and SFL9021. Drivers must be
able to identify which port they are addressing in order to use the
correct sub-region. Currently we use the PCI function number, but the
PCI address may be virtualised. Use the CS_PORT_NUM register field
defined for just this purpose.
Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| drivers/net/sfc/net_driver.h | diffblobblamehistory | |
| drivers/net/sfc/siena.c | diffblobblamehistory |