From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: LPC32xx: Ethernet support
Date: Mon, 27 Feb 2012 18:17:43 +0000 [thread overview]
Message-ID: <20120227181742.GD2440@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1330364762-23203-1-git-send-email-stigge@antcom.de>
On Mon, Feb 27, 2012 at 06:46:02PM +0100, Roland Stigge wrote:
> +menu "LPC32XX chip components"
> +
> +config ARCH_LPC32XX_IRAM_FOR_NET
> + bool "Use IRAM for network buffers"
> + default n
n is the default.
> + help
> + Say Y here to use the LPC internal fast IRAM (i.e. 256KB SRAM) as
> + network buffer. If the total combined required buffer sizes is
> + larger than the size of IRAM, then SDRAM will be used instead.
> +
> + This can be enabled safely if the IRAM is not intended for other
> + uses.
> +
> +config ARCH_LPC32XX_MII_SUPPORT
> + bool "Check to enable MII support or leave disabled for RMII support"
> + default n
Ditto.
> --- linux-2.6.orig/arch/arm/mach-lpc32xx/common.c
> +++ linux-2.6/arch/arm/mach-lpc32xx/common.c
> @@ -186,6 +186,40 @@ struct platform_device lpc32xx_ohci_devi
> };
>
> /*
> + * Network Support
> + */
> +static struct lpc_net_cfg lpc32xx_netdata = {
> + .phy_irq = -1,
> + .phy_mask = 0xFFFFFFF0,
> +};
> +
> +static struct resource net_resources[] = {
> + [0] = {
> + .start = LPC32XX_ETHERNET_BASE,
> + .end = LPC32XX_ETHERNET_BASE + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
DEFINE_RES_MEM() ?
> + [1] = {
> + .start = IRQ_LPC32XX_ETHERNET,
> + .end = IRQ_LPC32XX_ETHERNET,
> + .flags = IORESOURCE_IRQ,
> + },
DEFINE_RES_IRQ() ?
prev parent reply other threads:[~2012-02-27 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 17:46 [PATCH v3] ARM: LPC32xx: Ethernet support Roland Stigge
2012-02-27 18:08 ` Wolfram Sang
2012-02-27 22:04 ` Roland Stigge
2012-02-27 23:10 ` Kevin Wells
2012-02-28 6:38 ` Arnd Bergmann
2012-02-27 18:17 ` Russell King - ARM Linux [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=20120227181742.GD2440@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).