On 01.05.2013 01:21, Jonh Wendell wrote:
didn't try the patch, but I'm all for it, as it fixes a really annoying
behavior.
2013/4/30 Sergey Ryazanov ryazanov@gmail.com
mailto:ryazanov@gmail.com
Reducing entropy of configuration file, which is introduced by find
making the patch, I've read https://dev.openwrt.org/ticket/6992
I decided to go CamelCase to keep the current style and let the change
happen when that bug is fixed.
makes sense?
2012/9/6 Matthias Buecher / Germany m...@maddes.net
mailto:m...@maddes.net
Please use lowercase options
Signed-off by: Matthias Buecher m...@maddes.net
- - - -
Setting the trx header flags can be very useful, for instance when
reverting/switching from DD-Wrt to OpenWrt.
It can emulate DD-Wrt's -noheader option with -c 1, so the image can be
flashed correctly, e.g. on Buffalo WZR-HP-G300NH with
A) Use `sort -u` instead of just `uniq`
B) First add kernel packages alphabetically sorted, then all others
alphabetically sorted.
This allows other packages to override kernel configs if necessary.
Note: If find has no action for matches then also pruned folders are included
in the result
* Creation of uImage for WNR854T only done once (before 2x for jffs2
build and 1x for squashfs build)
* Got rid of unneccessary padding of rootfs partition
* ARM zImages always need a machine id, therefore do not copy generic
(=no id) uImage to BIN_DIR, instead copy zImage
* Generalized functions
http://patchwork.openwrt.org/patch/2046/
On 06.04.2012 18:31, Matthias Buecher / Germany wrote:
Add an image option for the Orion Generic targets, that allows to
specify the kernel mtd partition size.
The option takes care for necessary size extension when building with
symbols.
The value
On 07.04.2012 20:28, Imre Kaloz wrote:
On Fri, 06 Apr 2012 18:31:13 +0200, Matthias Buecher / Germany
m...@maddes.net wrote:
Add an image option for the Orion Generic targets, that allows to
specify the kernel mtd partition size.
The option takes care for necessary size extension when
Add an image option for the Orion Generic targets, that allows to
specify the kernel mtd partition size.
The option takes care for necessary size extension when building with
symbols.
The value is also used for image generation (padding).
Plus:
- creation of ARM uImage generalized in image
On 23.02.2012 19:21, John Crispin wrote:
On 23/02/12 19:19, Christoph Thielecke wrote:
Hello,
after got this device I'm just wonder a little bit why there is no image for
flashing from original dd-wrt web interface. It should not hard to build
this
bin file (as for brcm47xx).
It would
On 23.01.2012 20:33, Felix Fietkau wrote:
As you've probably noticed, we've had issues keeping up with the
workload of incoming patches.
There is quite a bit of work involved in taking care of incoming
patches, not just review. Patches need to be compile tested, ideally
also runtime tested,
Who is actively responsible for the Orion targets?
(Kaloz did not react on my mails in December.)
Maddes
On 16.12.2011 20:03, Matthias Buecher / Germany wrote:
http://patchwork.openwrt.org/patch/1646/
On 04.12.2011 20:52, Matthias Buecher / Germany wrote:
Signed-off-by: Matthias Bücher m
Is anybody so kind and can commit this patch.
http://patchwork.openwrt.org/patch/1645/
Thanks
Maddes
On 04.12.2011 20:52, Matthias Buecher / Germany wrote:
Signed-off-by: Matthias Bücher m...@maddes.net
Patch is attached and inline for comments
Regards
Maddes
Index: tools
Is anybody so kind and can commit this patch too.
http://patchwork.openwrt.org/patch/1645/
Thanks
Maddes
On 04.12.2011 20:21, Matthias Buecher / Germany wrote:
Signed-off-by: Matthias Bücher m...@maddes.net
Patch is attached and inline for comments
Regards
Maddes
Index: target
Correction:
http://patchwork.openwrt.org/patch/1646/
On 16.12.2011 20:01, Matthias Buecher / Germany wrote:
Is anybody so kind and can commit this patch.
http://patchwork.openwrt.org/patch/1645/
Thanks
Maddes
On 04.12.2011 20:52, Matthias Buecher / Germany wrote:
Signed-off-by: Matthias
Signed-off-by: Matthias Bücher m...@maddes.net
Patch is attached and inline for comments
Regards
Maddes
Index: target/linux/orion/generic/base-files/lib/upgrade/platform.sh
===
---
Signed-off-by: Matthias Bücher m...@maddes.net
Patch is attached and inline for comments
Regards
Maddes
Index: tools/wrt350nv2-builder/Makefile
===
--- tools/wrt350nv2-builder/Makefile(revision 29422)
+++
This patch is a complete overhaul of the image makefile for the Orion
generic target.[BR] Code is written in a way that it can be reused
several times in the image file, but can also be easily adopted to other
targets (BuildKernel, Sysupgrade image, etc.).[BR] Only working images
are generated,
Hello OpenWrt developers,
this is a cross-platform issue where I need your expertise.
As I build for Orion with kernel symbols the kernel is normally bigger
than the 1MB mtd partition.
That's why I'm interested in having support for flexible kernel sizes.
This would also allow people to reduce
On 20.09.2011 01:02, Patrick Florek wrote:
I just compiled a new Firmware for the Marvell Orion Generic Platform
(wrt350n v2). I build it with the standard config and failed on
creation of the firmware image. Error is that the kernel size is
bigger than his space in the filesystem.
-05 at 22:47 +0200, Matthias Buecher / Germany wrote:
Thanks Maarten, now kernel compiles again.
One of your patches had a typo (COFIG instead of CONFIG), corrected it
and recreated it for the latest trunk revision.
You're welcome, as I said I experienced similar problems just before you
did
The attached patch will bump the wing package to a more current version.
This version has less compile issues and solves ticket #9722 [1].
Signed by: Matthias Buecher mail at maddes.net
Thanks to Roberto Riggio for this help.
[1] https://dev.openwrt.org/ticket/9722
Index: net/wing/Makefile
A current log and error description is available in ticket #9017 [1]
Thanks in advance
Maddes
[1] https://dev.openwrt.org/ticket/9017
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi everybody,
I'm unable to resolve the dependencies for package perf in trunk, also
`make menuconfig` throws errors about the perf package.
Detailed log is available in ticket #9696 [1] .
Regards
Maddes
[1] https://dev.openwrt.org/ticket/9696
___
On 06.07.2011 11:54, Maarten Bezemer wrote:
On Tue, 2011-07-05 at 22:47 +0200, Matthias Buecher / Germany wrote:
Thanks Maarten, now kernel compiles again.
One of your patches had a typo (COFIG instead of CONFIG), corrected it
and recreated it for the latest trunk revision.
You're welcome
On 06.07.2011 21:09, John Crispin wrote:
On 06/07/11 20:32, Matthias Buecher / Germany wrote:
On 06.07.2011 11:54, Maarten Bezemer wrote:
On Tue, 2011-07-05 at 22:47 +0200, Matthias Buecher / Germany wrote:
Thanks Maarten, now kernel compiles again.
One of your patches had a typo (COFIG
On 06.07.2011 11:54, Maarten Bezemer wrote:
On Tue, 2011-07-05 at 22:47 +0200, Matthias Buecher / Germany wrote:
Thanks Maarten, now kernel compiles again.
One of your patches had a typo (COFIG instead of CONFIG), corrected it
and recreated it for the latest trunk revision.
You're welcome
without problems
when kmod-mv-cesa is selected
Greetings,
Maarten
On Mon, 2011-07-04 at 20:24 +0200, Matthias Buecher / Germany wrote:
Hi everybody,
I just got back to OpenWrt development after 6 months and recognized
that the Orion platform doesn't build anymore.
According to ticket
On 06.07.2011 00:38, Luca Olivetti wrote:
Al 05/07/11 22:47, En/na Matthias Buecher / Germany ha escrit:
But now I run into another issue with ltq-tapi:
Unsurprisingly, since, AFAIK, that's only meant for lantiq hardware,
so you should deselect it.
Did you select it in make menuconfig
Hi everybody,
I just got back to OpenWrt development after 6 months and recognized
that the Orion platform doesn't build anymore.
According to ticket #9209 [1] this happened ~3 months ago.
Can anybody please help, so I can continue developing some packages for
my platform.
Thanks in advance
solution just like it
is done in the kernel source
Maddes
[1] https://dev.openwrt.org/changeset/25090
[2]
https://dev.openwrt.org/attachment/ticket/8241/orion_dt2_2.6.37.2.patch
On 21.01.2011 19:11, Matthias Buecher / Germany wrote:
Anyone please?
Maddes
On 07.01.2011 00:44, Matthias
On 21.01.2011 19:11, Matthias Buecher / Germany wrote:
Anyone please?
Maddes
On 07.01.2011 00:44, Matthias Buecher / Germany wrote:
Hi developers,
can someone please commit the patch of ticket #8241 [1] to trunk.
The patch is needed to compile Orion with new kernel release 2.6.37.
Tried
Hi developers,
can someone please commit the patch of ticket #8241 [1] to trunk.
The patch is needed to compile Orion with new kernel release 2.6.37.
Tried to contact Imre several times but got no reply.
The patch is very simple, easy to review and keeps backward compatibility.
Thanks in advance
Hi there,
can please somebody commit ticket #8324 [1].
It removes unnecessary parts from the patches, which is already inside
the kernel source at a different location.
Additionally it tidies them up in a big way.
Thanks
Maddes
[1] https://dev.openwrt.org/ticket/8324
Hi there,
when building all packages on trunk then kernel compilation stops.
Created ticket #8384 [1] for this error.
Maddes
[1] https://dev.openwrt.org/ticket/8384
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Not necessary.
2.6.36.1 compiles fine with the current patches/ (which is for the
current kernel).
The patches-2.6.32/ is to compile trunk with the Backfire kernel.
Maddes
On 25.11.2010 21:29, Michael Kämmerer wrote:
In present trunk (r24146) for target orion, patchfiles reside in dir
patches
Inline is better for commenting the patch, as the comment can be placed
directly at the discussed location.
But a mangled patch is hard to apply.
If it is attached it normally doesn't get mangled, but then commenting
is harder as the relevant code is not shown.
So if you are sure that the patch
On 22.11.2010 09:35, Stefan Tomanek wrote:
Dies schrieb Matthias Buecher / Germany (m...@maddes.net):
So if you are sure that the patch is not mangled by your mail client (no
wraps, no tabs to spaces), then inline is definitely preferred.
Maybe setting some options in your mail client
Had some minutes before I leave, attached is the 089 rebasement patch.
Maddes
On 13.11.2010 09:19, Matthias Buecher / Germany wrote:
I think generic patch 089 must be rebased when 014 is removed.
Maddes
On 12.11.2010 18:14, Guillaume LECERF wrote:
Signed-off-by: Guillaume LECERF glec
Generic 014 is also something I'm currently working on, and it is not
really obsolete.
The printk() definitely helps to identify hardware, especially not
supported one.
The other changes help developers to find the correct spots for
enhancements.
You may remove the blocks with the comments, but
On 12.11.2010 21:33, Guillaume LECERF wrote:
2010/11/12 Matthias Buecher / Germany m...@maddes.net:
Generic 014 is also something I'm currently working on, and it is not
really obsolete.
The printk() definitely helps to identify hardware, especially not
supported one.
The other changes help
/compilelog.orion_generic.release-luci+ipv6.23900M.20101106_215019.log
Regards
Maddes
On 07.11.2010 00:25, Matthias Buecher / Germany wrote:
Hello everybody,
I experienced a weird problem when upgrading the Orion platform to
kernel 2.6.35:
Several packages are not build although
It turned out that the package kmod-pppol2tp doesn't compile with
2.6.35 on any platform.
So I create a defect ticket for it: #8195.
https://dev.openwrt.org/ticket/8195
Maddes
On 07.11.2010 15:06, Matthias Buecher / Germany wrote:
I found the problematic section:
mkdir -p /home/maddes/openwrt
Hello everybody,
I experienced a weird problem when upgrading the Orion platform to
kernel 2.6.35:
Several packages are not build although they are selected in `make
menuconfig`.
I assume that the build system is not setting all necessary configs for
2.6.35 and maybe later.
Or must be something
On 03.11.2010 15:50, Luka Perkov wrote:
On Sun, Oct 31, 2010 at 05:46:23PM +0100, Matthias Buecher / Germany wrote:
also had a look at other targets yesterday, and the adm5120 platform
has subtarget dependent image make files (just a simple include
$(SUBTARGET).mk) and even Profile dependent
:33, Imre Kaloz wrote:
Hi,
On Thu, 28 Oct 2010 00:48:16 +0200, Matthias Buecher / Germany
m...@maddes.net wrote:
I want to transfer the Orion platform from subtargets to profiles.
Is there a possibility to have a separated image makefile for each
profile?
Example:
For profiles/100
Hi there,
I want to transfer the Orion platform from subtargets to profiles.
Is there a possibility to have a separated image makefile for each profile?
Example:
For profiles/100-wrt350nv2.mk with define Profile/WRT350Nv2 I would
like to use image/100-wrt350nv2.mk (or image/WRT350Nv2.mk).
If the
On a squashfs image just call firstboot and your router will be like
it has just been flashed.
Maddes
On 24.09.2010 20:21, Lukáš Macura wrote:
Hello to all,
please, we are working with asus wl-500gp and backfire on it. We need to
write script which will reset device to factory defaults. I
Hi there,
I had the need to bind one Dropbear instance to multiple ports, so I
copied the latest Dropbear init script from Trunk onto my Backfire
10.03.1-rc2 installation.
When checking the script's functionality I recognized that r20960 [1]
for ticket #7149 [2] allowed to enter an ip address,
Hello OpenWrt team,
is it planned to update Busybox for 10.03.1?
Maddes
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Just read this thread today and want to mention, that if you run into
build problems you should issue a make distclean (not dirclean) to get
rid of all old stuff and extra packages (create patches of your manual
changes first, so you can later re-apply them).
Remember that trunk is ongoing
If awk of Busybox has a range limit issue, then try calculating in the
shell itself:
echo $(( `echo 255.255.255.255 | awk -F\. '{printf (%i*256*256*256)
+ (%i*256*256) + (%i*256) + (%i), $1, $2, $3, $4}'` ))
Awk creates the formular, while ash calculates it via $((
Maddes
On 15.07.2010
Just saw r22145 and was wondering why this has been changed.
What if 2.8 changes again the suffix? Re-replace everything?
If someone is still compiling 2.4 for any reason with latest trunk he
will have problems (lots of manual changes).
I think the previous situation was a good general solution
Updates MD5SUM of kernel 2.6.35 to RC3.
Signed off by: Matthias Buecher m...@maddes.net
Index: include/kernel-version.mk
===
--- include/kernel-version.mk (revision 21899)
+++ include/kernel-version.mk (working copy)
@@ -26,8 +26,8
trunk/target/linux/generic-2.6/patches-2.6.34/976-ssb_add_dma_dev.patch
applies to 2.6.32.15 without any changes, should be the same for 2.6.33 too.
Maddes
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Just tested 2.6.32.15 on the Backfire branch for Orion CPU.
Only the package carl9170 didn't compile and a few patches had some offsets.
* MD5SUM:
ifeq ($(LINUX_VERSION),2.6.32.15)
LINUX_KERNEL_MD5SUM:=1cbbf16e93bbe03368172872690600c0
endif
* Patches:
Applying patch
Salut Florian,
you took care of ticket #6552 [1] and committed the patch into trunk.
It came out that the patch broke compiling the Orion platform, that was
reported in ticket #7348 [2].
Inside this ticket the reporter of #6552 and I came to a much cleaner
approach.
Would be great if you could
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.
Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000
Both, backfire and latest trunk.
Can you hint me where this patch is?
Maddes
On 25.05.2010 21:59, Bernhard Loos wrote:
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?
2010/5/25 Matthias Buecher / Germany m
this work out of the box with uboot-envtools?
Maddes
On 25.05.2010 23:14, Bernhard Loos wrote:
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
2010/5/25 Matthias Buecher / Germany m...@maddes.net:
Both, backfire and latest trunk.
Can
Tried to set that flag, but can not find the right spot.
Any help?
Maddes
On 26.05.2010 00:08, Bernhard Loos wrote:
It should work out of the box with the patch.
It will (should) set the erase size to the right value.
2010/5/26 Matthias Buecher / Germany m...@maddes.net:
So I can mark
New stable kernel releases are available, especially 2.6.34 is interessting.
The Orion platform compiles fine with 2.6.32.12. No re-basing of
platform patches needed.
Attached are two patches (-p0) for trunk.
Add md5sums of latest stable kernels (2.6.32.13 and 2.6.34)
Signed off by: Matthias
The 2.6.34 md5sum was added in r21498, so only 2.6.32.13 is missing.
#1
Add md5sum of kernel 2.6.32.13.
Signed off by: Matthias Bücher m...@maddes.net
#2
Update Orion to kernel 2.6.32.13.
Signed off by: Matthias Bücher m...@maddes.net
On 17.05.2010 20:01, Matthias Buecher / Germany wrote
It may not downsize the packages themselves, but moving kernel mods from
rootfs to the kernel image will reduce the rootfs size. Leaving more
space for JFFS2 rootfs_data.
Having a K setting for kernel options would be great.
Will try to have a look at it during the next weeks.
Thanks for all
the size of the rootfs_data
stay the same? Both are lzma compressed.
..ede
On 10.05.2010 19:16, Matthias Buecher / Germany wrote:
It may not downsize the packages themselves, but moving kernel mods from
rootfs to the kernel image will reduce the rootfs size. Leaving more
space for JFFS2
according the space requirement?
Looks like the linux size is fixed, what is the maximum size for a
kernel on wrt54g?
.. ede
On 10.05.2010 23:28, Matthias Buecher / Germany wrote:
Kernel and rootfs are in two different mtd partitions on the WRT54G:
# dmesg
...
Creating 5 MTD partitions
On 10.05.2010 23:47, Bernhard Loos wrote:
2010/5/10 Bernhard Loos bernhardl...@googlemail.com:
2010/5/10 Matthias Buecher / Germany m...@maddes.net:
The linux partition spans over the kernel and the complete rootfs for
flashing.
The maximum kernel size is 0x000bc000 (begin of rootfs) minus
it will not be sufficient
to update the clock every 24h when my provider restarts the connection.
Will have to add a cron job for rdate.
Maddes
On 30.04.2010 22:23, Matthias Buecher / Germany wrote:
I wanted to upgrade my mom's WRT54G v2.2 from WR 0.9 to Backfire 10.03.
But during installation the flash
.
Thanks for the clarification, much appreciated.
Maddes
On 09.05.2010 18:28, Matthias Buecher / Germany wrote:
Sorry, my description was inaccurate.
In 'make menuconfig' the sign is '*' when pressing 'Y' and in the
resulting config file it is '=Y'.
@Bernhard:
So this adds kernel modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Created a patch that adds two new functions to lib/config/uci.sh:
uci_get() and uci_get_state()
The counterparts to the existing uci_set() and uci_set_state() functions.
A second patch changes packages to use the new functions, as several
packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While trying to reduce flash mem usage for my old WRT54G with 4MB I
created a patch that adds ntpclient functionalties to rdate.
Additionally ntp servers are separated into a new config file to reduce
JFFS2 usage even further.
Patch and changes are
to update the clock every 24h when my provider restarts the connection.
Will have to add a cron job for rdate.
Maddes
On 30.04.2010 22:23, Matthias Buecher / Germany wrote:
I wanted to upgrade my mom's WRT54G v2.2 from WR 0.9 to Backfire 10.03.
But during installation the flash space got full
Tried to create an OpenWrt of a small VoIP proxy for a friend.
Unfortunately the source itself does not have a Makefile.
It just says Use: gcc -o mjproxy md5.c mjproxy.c.
How must the Build/Compile section look like for such a case?
Looked at wiki and forum, but couldn't find any fitting
Thanks to Mirko and Florian, I got it compiled and my friend will test
tomorrow.
Hmm, adding a Makefile via a patch to the original source looks like
double work to me, but a valid idea.
My friend and I are currently trying to get in contact with the author
to get this addressed.
If all goes
I wanted to upgrade my mom's WRT54G v2.2 from WR 0.9 to Backfire 10.03.
But during installation the flash space got full and OpenVPN couldn't be
installed.
First I built an image without luci, then all packages fit into the
flash mem.
But when installing webif I got the same disk full error for
On 29.04.2010 21:03, Jo-Philipp Wich wrote:
Hmm, I got used to the fact that wan and lan mac are often the same on
various routers... but when settings all bridge ports to the same mac,
wouldn't that break arp etc.?
~ Jow
If you do not set the LAN mac address, then all bridge ports will
When changing the LAN mac address on a WRT54G v2.2 the router becomes
inaccessible from the LAN (no ping, no SSH, etc.).
The same happens on a WRT350Nv2 (Orion CPU), therefore it seems to be a
general issue.
Only revived the router back via serial access, as Backfire brcm47xx
(Linux 2.6) provides
Add MD5 sum of kernel 2.6.32.11 to Backfire.
Signed off by: Matthias Buecher m...@maddes.net
Index: target/linux/orion/Makefile
===
--- target/linux/orion/Makefile (revision 21152)
+++ target/linux/orion/Makefile (working copy)
@@
This works. Thanks.
On 21.04.2010 22:14, Jo-Philipp Wich wrote:
Try /bin/busybox reboot
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
it.
Travis
On Fri, Apr 16, 2010 at 2:41 PM, Matthias Buecher / Germany
m...@maddes.net wrote:
I set the root password way before I installed packages.
Here's how I installed Backfire:
1. Set root password via telnet to enable ssh
2. Configure network
3. Install other packages
4. Remove luci
5
Unfortunately X-Wrt's r4894 was not added to X-Wrt's Backfire branch.
When I compiled with the X-Wrt feed I still got the unfixed version.
Hence I changed feeds.conf.default to src-svn xwrt
http://x-wrt.googlecode.com/svn/trunk;, compiled and tested again.
It worked fine for me.
Please consider
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With Backfire I can not reboot the device after I issued a firstbot.
This was working fine in previous trunk builds, e.g. 19875 from end of
February.
Have used it often to restart from scratch and test in a clean environment.
r...@router:~# firstboot
Also tried /etc/init.d/firewall restart after restarting the network?
Maddes
On 18.04.2010 16:38, Nuno Gonçalves wrote:
I have internet connections at eth0.2 and eth1.
Config is like this:
config interface wan
option ifname eth1
option protodhcp
After boot
You have to take care of it.
Maddes
On 18.04.2010 23:41, Nuno Gonçalves wrote:
From: Matthias Buecher / Germany m...@maddes.net
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] iptables NAT not being updated on WAN
changes
Message-ID
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Due to the problem I rebuild a Backfire image from r20886 with the
config from http://downloads.openwrt.org/backfire/10.03/orion/OpenWrt.config
opkg shows the following related to uhttpd and webif:
uhttpd - 8
haserl - 0.9.26-1
webif - 0.3-4893
luci
, if not, then this is the issue.
Travis
On Fri, Apr 16, 2010 at 1:53 PM, Matthias Buecher / Germany
m...@maddes.net wrote:
Due to the problem I rebuild a Backfire image from r20886 with the
config from http://downloads.openwrt.org/backfire/10.03/orion/OpenWrt.config
opkg shows the following related to uhttpd
Changeset 20803 ( https://dev.openwrt.org/changeset/20803 ) updated the
patches for 2.6.33.2, but adding this version to
include/kernel-version.mk was forgotten (see
https://dev.openwrt.org/browser/trunk/include/kernel-version.mk ).
Maddes
___
Reminder to add ticket #7111 and also #7113 to trunk and backport to
Backfire.
Thanks
Maddes
On 07.04.2010 19:45, Matthias Buecher / Germany wrote:
Documented in https://dev.openwrt.org/ticket/7111, so it will not be
forgotten.
Maddes
On 03.04.2010 17:13, Matthias Buecher / Germany wrote
Wow, that fast (not to say hasty): three RCs and the release in only two
weeks.
I wasn't even able to test RC3 before the release came out.
Maddes
On 07.04.2010 09:02, Nico wrote:
OpenWrt Release 10.03, codename Backfire.
The OpenWrt team will humbly like to announce the final version of the
Documented in https://dev.openwrt.org/ticket/7111, so it will not be
forgotten.
Maddes
On 03.04.2010 17:13, Matthias Buecher / Germany wrote:
Sorry, forgot the signed-off part:
Set mac address for bridge also on sub-devices
* cc: backf...@openwrt.org
Signed-off by: Matthias Buecher m
Sorry, forgot the signed-off part:
Set mac address for bridge also on sub-devices
* cc: backf...@openwrt.org
Signed-off by: Matthias Buecher m...@maddes.net and Peter van Valderen
p.v.valde...@gmail.com
On 02.04.2010 21:21, Matthias Buecher / Germany wrote:
If a mac address is set for the lan
If a mac address is set for the lan bridge, e.g.
network.lan.macaddr=00:1a:70:a0:38:80
then it is only set on the bridge itself and not the sub-devices
br-lanLink encap:Ethernet HWaddr 00:1A:70:A0:38:80
lan1 Link encap:Ethernet HWaddr 00:00:00:00:51:81
lan2 Link
Happens to me on Linksys WRT350Nv2 (Orion CPU):
Adminstration - System - System:
XML Parsing Error: unclosed token
Location:
http://10.0.0.254/cgi-bin/luci/;stok=160e97786ece60ac94533c0785be4583/admin/system/system/
Line Number 264, Column 3: input type=submit class=cbi-button
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make
have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6
Is the script set to executable (+x) in the image?
This is typical for scripts that are presebt but not running, and often
overlooked.
Maddes
On 20.03.2010 04:02, Otto Solares wrote:
It works on squashfs but didn't on pure jffs2 which I pressume was our
only environment difference.
The
Update Orion to Linux kernel 2.6.32.10
Signed off by: Matthias Buecher m...@maddes.net
The most simple, a single line in the Makefile.
All patches applied cleanly.
Everything compiled well.
Index: target/linux/orion/Makefile
===
On 17.03.2010 21:01, Travis Kemen wrote:
On Wed, Mar 17, 2010 at 5:26 AM, Matthias Buecher / Germany
m...@maddes.net wrote:
Update Orion to Linux kernel 2.6.32.10
Signed off by: Matthias Buecher m...@maddes.net
The most simple, a single line in the Makefile.
All patches applied cleanly
Just flashed Backfire 10.03-beta for Orion from
http://downloads.openwrt.org/backfire/10.03-beta/orion/ and recognized
that opkg is pointing to
src/gz snapshots
http://downloads.openwrt.org/snapshots/trunk/orion/packages
instead of
src/gz backfire
, at least for Orion
Maddes
On 16.03.2010 22:56, Travis Kemen wrote:
Did you do a opkg update before installing like the errors say to do?
Travis
On Tue, Mar 16, 2010 at 4:52 PM, Matthias Buecher / Germany
m...@maddes.net wrote:
On 16.03.2010 21:42, Bruno Wolff III wrote:
On Tue, Mar 16, 2010
1 - 100 of 168 matches
Mail list logo
