From: Stephen Hemminger <shemminger@vyatta.com>
To: "Anoop P.A" <anoop.pa@gmail.com>
Cc: davem@davemloft.net, khilman@deeprootsystems.com, cyril@ti.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Network driver for PMC-Sierra MSP71xx TSMAC.
Date: Thu, 24 Feb 2011 09:45:56 -0800 [thread overview]
Message-ID: <20110224094556.6c371c38@nehalam> (raw)
In-Reply-To: <1298548660-10546-1-git-send-email-anoop.pa@gmail.com>
On Thu, 24 Feb 2011 17:27:40 +0530
"Anoop P.A" <anoop.pa@gmail.com> wrote:
> +#if PMC_MSP_TSMAC
> +
> +config DESC_ALL_DSPRAM
> + bool "TX/RX Descriptors in DSPRAM"
> + depends on DMA_TO_SPRAM
> + default n
> + help
> + Turning this on puts TX/RX descriptors in DSPRAM. Otherwise they are in
> + DRAM.
> +
> +config TSMAC_LINELOOPBACK_FEATURE
> + bool "lineLoopBack command"
> + default n
> + help
> + Turning this on includes the lineLoopBack command in the driver's proc
> + interface. Echoing 1 into the lineLoopBack results in all rx packets
> + being transmitted out the same port.
> +
> +config TSMAC_TEST_CMDS
> + bool "test commands"
> + default n
> + help
> + Turning this on includes the testing commands in the driver's proc
> + interface. These are used internally by PMC.
> +
Too many config options. Usually no config options is best, or at
most one debug option.
The proc interface for testing should be replaced with debugfs
prev parent reply other threads:[~2011-02-24 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 11:57 [PATCH] Network driver for PMC-Sierra MSP71xx TSMAC Anoop P.A
2011-02-24 17:35 ` Stephen Hemminger
2011-02-24 17:45 ` Stephen Hemminger [this message]
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=20110224094556.6c371c38@nehalam \
--to=shemminger@vyatta.com \
--cc=anoop.pa@gmail.com \
--cc=cyril@ti.com \
--cc=davem@davemloft.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.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).