Hello,
We use our own kernel source (official linux 3.8.13 plus a drivers) and build
openwrt for x86 and powerpc 85xx.
Now the modules generated for powerpc don't load. When trying to insmod, then
the kernel message (e.g.)
xt_LOG: no symbol version for module_layout
is issued on the console.
On Fri, Mar 07, 2014 at 06:37:43PM +0100, Felix Fietkau wrote:
> On 2014-03-07 16:40, Hannu Nyman wrote:
> > So far I have not seen any response from the devs, which is a bit
> > disappointing :-(
> >
> > In any case, I thought to add that apparently 3.12 has been named a
> > "long-term kernel"
Ok, I didn't imagine better title for this curious bug, don't think this is an
arecord problem, it might be
a deeper problem in Openwrt.
Scenario: USB sound card installed in a MIPS BE router (bcm63xx), using OHCI
module, alsa-utils installed. Let's make
some recordings with arecord.
arecord -q
Interface state needs to be set in teardown state before launching an interface
event otherwise the up state will be reported as true in the ubus interface
notify message
Signed-off-by: Hans Dedecker
---
interface.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a
Reapply bridge mtu setting as adding a bridge member will override the bridge
mtu in the kernel
Signed-off-by: Hans Dedecker
---
bridge.c | 13 +++--
device.c |2 +-
interface.c|2 +-
system-dummy.c |2 +-
system-linux.c | 15 +--
system.h
Interface metric needs to be assigned to the route metric parameter at route
creation time. Otherwise if the interface metric is different from 0 route_cmp
will wrongly conclude the routes are different.
In this case the route will be added/deleted and could end up with the route
missing in the
From: Karl Palsson
No functional change. The difference in the md5sum of the tarball is
the inclusion of a .gitignore file in the github provided tarball.
This change allows https://home.comcast.net/~sdwalker/uscan/index.html
to more accurately track the state of this package, and includes link
On Fri, Mar 7, 2014 at 11:34 AM, Rafał Miłecki wrote:
> If you don't have any access to specs, it may be hard. Do you have any
> plan how to develop a driver? Some kind of RE?
I don’t have any specs and I don’t have prior driver developing
experience :( The only thing I have are the WiFi card and
Add support for Astoria ARV7519RW.
These patches add support for the Astoria ARV7519RW aka Livebox 2.1
The PCI and PCIe interfaces have been disabled. Also, because there are
two revisions of this board with differen GPHY firmwares, two targets
were defined.
Signed off by: Esteban Benito
Signed
