Ok, well I think I figured out what dd-wrt is doing with broadcom-wl, took
forever due to there being pretty much zero documentation and the whole
source tree being ridiculously confusing. Their build system for the
broadcom-wl appears to be a hybrid kernel agnostic system in which
OS-independent w
Hi,
On Wed, Sep 18, 2013 at 05:45:26AM -0500, James Hilliard wrote:
> I thought DD-WRT was only using public tarball drivers.I looked through
> their source and everything seems to match up with tarbar type wl.o files
> and so on.
Try building from their public source.
Half of the relevant bro
On 2013-09-18 12:45 PM, James Hilliard wrote:
> I thought DD-WRT was only using public tarball drivers.I looked through
> their source and everything seems to match up with tarbar type wl.o
> files and so on.
That's what the build system of the Broadcom driver generates. There's a
reason why the dr
I thought DD-WRT was only using public tarball drivers.I looked through
their source and everything seems to match up with tarbar type wl.o files
and so on.
On Wed, Sep 18, 2013 at 5:37 AM, Felix Fietkau wrote:
> On 2013-09-18 12:31 PM, James Hilliard wrote:
> > Aren't all the other router proj
On 2013-09-18 12:31 PM, James Hilliard wrote:
> Aren't all the other router projects using the broadcom-wl binary's
> generally sourced from GPL tarballs? although not necessarily the exact
> matching ones? DD-WRT and tomato all use broadcom-wl, but I think they
> use versions that are at least som
Aren't all the other router projects using the broadcom-wl binary's
generally sourced from GPL tarballs? although not necessarily the exact
matching ones? DD-WRT and tomato all use broadcom-wl, but I think they use
versions that are at least somewhat devices specific unlike OpenWRT which
seems to b
On 2013-09-17 11:45 PM, James Hilliard wrote:
> Following up on this I'm trying to figure out how broadcom-wl is set up
> in openwrt and what devices specific variables there are how those would
> be changed/determined. I'm trying to fix compatibility problems with
> this driver for a lot of broadc
Following up on this I'm trying to figure out how broadcom-wl is set up in
openwrt and what devices specific variables there are how those would be
changed/determined. I'm trying to fix compatibility problems with this
driver for a lot of broadcom devices.
On Sun, Sep 15, 2013 at 5:19 PM, James H
I thought that a number of routers could not use b43 and brcmsmac and had
to use the actual broadcom-wl driver more or less as provided by broadcom.
My email was only in reference the ones that run wl.ko like mine does(which
is what it is using right now although on shibbytomato). In the wiki it is
On 09/15/2013 05:40 PM, James Hilliard wrote:
> From what I'm seeing everyone is patching broadcom-wl around
> this(http://mirror2.openwrt.org/sources/broadcom-wl-5.100.138.tar.bz2)
> driver for the Netgear WNDR4500 for pretty much everything broadcom-wl
> related.
That is wrong!
broadcom-wl-5.10
2013/9/15 James Hilliard :
> From what I'm seeing everyone is patching broadcom-wl around
> this(http://mirror2.openwrt.org/sources/broadcom-wl-5.100.138.tar.bz2)
> driver for the Netgear WNDR4500 for pretty much everything broadcom-wl
> related. What's the point of making a bunch of patches for th
11 matches
Mail list logo
