From: mporter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU
Date: Wed, 19 Feb 2014 10:00:44 -0500 [thread overview]
Message-ID: <20140219150044.GG29906@beef> (raw)
In-Reply-To: <1391468506-5800-1-git-send-email-hauke@hauke-m.de>
On Tue, Feb 04, 2014 at 12:01:42AM +0100, Hauke Mehrtens wrote:
> This adds initial support for Broadcom network SoC from the BCM5301X
> and BCM470X line.
>
> I do not have any documentation, only the vendor source code published
> by Asus and Netgear to conform with the GPL, it would be nice to get
> some documentation for this Soc like this
> https://www.broadcom.com/collateral/pg/440X-PG02-R.pdf
> for the Broadcom BCM440X Ethernet controller.
>
> With some additional patches I got Ethernet working with ~250 MBit/s.
>
> A bootlog can be found here:
> http://hauke-m.de/files/openwrt/devices/R6250/openwrt-boot-2014-01-05.txt
>
> This is based on 3.14-rc1.
>
> Christian Daudt could you please take these patches.
Applied for 3.15
Note: our tree is now git://git.github.com/broadcom/mach-bcm
-Matt
prev parent reply other threads:[~2014-02-19 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 23:01 [PATCH v8 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU Hauke Mehrtens
2014-02-03 23:01 ` [PATCH v8 1/4] " Hauke Mehrtens
2014-02-03 23:01 ` [PATCH v8 2/4] ARM: BCM5301X: add early debugging support Hauke Mehrtens
2014-02-03 23:01 ` [PATCH v8 3/4] ARM: BCM5301X: add dts files for BCM4708 SoC Hauke Mehrtens
2014-02-03 23:01 ` [PATCH v8 4/4] ARM: BCM5301X: workaround suppress fault Hauke Mehrtens
2014-02-14 16:54 ` [PATCH v8 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU Florian Fainelli
2014-02-14 21:51 ` Matt Porter
2014-02-19 15:00 ` Matt Porter [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=20140219150044.GG29906@beef \
--to=mporter@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.