From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org, brice@myri.com
Cc: netdev@vger.kernel.org, peter.oruba@amd.com, rolandd@cisco.com,
shemminger@linux-foundation.org
Subject: Re: [patch 06/18] PCI-X/PCI-Express read control interfaces: use them in myrinet
Date: Tue, 14 Aug 2007 01:30:13 -0400 [thread overview]
Message-ID: <46C13DE5.2070107@garzik.org> (raw)
In-Reply-To: <200708102105.l7AL5H0a008960@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> From: "Peter Oruba" <peter.oruba@amd.com>
>
> These driver changes incorporate the proposed PCI-X / PCI-Express read byte
> count interface. Reading and setting those valuse doesn't take place
> "manually", instead wrapping functions are called to allow quirks for some
> PCI bridges.
>
> Signed-off by: Peter Oruba <peter.oruba@amd.com>
> Based on work by Stephen Hemminger <shemminger@linux-foundation.org>
> Cc: Roland Dreier <rolandd@cisco.com>
> Cc: Brice Goglin <brice@myri.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/net/myri10ge/myri10ge.c | 3 +--
> 1 files changed, 1 insertion(+), 2 deletions(-)
>
> diff -puN drivers/net/myri10ge/myri10ge.c~pci-x-pci-express-read-control-interfaces-myrinet drivers/net/myri10ge/myri10ge.c
> --- a/drivers/net/myri10ge/myri10ge.c~pci-x-pci-express-read-control-interfaces-myrinet
> +++ a/drivers/net/myri10ge/myri10ge.c
> @@ -2884,8 +2884,7 @@ static int myri10ge_probe(struct pci_dev
> status);
> goto abort_with_netdev;
> }
> - val = (val & ~PCI_EXP_DEVCTL_READRQ) | (5 << 12);
> - status = pci_write_config_word(pdev, cap + PCI_EXP_DEVCTL, val);
> + status = pcie_set_readrq(pdev, 4096);
I presume Brice will resend this one to me, next time he pushes...
next prev parent reply other threads:[~2007-08-14 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:05 [patch 06/18] PCI-X/PCI-Express read control interfaces: use them in myrinet akpm
2007-08-14 5:30 ` Jeff Garzik [this message]
2007-08-14 5:49 ` Brice Goglin
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=46C13DE5.2070107@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=brice@myri.com \
--cc=netdev@vger.kernel.org \
--cc=peter.oruba@amd.com \
--cc=rolandd@cisco.com \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).