Hi,
you should take look at the Freifunk Berlin firmware and the Gluon project:
https://github.com/freifunk-berlin/firmware
https://gluon.readthedocs.io/en/v2019.1.x/
The Freifunk Berlin firmware uses uci-defaults scripts quite a lot for setting
default configuration or changing configuration o
The url for the gdb source changed upstream.
Related ticket: https://dev.openwrt.org/ticket/20789
Signed-off-by: Philipp Borgers
---
toolchain/gdb/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolchain/gdb/Makefile b/toolchain/gdb/Makefile
index 10de1f8..d437c9a
I can test if you provide me with an image or an *easy* way to compile.
Is there any testing procedure I should follow? Do we have some kind of tests I
don't know of?
Regards
Philipp
On Thu, Feb 12, 2015 at 12:31:07PM +0100, John Crispin wrote:
> Hi,
>
> just bumped the kernel for the tl-wdr490
Someone accepted the patch in patchwork [1] but as far as I can see nobody
applied the patch. Could someone with the appropriate priveleges apply the patch
please?
Thanks a lot
Philipp
On Wed, Aug 06, 2014 at 02:09:09PM +0200, Philipp Borgers wrote:
> This change makes the profile of WDR4
Hi,
if I create a rule such as:
config rule
option in 'wireless0'
option action 'unreachable'
and have a wireless0 network configured in network and wireless config, the rule
does not show up after a network restart (/etc/init.d/network restart). E.g. ip
rule does not list the rule. If a jus
This change makes the profile of WDR4900 more consistent with other router
specific profiles.
Signed-off-by: Philipp Borgers
---
target/linux/mpc85xx/profiles/tp-link.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mpc85xx/profiles/tp-link.mk
b/target/linux
If I start from a clean setup with "make -j" e.g. a new clone of the
trunk, the patch seems to work. Otherwise it still fails.
If someone can confirm this we should close the ticket. Otherwise we
should take a look at Thomas patch.
Thanks
Philipp
On 06.12.2013 17:29, thomas.lan...@lantiq.com wro
Some people including me have a problem compiling openwrt for the ar71xx
target:
https://dev.openwrt.org/ticket/12907
Could someone more familiar with the build process have a look?
Thanks in advance!
Best Regards
Philipp
signature.asc
Description: OpenPGP digital signature
This patch adds support for all file system types as discussed earlier:
https://lists.openwrt.org/pipermail/openwrt-devel/2013-October/022109.html
This patch depends on a previous patch:
https://lists.openwrt.org/pipermail/openwrt-devel/2013-October/022111.html
Signed-off-by: Philipp Borgers
On 30.10.2013 09:28, Bruno Randolf wrote:
> On 10/30/2013 07:24 AM, Bastian Bittorf wrote:
>> [platform/au1000/sysupgrade] fix sysupgrade when changing rootfs from jffs2
>> to squashfs and visa versa
>>
>> till now only jffs2 was possible and sysupgrade refuses to change fs-type,
>> because of bad
This patch should prevent overriding of sysupgrade binaries in the bin directory
if we build images for more then one file system type.
Discussion:
https://lists.openwrt.org/pipermail/openwrt-devel/2013-October/022108.html
Signed-off-by: Philipp Borgers
---
target/linux/au1000/image/Makefile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think we should also update the Makefile for the images. As far as I
know the Makefile only creates an image for one of the rootfs types. I
can provide a patch if you don't have the time to do so.
Best Regards
Philipp
On 30.10.2013 08:24, Bastian B
Possible parameters are yes, no and adaptive. See manpage for more information.
Signed-off-by: Philipp Borgers
---
package/network/services/openvpn/files/openvpn.config | 4 ++--
package/network/services/openvpn/files/openvpn.init | 4 ++--
2 files changed, 4 insertions(+), 4 deletions
This will hopefully fix jffs2 support for target system rmi/amd au1x00,
subtarget Au1500 and Target Profile T-Mobile InternetBox. Tested on same
configuration. Related ticket: https://dev.openwrt.org/ticket/8058
Signed-off-by: Philipp Borgers
>From 5ec2b5febd58a391fac6aeb7508e08a251a2be92
Perhaps just use the description field for this kind of stuff or add
something like NON_FREE=yes? Plain and easy...
> > For non-free packages, would something like
> > DEPENDS=-LIBRE
> > work?
>
> > If CONFIG_LIBRE is defined, these packages would simply disappear from the
> > menu.
>
> That's
I think this is no solution or not the whole solution. Sorry :)
r...@openwrt:/# lspci
00:00.0 SERCOS interface: Device 0057:1800 (rev 02)
00:01.0 Non-VGA unclassified device: Device 2800:4085 (rev 02)
00:02.0 Non-VGA unclassified device: Device 0002: (rev 02)
00:03.0 Non-VGA unclassified d
16 matches
Mail list logo