On 2013-11-02 23:47, James Hilliard wrote:
I'm not actually trying to use a fully compiled .ko file, the file is a
.o file such as wl_apsta.o(tools indicate it is a relocatable ELF for
ARM) that gets compiled into a .ko when you build GPL tarballs. Seems to
be the same as the wl_prebuilt.o
Something interesting I found, seems broadcom is building the driver in
this strange way precisely because of the GPL:
/* Where to get the declarations for mem, str, printf, bcopy's? Two basic
approaches.
*
* First, use the Linux header files and the C standard library
replacmenent versions
*
On 2013-11-02 00:30, James Hilliard wrote:
It's a very confusing way of building a package, but the reason seems to
come down to how the GPL works. The GPL prohibits statically linking any
closed source packages into the kernel, that however is how drivers are
often built. Broadcom came up
Well, maybe they didn't create the shared code because of the GPL but they
can't link a binary directly to a GPL component, only a LGPL component I
think or something like that. I've object dumped and ran decompilers on
the broadcom-wl object files and I don't see anything statically linked or
On 2013-11-02 08:59, James Hilliard wrote:
Well, maybe they didn't create the shared code because of the GPL but
they can't link a binary directly to a GPL component, only a LGPL
component I think or something like that. I've object dumped and ran
decompilers on the broadcom-wl object files
I'm not actually trying to use a fully compiled .ko file, the file is a .o
file such as wl_apsta.o(tools indicate it is a relocatable ELF for ARM)
that gets compiled into a .ko when you build GPL tarballs. Seems to be the
same as the wl_prebuilt.o files we have for the most part in the current
I noticed that there is a broadcom ARM build option but it only seems to
build for the r6250 and I'm not sure if its actually making installable
builds. I have a number of very large patches that are part of the build
system for these routers. Has anyone been working on these recently? The
On 11/01/2013 01:22 PM, James Hilliard wrote:
I noticed that there is a broadcom ARM build option but it only seems to
build for the r6250 and I'm not sure if its actually making installable
builds. I have a number of very large patches that are part of the build
system for these routers. Has
From what I can tell the way the openwrt broadcom-wl is compiled makes it
extremely difficult to patch in any upstream changes from broadcom. The
broadcom-wl binary module distributed with stock routers does not appear to
be kernel version specific since it is not statically linked, however it is
It's a very confusing way of building a package, but the reason seems to
come down to how the GPL works. The GPL prohibits statically linking any
closed source packages into the kernel, that however is how drivers are
often built. Broadcom came up with another way that gets around the problem
by
10 matches
Mail list logo
