From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "fugang.duan@freescale.com" <fugang.duan@freescale.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
'Frank Li' <lznuaa@gmail.com>,
"Frank.Li@freescale.com" <Frank.Li@freescale.com>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 5/7] net:fec: add support for dumping transmit ring on timeout
Date: Fri, 30 May 2014 01:03:36 +0100 [thread overview]
Message-ID: <20140530000336.GM3693@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <51ca1e44e5e849ecbae40bf0beaa2028@BY2PR03MB377.namprd03.prod.outlook.com>
On Thu, May 29, 2014 at 08:17:07AM +0000, fugang.duan@freescale.com wrote:
> Hi, Russell,
>
> I see linux next and net "imx_v6_v7_defconfig" don't enable "CONFIG_CMA",
> if you enable the feature,
Sorry, telling people that CMA is required to avoid that is just not an
acceptable "solution".
With CMA not enabled, the DMA memory provided to the driver is still
perfectly valid and should be no different from what CMA provides.
I'd strongly suggest investigating why there is this difference, and
what the difference is - I'd assume freescale have the ability to do
that with their own devices much more than I have, and probably to a
greater depth too - especially as there is no possibility what so ever
of using any kind of hardware debug on the iMX6 platforms I have.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-05-30 0:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 12:09 [PATCH net-next 1/7] net:fec: remove unnecessary ip stack includes Frank Li
2014-04-29 12:09 ` [PATCH net-next 2/7] net:fec: reorder ethtool ops to match order in struct declaration Frank Li
2014-04-29 12:09 ` [PATCH net-next 3/7] net:fec: remove checking for NULL phy_dev in fec_enet_close() Frank Li
2014-04-29 12:09 ` [PATCH net-next 4/7] net:fec: ensure that a disconnected phy isn't configured Frank Li
2014-04-29 12:09 ` [PATCH net-next 5/7] net:fec: add support for dumping transmit ring on timeout Frank Li
2014-04-29 13:38 ` David Laight
2014-04-29 13:57 ` Frank Li
2014-04-29 14:01 ` David Laight
2014-04-29 14:15 ` Russell King - ARM Linux
2014-04-29 14:22 ` Frank Li
2014-04-29 14:30 ` Frank Li
2014-04-29 14:32 ` Russell King - ARM Linux
2014-04-29 14:54 ` Frank Li
2014-04-29 15:04 ` Russell King - ARM Linux
2014-04-29 15:11 ` Frank Li
2014-04-30 6:22 ` Shawn Guo
2014-04-29 14:18 ` Frank Li
2014-04-29 14:23 ` David Laight
2014-04-29 14:38 ` Russell King - ARM Linux
2014-05-29 8:17 ` fugang.duan
2014-05-30 0:03 ` Russell King - ARM Linux [this message]
2014-05-30 1:51 ` fugang.duan
2014-04-29 12:09 ` [PATCH net-next 6/7] net:fec: use netif_tx_disable() rather than netif_stop_queue() Frank Li
2014-04-29 12:09 ` [PATCH net-next 7/7] net:fec: iMX6 FEC does not support half-duplex gigabit Frank Li
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=20140530000336.GM3693@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=David.Laight@ACULAB.COM \
--cc=Frank.Li@freescale.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@freescale.com \
--cc=lznuaa@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@linaro.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).