Re: [OpenWrt-Devel] routerstation and madwifi
On Mon, Jun 29, 2009 at 06:42, Vasilis Tsiligiannis wrote: On Sunday 28 June 2009 19:08:10 David A. Bandel wrote: Vasilis, Well, in 16603 neither compression off nor backing out 434 works (or so it seems). I'm open to more suggestions. David- Hi David, Trying backing out r15949 patch. Btw, do you have access to the serial console? That's the big problem, I don't. I may be able to build a cable -- the board has UART pins. I have no jtag for a mips board either. Working this purely from ethernet. If syslog is alive, perhaps I can grab some snippets before it locks up. Will try 15949. David- -- Focus on the dream, not the competition. - Nemesis Air Racing Team motto signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] new package: nginx
Le lundi 29 juin 2009 à 22:12 +0200, Benjamin Cama a écrit : > +define Package/nginx > + SECTION:=custom > + CATEGORY:=Custom Mmmhhh forgot to change that to: + SECTION:=net + CATEGORY:=Network --- benjamin ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] new package: nginx
Hi,
I just wrote a Makefile + patches to compile nginx ( http://nginx.net/ )
for openwrt. It is quite basic for now (no init scripts, no
openwrt-specific config file), and has some hardcoded requirement, but
should run ok for those wanting to experiment with it.
The "hardcoded" requirements are for things that nginx want to run on
the host, but are OK for a recent 2.6 kernel and GNU userland, I think.
License-wise, the sizeof patch has been inspired by autoconf (see
http://ac-archive.sourceforge.net/ac-archive/compile_value.html ) and
the configure arguments come mainly from the debian package for nginx. I
think everything is OK, but I'd appreciate if someone could adivse of
any conflict.
Things to fix:
* Add init scripts
* Add a default config file for openwrt /etc/config
* Fix the --crossbuild argument to reflect kernel version number
* Fix the installation paths, they are debian-standards but may not be
well fitted for openwrt
Signed-off-by: Benjamin Cama
---
Index: nginx/patches/002-sizeof_test_fix
===
--- nginx/patches/002-sizeof_test_fix (révision 0)
+++ nginx/patches/002-sizeof_test_fix (révision 0)
@@ -0,0 +1,28 @@
+diff --git a/auto/types/sizeof b/auto/types/sizeof
+index 4d65dca..2d5da3e 100644
+--- a/auto/types/sizeof
b/auto/types/sizeof
+@@ -23,8 +23,13 @@ $NGX_INCLUDE_UNISTD_H
+ $NGX_INCLUDE_INTTYPES_H
+ $NGX_INCLUDE_AUTO_CONFIG_H
+
++char object_code_block[] = {
++'\n', 'e', '4', 'V', 'A',
++'0', 'x', ('0' + sizeof($ngx_type)),
++'Y', '3', 'p', 'M', '\n'
++};
++
+ int main() {
+-printf("%d", sizeof($ngx_type));
+ return 0;
+ }
+
+@@ -38,7 +43,7 @@ eval "$ngx_test >> $NGX_AUTOCONF_ERR 2>&1"
+
+
+ if [ -x $NGX_AUTOTEST ]; then
+-ngx_size=`$NGX_AUTOTEST`
++ngx_size=`sed -ne 's/^e4VA0x\(.\)Y3pM$/\1/p' < $NGX_AUTOTEST`
+ echo " $ngx_size bytes"
+ fi
+
Index: nginx/patches/001-feature_test_fix
===
--- nginx/patches/001-feature_test_fix (révision 0)
+++ nginx/patches/001-feature_test_fix (révision 0)
@@ -0,0 +1,144 @@
+diff --git a/auto/cc/conf b/auto/cc/conf
+index 4823900..1e676f4 100644
+--- a/auto/cc/conf
b/auto/cc/conf
+@@ -135,7 +135,8 @@ if [ "$NGX_PLATFORM" != win32 ]; then
+ ngx_feature_test="char buf[30]; buf[0] = '0';
+ var(0, buf, \"%d\", 1);
+ if (buf[0] != '1') return 1"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+
+
+ if [ "$NGX_CC_NAME" = "ccc" ]; then
+@@ -151,7 +152,8 @@ if [ "$NGX_PLATFORM" != win32 ]; then
+ ngx_feature_test="char buf[30]; buf[0] = '0';
+ var(0, buf, \"%d\", 1);
+ if (buf[0] != '1') return 1"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+ fi
+
+
+diff --git a/auto/cc/name b/auto/cc/name
+index d197fc5..28b74b0 100644
+--- a/auto/cc/name
b/auto/cc/name
+@@ -13,12 +13,12 @@ if [ "$NGX_PLATFORM" != win32 ]; then
+ ngx_feature_test=
+ . auto/feature
+
+-if [ $ngx_found = no ]; then
+-echo
+-echo $0: error: C compiler $CC is not found
+-echo
+-exit 1
+-fi
++#if [ $ngx_found = no ]; then
++#echo
++#echo $0: error: C compiler $CC is not found
++#echo
++#exit 1
++#fi
+
+ fi
+
+diff --git a/auto/os/linux b/auto/os/linux
+index 0bd0488..9cb0aa1 100644
+--- a/auto/os/linux
b/auto/os/linux
+@@ -49,7 +49,8 @@ ngx_feature_test="int efd = 0, fd = 1, n;
+ ee.data.ptr = NULL;
+ efd = epoll_create(100);
+ if (efd == -1) return 1;"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+
+ if [ $ngx_found = yes ]; then
+ have=NGX_HAVE_CLEAR_EVENT . auto/have
+@@ -73,7 +74,8 @@ ngx_feature_test="int s = 0, fd = 1;
+ ssize_t n; off_t off = 0;
+ n = sendfile(s, fd, &off, 1);
+ if (n == -1 && errno == ENOSYS) return 1"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+
+ if [ $ngx_found = yes ]; then
+ CORE_SRCS="$CORE_SRCS $LINUX_SENDFILE_SRCS"
+@@ -94,7 +96,8 @@ ngx_feature_test="int s = 0, fd = 1;
+ ssize_t n; off_t off = 0;
+ n = sendfile(s, fd, &off, 1);
+ if (n == -1 && errno == ENOSYS) return 1"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+
+
+ ngx_include="sys/prctl.h"; . auto/include
+@@ -108,7 +111,8 @@ ngx_feature_incs="#include "
+ ngx_feature_path=
+ ngx_feature_libs=
+ ngx_feature_test="if (prctl(PR_SET_DUMPABLE, 1, 0, 0, 0) == -1) return 1"
+-. auto/feature
++#. auto/feature
++have=$ngx_feature_name . auto/have
+
+
+ # sched_setaffinity()
+diff --git a/auto/unix b/auto/unix
+index 687a23a..23e8b78 100755
+--- a/auto/unix
b/auto/uni
[OpenWrt-Devel] NuWiki meeting thursday @ 20:00 CEST
Hello NuWiki'ans and interested people This is the call for the 1th NuWiki development meeting, please check the agenda at -> http://nuwiki.openwrt.org/meta/ircmeeting Chz -- Gregers Petersen Relationship manager, layer 8 and anthropology momu.dk/blog/ glp on irc ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M KAMIKAZE (bleeding edge) --- * 10 oz Vodka Shake well with ice and strain * 10 oz Triple sec mixture into 10 shot glasses. * 10 oz lime juice Salute! --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About Atmel at91
Hi Tian, I got an old board with u-boot(1.0.0) and linux(2.4.19) binaries and documents. Which board do you have? Is it one of the Atmel evaluation boards? I can download u-boot and linux binaries to the board through serial and it works, but documents are not very detailed, do not mention u-boot porting and I am new to u-boot, so I do not know where to start from to move to the OpenWRT build. For what purpose are you wanting to use this board, is it just for experimenting, or do you have a real project you are wanting to use it for? There is not a lot of documentation available for most boot-loaders - a lot of the process involves studying the code and your board schematics. Regards Hamish ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About Atmel at91
Great. I tried r14800 that can be compiled, but I don't know how to modify u-boot that the board uses. On at91rm9200, the boot process is a little complex, but is described here: http://www.open-research.org.uk/ARMuC/At91rm9200_Booting.html Does your board already boot, or are you trying to bring up a board which has never booted? Essentially in the OpenWRT build the dfboot.bin binary is 'tiny program' referred to. Your best bet would be to try to get that running on your hardware first before trying to modify u-boot. Regards Hamish ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About Atmel at91
ham...@prodigi.ch 写道: >> Hello, >> I am working with an Atmel at91RM9200-based board, and I am new to at91, >> cannot make Target System(Atmel AT91) work. >> >> target/linux/at91/image/dfboot and target/linux/at91/image/u-boot >> confused me a lot. >> >> Any suggestions about 9200, 9260, 9261 are welcome. >> > > Currently the bootloaders for at91rm9200 target is broken - I am busy > working on getting this at the moment - the reason for the breakage was > updating the abi for all ARM targets from oabi to eabi, and the fact > that I have not had hardware to test on for the last few months - I did > get hardware again last week, but have not had a chance to work on this. > > You could try going back to revision 11747 in SVN - the tree for at91 > was known to be good at that point in time. > > Regards > > Hamish > Great. I tried r14800 that can be compiled, but I don't know how to modify u-boot that the board uses. Thanks Tian HongPeng ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About Atmel at91
Hello, I am working with an Atmel at91RM9200-based board, and I am new to at91, cannot make Target System(Atmel AT91) work. target/linux/at91/image/dfboot and target/linux/at91/image/u-boot confused me a lot. Any suggestions about 9200, 9260, 9261 are welcome. Currently the bootloaders for at91rm9200 target is broken - I am busy working on getting this at the moment - the reason for the breakage was updating the abi for all ARM targets from oabi to eabi, and the fact that I have not had hardware to test on for the last few months - I did get hardware again last week, but have not had a chance to work on this. You could try going back to revision 11747 in SVN - the tree for at91 was known to be good at that point in time. Regards Hamish ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] About Atmel at91
Hello, I am working with an Atmel at91RM9200-based board, and I am new to at91, cannot make Target System(Atmel AT91) work. target/linux/at91/image/dfboot and target/linux/at91/image/u-boot confused me a lot. Any suggestions about 9200, 9260, 9261 are welcome. Thanks in advance, Tian Hongpeng ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] routerstation and madwifi
On Sunday 28 June 2009 19:08:10 David A. Bandel wrote: > Vasilis, > > Well, in 16603 neither compression off nor backing out 434 works (or so it > seems). I'm open to more suggestions. > > David- Hi David, Trying backing out r15949 patch. Btw, do you have access to the serial console? Regards, Vasilis signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Note for mips/mipsel targets running trunk
Thanks for pointing out ... bud Hi, Since changesets 16606 and 16607 we have switched to using software floating point emulation in the toolchain and we disabled the in-kernel FPU Emulator in the MIPS kernel by default. The rationale behind this is : - the FPU emulator of the kernel is slow and works by catching floating point operations exceptions, emulating them and continuing its work - software floating point emulation is only added when a program needs it and will not bloat fixed point programs (most) with software floating point code, additionnaly software floating point is faster due to the absence of the exception mechanism - for consistency, other targets (arm, powerpc) also use software floating point This allows us to have a kernel which is slightly smaller (~ 1%) and faster, and since most programs do not use floats, their memory footprint do not change while programs using float have a slightly bigger one as they require software floating point emulation. Still the tradeoff is worth :) The "bad" effect is that you have to recompile your mips/mipsel toolchain AND kernel otherwise you will get a device which boots the kernel then silently fails while running busybox (the later using floats). Thank you very much for your attention. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Note for mips/mipsel targets running trunk
Hi, Since changesets 16606 and 16607 we have switched to using software floating point emulation in the toolchain and we disabled the in-kernel FPU Emulator in the MIPS kernel by default. The rationale behind this is : - the FPU emulator of the kernel is slow and works by catching floating point operations exceptions, emulating them and continuing its work - software floating point emulation is only added when a program needs it and will not bloat fixed point programs (most) with software floating point code, additionnaly software floating point is faster due to the absence of the exception mechanism - for consistency, other targets (arm, powerpc) also use software floating point This allows us to have a kernel which is slightly smaller (~ 1%) and faster, and since most programs do not use floats, their memory footprint do not change while programs using float have a slightly bigger one as they require software floating point emulation. Still the tradeoff is worth :) The "bad" effect is that you have to recompile your mips/mipsel toolchain AND kernel otherwise you will get a device which boots the kernel then silently fails while running busybox (the later using floats). Thank you very much for your attention. -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
