From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Stephen Hemminger" <shemminger@linux-foundation.org>
Cc: bryan.wu@analog.com, "Andrew Morton" <akpm@linux-foundation.org>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH -mm 3/5] Blackfin: on-chip ethernet MAC controller driver
Date: Thu, 1 Mar 2007 13:21:27 -0500 [thread overview]
Message-ID: <8bd0f97a0703011021s3d74b129yaa59ce65142115e0@mail.gmail.com> (raw)
In-Reply-To: <45E6F6D6.5000804@linux-foundation.org>
On 3/1/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> Wu, Bryan wrote:
> > +config BFIN_MAC
> > + tristate "Blackfin 536/537 on-chip mac support"
> > + depends on NET_ETHERNET && (BF537 || BF536) && (!BF537_PORT_H)
> > + select CRC32
> > + select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
> > + help
> > + This is the driver for blackfin on-chip mac device. Say Y if you want it
> > + compiled into the kernel. This driver is also available as a module
> > + ( = code which can be inserted in and removed from the running kernel
> > + whenever you want). The module will be called bfin_mac.
> > +
> > +config BFIN_MAC_USE_L1
> > + bool "Use L1 memory for rx/tx packets"
> > + depends on BFIN_MAC && BF537
> > + default y
> > + help
> > + To get maximum network performace, you should use L1 memory as rx/tx buffers.
> > + Say N here if you want to reserve L1 memory for other uses.
> > +
> > +config BFIN_TX_DESC_NUM
> > + int "Number of transmit buffer packets"
> > + depends on BFIN_MAC
> > + range 6 10 if BFIN_MAC_USE_L1
> > + range 10 100
> > + default "10"
> > + help
> > + Set the number of buffer packets used in driver.
> > +
> > +config BFIN_RX_DESC_NUM
> > + int "Number of receive buffer packets"
> > + depends on BFIN_MAC
> > + range 20 100 if BFIN_MAC_USE_L1
> > + range 20 800
> > + default "20"
> > + help
> > + Set the number of buffer packets used in driver
> >
> The regular practice is to put these in a device include file, and not
> make them kernel configurable.
we're working on moving some of this stuff into the board files rather
than Kconfig
> Why would you want to make it tuneable at compile time?
because it was easier to implement and deploy the first time around ;)
-mike
next prev parent reply other threads:[~2007-03-01 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 4:15 Wu, Bryan
2007-03-01 8:53 ` Andrew Morton
2007-03-01 15:52 ` Stephen Hemminger
2007-03-01 18:21 ` Mike Frysinger [this message]
2007-03-01 18:35 ` Robin Getz
2007-03-02 8:08 ` Wu, Bryan
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=8bd0f97a0703011021s3d74b129yaa59ce65142115e0@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®