diff options
| author | Hauke Mehrtens <hauke@hauke-m.de> | 2014-08-24 15:57:49 +0000 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2014-08-24 15:57:49 +0000 |
| commit | 823659f458637665ebb91bcf25fae22e4ab74d6b (patch) | |
| tree | cb13ff278a99b276b38c857936cdf445eb0ce2d8 /target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch | |
| parent | befad7432bc17b6cb34ccc2bd1f0961cf161617c (diff) | |
| download | upstream-823659f458637665ebb91bcf25fae22e4ab74d6b.tar.gz upstream-823659f458637665ebb91bcf25fae22e4ab74d6b.tar.bz2 upstream-823659f458637665ebb91bcf25fae22e4ab74d6b.zip | |
bcm53xx: update bcma device tree intergeneration and fix nvram parsing
This fixes lots of sparse and checkpatch errors and extends the
documentation.
This also fixes a problem in the nvram parser, it now detects the
correct nvram on my Netgear R6250.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 42272
Diffstat (limited to 'target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch')
| -rw-r--r-- | target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch b/target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch index 312f63b370..c744e3892d 100644 --- a/target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch +++ b/target/linux/bcm53xx/patches-3.14/142-bcma-add-support-for-chipcommon-B-core.patch @@ -1,7 +1,7 @@ -From 6c0df4a483e41ef129caa8948b3bcde7f91de197 Mon Sep 17 00:00:00 2001 +From 30e85c691b905f15ef55ab9e1aea98ac35f5e31a Mon Sep 17 00:00:00 2001 From: Hauke Mehrtens <hauke@hauke-m.de> Date: Mon, 12 May 2014 20:33:15 +0200 -Subject: [PATCH 11/15] bcma: add support for chipcommon B core +Subject: [PATCH 10/17] bcma: add support for chipcommon B core This core is used on BCM4708 to configure the PCIe and USB3 PHYs and it contains the addresses to the Device Management unit. This will be used |