From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Rasesh Mody <rmody@brocade.com>,
e1000-devel@lists.sourceforge.net,
Bruce Allan <bruce.w.allan@intel.com>,
John Ronciak <john.ronciak@intel.com>,
netdev@vger.kernel.org
Subject: Re: [RFC 0/7] Fixing dma mask setting in various network drivers
Date: Mon, 17 Jun 2013 15:01:45 +0100 [thread overview]
Message-ID: <20130617140145.GH2718@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130611111230.000062d2@unknown>
On Tue, Jun 11, 2013 at 11:12:30AM -0700, Jesse Brandeburg wrote:
> This is my proposed change to the intel drivers. Comments?
>
> + if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(64))) {
> + pci_using_dac = true;
> + /* coherent mask for the same size will always succeed if
> + * dma_set_mask does
> + */
> + dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(64));
> + } else if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(32))) {
> + pci_using_dac = false;
> + dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(32));
> + } else {
> + dev_err(&pdev->dev, "%s: DMA configuration failed: %d\n",
> + __func__, err);
> + err = -EIO;
> + goto err_dma;
> }
>
So, will you be going with this change rather than mine, which apparantly
Jeff queued? Please let me know what you decide so I can keep my private
git tree in sync with what you've decided to avoid conflicting with
further dma-mask changes which I'm working on.
Thanks.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2013-06-17 14:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 23:08 [RFC 0/7] Fixing dma mask setting in various network drivers Russell King - ARM Linux
2013-06-10 23:09 ` [PATCH 1/7] NET: brocade/bna/bnad.c: fix 32-bit DMA mask handling Russell King
2013-06-10 23:10 ` [PATCH 2/7] NET: intel/e1000e/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:11 ` [PATCH 3/7] NET: intel/igb/igb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:12 ` [PATCH 4/7] NET: intel/igbvf/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:13 ` [PATCH 5/7] NET: intel/ixgb/ixgb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:14 ` [PATCH 6/7] NET: intel/ixgbe/ixgbe_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-10 23:15 ` [PATCH 7/7] NET: intel/ixgbevf/ixgbevf_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-11 18:12 ` [RFC 0/7] Fixing dma mask setting in various network drivers Jesse Brandeburg
2013-06-11 20:35 ` Russell King - ARM Linux
2013-06-11 23:50 ` Jesse Brandeburg
2013-06-12 0:01 ` Russell King - ARM Linux
2013-06-17 14:01 ` Russell King - ARM Linux [this message]
2013-06-17 20:35 ` Jeff Kirsher
2013-06-17 20:45 ` Russell King - ARM Linux
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=20130617140145.GH2718@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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;
as well as URLs for NNTP newsgroup(s).