Looks like the BCM53012 has a similar problem to the BCM53011.
Signed-off-by: Ian Kent
---
...-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch | 12 +++-
...-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch | 12 +++-
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git
On Mon, 2015-03-09 at 10:23 +0100, Rafał Miłecki wrote:
> On 9 March 2015 at 10:08, Ian Kent wrote:
> > Looks like the BCM53012 has a similar problem to the BCM53011.
>
> Change looks OK, however I'd prefer you to simply modify existing
> patch 170-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch
>
On 9 March 2015 at 10:08, Ian Kent wrote:
> Looks like the BCM53012 has a similar problem to the BCM53011.
Change looks OK, however I'd prefer you to simply modify existing
patch 170-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch
It still wasn't included/accepted mainline, so it's safe to update
Looks like the BCM53012 has a similar problem to the BCM53011.
Signed-off-by: Ian Kent
---
.../171-bcm5301x-fixup-early-device-id-8012.patch | 26
.../171-bcm5301x-fixup-early-device-id-8012.patch | 26
2 files changed, 52 insertions(+)
create mod
