On Fri, 2015-08-21 at 20:17 +0200, Hauke Mehrtens wrote:
>
> On 08/16/2015 06:19 AM, Ian Kent wrote:
> > On Tue, 2015-06-23 at 07:58 +0800, Ian Kent wrote:
> >> On Mon, 2015-06-22 at 18:42 +0200, Hauke Mehrtens wrote:
> >>>
> >>> On 03/10/2015 04:30
On Tue, 2015-06-23 at 07:58 +0800, Ian Kent wrote:
> On Mon, 2015-06-22 at 18:42 +0200, Hauke Mehrtens wrote:
> >
> > On 03/10/2015 04:30 AM, Ian Kent wrote:
> > > The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
> > > it isn't configured
On Sat, 2015-08-15 at 09:55 +0800, Ian Kent wrote:
> On Fri, 2015-08-14 at 19:55 +0200, Hauke Mehrtens wrote:
> > On 08/14/2015 06:03 AM, Ian Kent wrote:
> > > On Wed, 2015-08-12 at 22:01 +0200, Hauke Mehrtens wrote:
> > >> On 07/15/2015 12:11 PM, Ian Kent wrote:
&g
On Sat, 2015-08-15 at 09:55 +0800, Ian Kent wrote:
> On Fri, 2015-08-14 at 19:55 +0200, Hauke Mehrtens wrote:
> > On 08/14/2015 06:03 AM, Ian Kent wrote:
> > > On Wed, 2015-08-12 at 22:01 +0200, Hauke Mehrtens wrote:
> > >> On 07/15/2015 12:11 PM, Ian Kent wrote:
&g
On Fri, 2015-08-14 at 19:55 +0200, Hauke Mehrtens wrote:
> On 08/14/2015 06:03 AM, Ian Kent wrote:
> > On Wed, 2015-08-12 at 22:01 +0200, Hauke Mehrtens wrote:
> >> On 07/15/2015 12:11 PM, Ian Kent wrote:
> >>> On Tue, 2015-07-14 at 18:19 +0200, Rafał Miłecki wrote:
&
On Wed, 2015-08-12 at 22:01 +0200, Hauke Mehrtens wrote:
> On 07/15/2015 12:11 PM, Ian Kent wrote:
> > On Tue, 2015-07-14 at 18:19 +0200, Rafał Miłecki wrote:
> >> On 28 June 2015 at 05:37, Ian Kent wrote:
> >>> Let me rework this using the bus number as you r
On Tue, 2015-07-14 at 18:19 +0200, Rafał Miłecki wrote:
> On 28 June 2015 at 05:37, Ian Kent wrote:
> > Let me rework this using the bus number as you recommend.
> > I'll repost my updated patch series once I've done that.
>
> Hi Ian,
>
> Is there any chanc
On Tue, 2015-06-23 at 07:58 +0800, Ian Kent wrote:
> On Mon, 2015-06-22 at 18:42 +0200, Hauke Mehrtens wrote:
> >
> > On 03/10/2015 04:30 AM, Ian Kent wrote:
> > > The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
> > > it isn't configured
On Mon, 2015-06-22 at 18:42 +0200, Hauke Mehrtens wrote:
>
> On 03/10/2015 04:30 AM, Ian Kent wrote:
> > The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
> > it isn't configured during the bus scan the PCI layer goes crazy
> > trying to configure ph
On Sun, 2015-06-21 at 19:19 +0200, Rafał Miłecki wrote:
> On 10 March 2015 at 04:30, Ian Kent wrote:
> > The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
> > it isn't configured during the bus scan the PCI layer goes crazy
> > trying to configure phantom
On Wed, 2015-05-27 at 22:32 +0200, Rafał Miłecki wrote:
> Hi,
>
> With few recent commits OpenWrt can now generate Asus-specific TRX
> files for brcm47xx and bcm53xx. The magic is about some extra data at
> the end of TRX (so the format differs a bit, even it using the same
> file extension and la
On Wed, 2015-05-13 at 06:34 +0200, Rafał Miłecki wrote:
> On 13 May 2015 at 03:49, Ian Kent wrote:
> > On Tue, 2015-05-12 at 19:31 +0200, Rafał Miłecki wrote:
> >> On 12 May 2015 at 15:10, Hante Meuleman wrote:
> >> > Added two functions to the bcm47xx_nvram mo
On Tue, 2015-05-12 at 19:31 +0200, Rafał Miłecki wrote:
> On 12 May 2015 at 15:10, Hante Meuleman wrote:
> > Added two functions to the bcm47xx_nvram module to get and release copies
> > of the complete nvram contents. This can be used by for example brcmfmac
> > to get complete nvram contents whi
Message-
> From: Rafał Miłecki [mailto:zaj...@gmail.com]
> Sent: vrijdag 24 april 2015 14:08
> To: Hante Meuleman
> Cc: Ian Kent; Arend Van Spriel; Jonas Gorski; mailinglist
> Subject: Re: [OpenWrt-Devel] Fwd: Re: [PATCH 10/10] brcmfmac: Add support for
> multiple PCIE devi
's more annoying is doing the heavy lifting in b53 to setup the
> switch to use port 8 for the cpu, the way the Broadcom source does,
> doesn't work so I'm missing something with that for sure.
>
> So we do need to stick to using port 5 for the cpu consistently
>
source does,
> doesn't work so I'm missing something with that for sure.
>
> So we do need to stick to using port 5 for the cpu consistently
> throughout for now.
>
> >
> > Regards,
> > Hante
> >
> > -Original Message-
> > From:
> Hante
>
> -Original Message-----
> From: Hante Meuleman
> Sent: woensdag 22 april 2015 13:45
> To: 'Ian Kent'; Arend Van Spriel
> Cc: 'Jonas Gorski'; 'mailinglist'
> Subject: RE: [OpenWrt-Devel] Fwd: Re: [PATCH 10/10] brcmfmac: Add support fo
to use port 8 for the cpu, the way the Broadcom source does,
doesn't work so I'm missing something with that for sure.
So we do need to stick to using port 5 for the cpu consistently
throughout for now.
>
> Regards,
> Hante
>
> -Original Message-
> From: Hante
On Mon, 2015-04-20 at 19:28 +0200, Arend van Spriel wrote:
> On 04/20/15 13:50, Jonas Gorski wrote:
> > Hi,
> >
> > On Mon, Apr 20, 2015 at 1:29 PM, Rafał Miłecki wrote:
> >> On 20 April 2015 at 11:27, Arend van Spriel wrote:
> Following an "nvram erase" none of the needed pairs remain
> >
On Mon, 2015-04-20 at 18:40 +0800, Ian Kent wrote:
> On Mon, 2015-04-20 at 18:26 +0800, Ian Kent wrote:
> > On Mon, 2015-04-20 at 11:27 +0200, Arend van Spriel wrote:
> > > On 04/20/15 03:00, Ian Kent wrote:
> > > > On Fri, 2015-04-17 at 10:55 +0200, Arend van Sprie
On Mon, 2015-04-20 at 18:26 +0800, Ian Kent wrote:
> On Mon, 2015-04-20 at 11:27 +0200, Arend van Spriel wrote:
> > On 04/20/15 03:00, Ian Kent wrote:
> > > On Fri, 2015-04-17 at 10:55 +0200, Arend van Spriel wrote:
> > >> Resend as it bounced on openwrt-devel list.
&
On Mon, 2015-04-20 at 11:27 +0200, Arend van Spriel wrote:
> On 04/20/15 03:00, Ian Kent wrote:
> > On Fri, 2015-04-17 at 10:55 +0200, Arend van Spriel wrote:
> >> Resend as it bounced on openwrt-devel list.
> >>
> >> Original Message
> >
On Fri, 2015-04-17 at 10:55 +0200, Arend van Spriel wrote:
> Resend as it bounced on openwrt-devel list.
>
> Original Message
> Subject: Re: [PATCH 10/10] brcmfmac: Add support for multiple PCIE
> devices in nvram.
> Date: Fri, 17 Apr 2015 10:50:08 +0200
> From: Arend van Spriel
On Wed, 2015-04-15 at 09:01 +0200, Rafał Miłecki wrote:
> On 15 April 2015 at 07:37, Ian Kent wrote:
> > On Sun, 2015-04-12 at 19:01 +0200, Rafał Miłecki wrote:
> >> Newer revisions (5+) of BCM53011 and probably all revs of BCM53012
> >> require overriding CPU p
On Sun, 2015-04-12 at 19:01 +0200, Rafał Miłecki wrote:
> Newer revisions (5+) of BCM53011 and probably all revs of BCM53012
> require overriding CPU port to work. So far we were handling it only for
> CPU port 8, but some devices may use e.g. port 5. In such case we need
> to use recently defined
On Thu, 2015-04-02 at 17:47 +0800, Ian Kent wrote:
> On Thu, 2015-04-02 at 09:45 +0200, Rafał Miłecki wrote:
> > On 10 March 2015 at 04:30, Ian Kent wrote:
> > > The R8000 nvram is larger than 32k, increase nvram allocation to
> > > 64k to accomadate.
> >
>
On Thu, 2015-04-02 at 09:45 +0200, Rafał Miłecki wrote:
> On 10 March 2015 at 04:30, Ian Kent wrote:
> > The R8000 nvram is larger than 32k, increase nvram allocation to
> > 64k to accomadate.
>
> I handled this by sending nvram.c patch for mainline:
> http://patchwork.l
On Thu, 2015-04-02 at 10:22 +0200, Rafał Miłecki wrote:
> Hi Ian,
>
> On 10 March 2015 at 04:30, Ian Kent wrote:
> > Add new sprom revision 11 variables to the nvram -> sprom reader.
> >
> > Signed-off-by: Ian Kent
>
> There are few problems with bcm53xx&#
On Thu, 2015-03-19 at 19:32 -0600, Pat Fruth wrote:
> > On Mar 18, 2015, at 10:05 PM, Ian Kent wrote:
> >
> > On Wed, 2015-03-18 at 21:40 -0600, Pat Fruth wrote:
> >> This patch addresses an issue specific to Apple devices experiencing a
> >> wireless disc
On Thu, 2015-03-19 at 12:05 +0800, Ian Kent wrote:
> On Wed, 2015-03-18 at 21:40 -0600, Pat Fruth wrote:
> > This patch addresses an issue specific to Apple devices experiencing a
> > wireless disconnect when trying to associate with either 2.4Ghz or 5Ghz
> > wifi of a Lin
On Wed, 2015-03-18 at 21:40 -0600, Pat Fruth wrote:
> This patch addresses an issue specific to Apple devices experiencing a
> wireless disconnect when trying to associate with either 2.4Ghz or 5Ghz wifi
> of a Linksys WRT1900AC router.
> Apple devices (MacBooks running Mac OS X 10.10.x Yosemite
On Sat, 2015-02-28 at 23:07 +0800, Ian Kent wrote:
> Hi all,
>
> I'm trying to make progress on getting the Netgear R8000 to work.
> Basically it's a BCM4799 but with a BCM53012 switch rather than the
> usual BCM53011 (among other differences).
>
> I have a number
On Tue, 2015-03-10 at 12:55 +0100, Rafał Miłecki wrote:
> On 10 March 2015 at 12:29, Jonas Gorski wrote:
> > On Tue, Mar 10, 2015 at 4:30 AM, Ian Kent wrote:
> >> [OpenWrt-Devel] [PATCH 0/6] bcm53xx: changes for R8000 so far
> >
> > Ah, this is supposed to be the V
On Tue, 2015-03-10 at 12:26 +0100, Jonas Gorski wrote:
> On Tue, Mar 10, 2015 at 4:30 AM, Ian Kent wrote:
> > After a vendor firmware install the values seen in nvram for et0macaddr
> > and et1macaddr are that of nvram macaddr and nvram macaddr+1.
> >
> > So
On Tue, 2015-03-10 at 12:17 +0100, Jonas Gorski wrote:
> On Tue, Mar 10, 2015 at 4:25 AM, Ian Kent wrote:
> > The following series implements...
>
> If you don't have anything nice to say, ... ;) (i.e. you should drop
> the cover letter if it does not contain anything us
The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
it isn't configured during the bus scan the PCI layer goes crazy
trying to configure phantom devices.
Signed-off-by: Ian Kent
---
.../172-bcm5301x-R8000-handle-PEX8603-switch.patch | 225
.../172-bcm
After a vendor firmware install the values seen in nvram for et0macaddr
and et1macaddr are that of nvram macaddr and nvram macaddr+1.
So set them that way here too.
Signed-off-by: Ian Kent
---
...53xx-deal-with-R8000-mac-address-settings.patch | 83
...53xx-deal-with
The R8000 nvram is larger than 32k, increase nvram allocation to
64k to accomadate.
Signed-off-by: Ian Kent
---
...3xx-increase-nvram-allocation-size-to-64k.patch | 19 +++
...3xx-increase-nvram-allocation-size-to-64k.patch | 20
2 files changed, 39
Add new sprom revision 11 variables to the nvram -> sprom reader.
Signed-off-by: Ian Kent
---
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 426
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 432
2 files changed, 858 inserti
Fix thinko' in the bcm47xx sprom driver.
Signed-off-by: Ian Kent
---
.../bcm53xx/files/drivers/misc/bcm47xx-sprom.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/bcm53xx/files/drivers/misc/bcm47xx-sprom.c
b/target/linux/bcm53xx/files/drivers
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
Rather than struggle working out what needs what I thought it better
to update and resend with the few changes you recommended so we can
work from there.
---
Ian Kent (6):
bcm53xx: fixup early device id 8012
bcm53xx: fix typo in bcm47xx sprom driver
bcm53xx: update sprom from
The following series implements...
---
Ian Kent (6):
bcm53xx: fixup early device id 8012
bcm53xx: fix typo in bcm47xx sprom driver
bcm53xx: update sprom from nvram to handle rev 11
bcm53xx - increase nvram allocation size to 64k
bcm53xx: deal with R8000 mac address
On Mon, 2015-03-09 at 10:28 +0100, Rafał Miłecki wrote:
> On 9 March 2015 at 10:21, Rafał Miłecki wrote:
> > On 9 March 2015 at 10:08, Ian Kent wrote:
> >> Here are some changes done while working to get the R8000 working.
> >> Some are straight forward while some req
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-PCIe
x/patches-3.18/172-bcm5301x-R8000-handle-PEX8603-switch.patch
new file mode 100644
index 000..e321845
--- /dev/null
+++
b/target/linux/bcm53xx/patches-3.18/172-bcm5301x-R8000-handle-PEX8603-switch.patch
@@ -0,0 +1,225 @@
+bcm5301x - R8000 handle PEX8603 switch
+
+The Netgear R8000 has a
After a vendor firmware install the values seen in nvram for et0macaddr
and et1macaddr are that of nvram macaddr and nvram macaddr+1.
So set them that way here too.
Signed-off-by: Ian Kent
---
...53xx-deal-with-R8000-mac-address-settings.patch | 83
...53xx-deal-with
nvram allocation size to 64k
+
+The R8000 nvram is too large for the 32k allocation size in
+bcm47xx_nvram.c.
+
+Increase the allocation size to 64k.
+
+Signed-off-by: Ian Kent
+--- a/drivers/firmware/broadcom/bcm47xx_nvram.c
b/drivers/firmware/broadcom/bcm47xx_nvram.c
+@@ -20,7 +20,7
Add new sprom revision 11 variables to the nvram -> sprom reader.
Signed-off-by: Ian Kent
---
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 426
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 432
2 files changed, 858 inserti
Fix thinko' in the bcm47xx sprom driver.
Signed-off-by: Ian Kent
---
.../bcm53xx/files/drivers/misc/bcm47xx-sprom.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/bcm53xx/files/drivers/misc/bcm47xx-sprom.c
b/target/linux/bcm53xx/files/drivers
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
s way for production cost reasons since it probably
could have benn done in a more sensible way (such as using the
unused PCIe device).
Anyway, feedback welcome.
---
Ian Kent (6):
bcm53xx - fixup early device id 8012
bcm53xx - fix typo in bcm47xx sprom driver
bcm53xx - update
On Wed, 2015-03-04 at 10:29 +, Conor O'Gorman wrote:
> On 04/03/15 05:29, Ian Kent wrote:
> > On Sat, 2015-02-28 at 23:07 +0800, Ian Kent wrote:
> >> The only things I can say for sure are, packets sent are seen by the
> >> bgmac driver and the driver gets a tra
On Sat, 2015-02-28 at 23:07 +0800, Ian Kent wrote:
> Hi all,
>
> I'm trying to make progress on getting the Netgear R8000 to work.
> Basically it's a BCM4799 but with a BCM53012 switch rather than the
> usual BCM53011 (among other differences).
Obviously that's a
Hi all,
I'm trying to make progress on getting the Netgear R8000 to work. Basically
it's a BCM4799 but with a BCM53012 switch rather than the usual BCM53011 (among
other differences).
I have a number of problems but the one that is the most concerning is that
Ethernet doesn't work.
Now, this
On Mon, 2015-01-12 at 19:03 -0800, David Lin wrote:
> Hi Ian,
>
> 1. I will take off these additional blank lines.
> 2. I work for problems reported from community. If you do find problems
> for the driver, please let me know.
Hi David,
I was disappointed to find that client mode wi
suitable integer that enables the logging
required. But that's another story.
This change is meant to avoid the firmware loading problem if anyone
does use the logging, and that's all.
Signed-off-by: Ian Kent
---
...nt-break-fw-upload-timing-with-log-prints.patch | 82 ++
have experience with device
drivers since file systems are more my area, actually more the VFS than
anything, necessarily, as I'm the autofs maintainer, ;)
>
> Thanks
> David
>
> -Original Message-
> From: Ian Kent [mailto:ra...@themaw.net]
> Sent: Tuesday, Januar
Hi David,
Please forgive the top posting.
I don't think that the kernel programming style guidelines recommend
against it and I also don't know if checkpatch.pl will complain about it
but personally I find the additional blank lines in things like the
below actually make the code harder to read:
On Thu, 2015-01-08 at 14:36 -0200, Fernando Frediani wrote:
> Hi all,
>
> Does anyone here have a Linksys WRT1900AC (that fiasco that suppose to
> be the new generation of WRT54G) ?
Yes and I like it.
As Imre Kaloz says Marvel recently released updated driver source.
It seems to me the major h
60 matches
Mail list logo
