-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
by the time we have gcc 5 the patch will be obsolete.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4eEe8ACgkQdputYINPTPNnrACeJWvlSmK40M0kb7O
The OpenWrt team will humbly like to announce the 5th release candidate
of the 10.03.1 maintenance release.
___ __
| |.-.-.-.| | | |..| |_
| - || _ | -__| || | | || _|| _|
|___|| __|_|__|__||
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I took a look at it and it seems that upstream now gracefully handles
errors in the PADS processing, on a first glance I see no condition
anymore that may lead into a fatal() so dropping this patch is ok.
~ Jow
-BEGIN PGP SIGNATURE-
Versi
Hi.
> - KCONFIG:=CONFIG_INPUT_EVDEV
> + KCONFIG:=CONFIG_INPUT_EVDEV +kmod-input-core
This looks wrong.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> Remaining question:
> I have not checked the nixio code but I assume
> nixio.uname().machine
> would be
> uname -m
> in a bash shell script, right?
Correct.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Will this work?
> It will need root mounted already to load the module.
Yes. The extroot code in the preinit sequence will arrange stuff as
needed and either configure the mass storage later on as either overlay
filesystems or in newer versions a pi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I don't see why we can't just update valgrind, if you want to give it a
try I can offer to help you with testing or porting.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> +-USE_BIGENDIAN ?= AUTO
> ++USE_BIGENDIAN ?= YES
This looks wrong.
You should rather add something like the line below to the OpenWrt makefile:
MAKE_VARS += USE_BIGENDIAN=$(if $(CONFIG_BIG_ENDIAN),YES,NO)
~ Jow
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is that it? I don't understand how the systems works out to pull in
> the correct feed version. I can understand how it works for tagged
> feeds, e.g. svn://svn.openwrt.org/openwrt/branches/packages_10.03.1
> but I don't get how it can work for
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I have also removed the @BROKEN symbol, as all packages build fine
> here with trunk r28297 for at least BRCM, AR7, x86 and UML
> architectures. I read on the forum that there was some problems
> building the programs but I did not find any repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
committed the squashfs parallel option slightly modified in r28305 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5/3aUACgkQdputYINPT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> What should I do in order to have also a KXXfoo link?
Define STOP=nn where nn is an integer between 00 and 99.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Iordan,
I gave it a try and it looks quite good on first sight.
However I have some issues, the sections in the call routing tab are
empty and the "Server Setting for Local SIP Devices" shows no input field.
You might want to recheck this on a fre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
you'll get the IP address behaviour if "lan" is set to proto dhcp or
something else which does not specify an ipaddr in advance.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://eni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, thats probably enough.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6cZu8ACgkQdputYINPTPN65QCdGD/8SjP4H5BiIlww5Cd3hUZr
t6IAn3hmizfBu1h3TJJuAs
Your gcc commandline lacks -lpcap, also never compile against host
headers when cross compiling, use the pcap headers in staging_dir.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r28556 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6lrTYACgkQdputYINPTPPHxACfRGRvZRvzWXWhUY9qtuMVHOqM
fcIAn3HJ8S9KWs6I420/N6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r28555 - thanks!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6lrUYACgkQdputYINPTPNXRgCbBLBx7fBMK7d2HuYUhJE3OJdv
+EUAmwVuyLXBHhHUfXvd5EtqL6B+3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That one does not apply against the current head, can you update the patch?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6lrWAACgkQdputYINPTPPT2QC
Committed with minor modification in r28573 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Applied in r28574 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This one does not apply against current head, can you please update it?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> +US_PATH="/usr/sbin/lisp"
> +KMOD_PATH="/usr/sbin"
> +CONF_PATH="/lib/network/lisp"
> +IF_NAME="eth1"
> +
> +# RLOC used in ip rules for source routing
> +#RLOC="128.107.165.94"
> +RLOC=`/sbin/ifconfig eth1 | sed '/inet\ /!d;s/.*r://g;s/\ .*//g'
I am not Felix but as I did the change, let me answer here.
> I understand the rationale of the change from busybox to ntpd in
> standard. Does that mean though that the ntpd package has to be chosen
> in the .config file
No.
> or is ntpd really integrated into busybox, making
> the ntpd client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> If I understood you correctly, it is enough to just use the busybox ntpd
> and no ntpclient package needs to be selected separately?
Yes.
> Is there any need for luci-app-ntpc in the build or can it also be left
> out?
Can be left out.
> Is
Hi Saverio,
just remove the patch, I assume the txtinfo is uniformly formatted now.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The OpenWrt team will humbly like to announce the 6th release
candidate of the 10.03.1 maintenance release.
___ __
| |.-.-.-.| | | |..| |_
| - || _ | -__| || | | || _|| _|
|___|| __|_|__|__||
Hi,
you're supposed to use "iw" with modern mac80211.
To spawn a real monitor interface:
iw phy phy0 interface add mon0 type monitor; ifconfig mon0 up
See also http://wireless.kernel.org/en/users/Documentation/iw
It is certainly not required to recompile the driver.
The mon.wlanX devices are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Then simply do the same nl80211 api calls (netlink messages) that iw
uses, its easy.
Wext (the api that iwconfig uses) is deprecated and will disappear soon
- - so you should do yourself a favor and avoid it.
~ Jow
-BEGIN PGP SIGNATURE-
Versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r28776 - thanks!
Will merge it to backfire together with the other SSL fixes soon.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk62q8E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r28872 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk657N4ACgkQdputYINPTPMUKACcD1yxTfqtz8AreM0IJ3cr8IVj
nzMAnjTFPnHpEDxCiFppWC
Your running LuCI is too old, simply update it.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Care to explain what you mean? It looks fine in both Trac and my local
svn checkout.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
committed in r29136 and r29138 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7Bi2sACgkQdputYINPTPMq9gCgiTx0DxDoJmGHB53LJhCISXz+
hkcA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
SIOCGIWPRIV is part of the deprecated wext api which is not fully
supported by ath9k. Use nl80211. See wireless.kernel.org for details,
also check the source code of the "iw" utility.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Hanno,
the interesting bits are in package/madwifi/patches/384-hwdetect.patch .
Basically the model name is inferred from the PCI IDs of the radio, this
might work for some popular appliances but I guess it will fail for
generic boards with replac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is this information of 'vendor id' and 'subsys id' visible somewhere
> in 'user land' i.e on the command line, possibly with additional
> packages like pciutils? or some other way?
Yep, see /sys/bus/pci/devices/*/vendor and /sys/bus/pci/devices/*/de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
https://dev.openwrt.org/wiki/GetSource
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7L3YIACgkQdputYINPTPNzNgCbB0odOr2oCGIapRxY+ZHD88JJ
4sYAn3tS6J43m5mlF3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is one for packages, none for packages_10.03.1 if you mean that.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7L3wEACgkQdputYINPTPNpKwCeLjpkOfT1DB0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the patch looks very well. Testing it atm and will commit it if there
are no issues.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7SesoACgkQd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r29343 and r29344 - thank you!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7Sgg4ACgkQdputYINPTPNZSwCcC5a/F1dcVPq6tz0Zpws9YRcV
TvUAn1u5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this happens if you do not start with a fresh .config .
The profiles actually just populate the CONFIG_DEFAULT_* variables. If
everything is populated already they have no effect anymore.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10
Hi.
> Should we put the option back? Or should this option be placed somewhere
> else?
> In any case it seems required.
Problem with hardcoding br-lan is that it must not always be a bridge
(lan can be unbridged by default as well, for example on the Dockstar
which ironically is a NAS appliance
Hi.
You must pick the target which matches your board, it is used across
various placing, ranging from optimization flag settings to package
architecture fields. The correct one for the LifeBox would be the
brcm63xx target.
As far as I can see it in my local test it does indeed build the
ext
Current LuCI covers both backfire and trunk. Applying your fix will
break backfire, not applying your fix will break trunk. Merging current
OpenVPN to Backfire will break existing configs, just accepting enable
and enabled breaks nothing - easy choice.
~ Jow
___
Am 30.11.11 06:28, schrieb i iordanov:
> This is the last one for now! I hope I haven't been too annoying! :)
>
> 1) Setting the hostname of the router to anything does not actually
> add an entry to /etc/hosts. This is a problem if one expects the
> hostname to resolve to something, and on OpenWR
Already fixed since yesterday - please make sure to use the most recent
feeds before reporting issues.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Hanno,
for starters you could just compile and install "iwinfo", then run it
on your board like this:
iwinfo ath0 info or iwinfo wlan0 info
It should output data similar to this:
- -- 8< --
root@uplink:~# iwinfo wlan1 i
wlan1 ESSID: "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unclean tree.
./scripts/feeds update luci
./scripts/feeds uninstall libiwinfo iwinfo
svn up
make defconfig package/iwinfo/clean world V=99
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
should be fixed with https://dev.openwrt.org/changeset/29474 and
https://dev.openwrt.org/changeset/29475
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Updates committed in r29481 (trunk) and r29482 (backfire). Thank you.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7f+hsACgkQdputYINPTPPG8wCfTAdzW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Helmut,
this is already implemented, see scan_mac80211().
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7iKGYACgkQdputYINPTPPJUwCcDUBFQ6hvRMt6M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> *) For each stored 'connection' a new 'wlanN' Interface, is brought up.
> Usually also an associated instance of
> wpa_supplicant is launched, consuming startup time, memory, and cpu
> resources.
Use option disable on the wifi-iface.
> *) Log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So rework mac80211/wpa_supplicant integration to work like hostapd,
there we also just define a base part and append additional sections for
each wifi-iface.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I didn't make this patch, it came from jow. I changed use of libnl-tiny
> to libnl, since in my testing, it didn't compile with the former.
What are the issues with libnl-tiny? I really don't want this to depend
on full libnl, linking against
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See https://dev.openwrt.org/changeset/29558
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7sAmMACgkQdputYINPTPN9SQCcDiV5+qhWduOaUsLoue8mBZbb
W9EAnR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks for you patch, unfortunately I cannot accept kernel level patches
for Backfire anymore. If we do another point release after 10.03.1 we'll
look into it.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the patch looks okay but maybe you can change a few things:
* the init script should use the new service_* functions to properly
detach om-watchdog from the calling shell
* the om-watchdog should trap some common signals to be more robust
21 December 2011
The OpenWrt Release Team would like to announce the final
Backfire Interim Release 1 (10.03.1).
___ __
| |.-.-.-.| | | |..| |_
| - || _ | -__| || | | || _|| _|
|___|| __|_|__|__||__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
/etc/config/ucitrack defines config<>init relations - the section name
corresponds to the config name, the "option init" specifies the init
script name.
Note that LuCI versions up to and including r8126 have a bug that
prevents apply actions for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk76adYACgkQdputYINPTPNxHgCaAq9obfl1bIgns84+hRRSulfN
IfsAn2vYLBeDi+DKLwFxYkcFgOUzV7VO
=RCCq
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Ubiquiti tightened the regulatory enforcement. They now ship with a
regdomain entry in the boarddate which is not recognized by OpenWrt's
HAL, therfore the wifi is rejected.
It can be fixed by changing the byte at offset 0x277 in mtd6 to 0x00 or
Hi.
> Is it because of dnsmasq (I didn't change its settings) or hostapd?
It seems to correlate with the WPA rekeying. You could try to lower the
group rekey interval and see if it helps.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Added in r29645.
Next time ensure that you include a signed-off-by line and that the
patch is applicable with -p1.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Hi.
> Error: bad register name `%sil'
You probably need a patch similar to this:
http://old-list-archives.xen.org/archives/html/xen-devel/2009-05/binBCldaQtw31.bin
I see whether I can prepare one tonight.
~ Jow
___
openwrt-devel mailing list
openwrt-
An OOM is not considered to be a panic by default afaik.
Regarding your cronjob idea; won't work imo. Many (most?) watchdog
drivers do not support >= 60 second intervals.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Use "DEPENDS:=+CONFIG_MYPACKAGE_USES_LIBRARY:mylib" (the plus in front).
That will also make the PKG_BUILD_DEPENDS unnecessary.
Adding a plus in front of a dependency spec means your package selects
the dependant package and it is also propagated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking again at your Kconfig snippet, the depends do not make sense to
me. The bool option which ultimatively is supposed to select mylib
depends itself at mylib. This looks like a recursive dependency to me
and it does not surprise me that it does no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can suppress this note by ensuring the compiler is called with
"-fhonour-copts". If the configure script does not respect the CFLAGS
variable, you can try to redefine CC as
CC="$(TARGET_CC) -fhonour-cflags".
hth,
~ Jow
-BEGIN PGP SIGNATURE--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just seen your message on the Lua list - be aware that OpenWrt Lua is
heavily patched, so maybe try again with some of the Lua patches removed
and see if the issue persists.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
libre fails to build here, seems to lack an include of stdint.h in
re_types.h :
- -- >8 --
make -C
/home/jow/devel/openwrt/trunk/build_dir/target-mips-linux-gnu/re-0.4.0
HAVE_LIBRESOLV= CC="mips-linux-gnu-gcc" EXTRA_CFLAGS="-Os -pipe -mips32
- -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> libre fails to build here, seems to lack an include of stdint.h in
> re_types.h
Adding stdint.h indeed solves it nicely.
- --- a/include/re_types.h
+++ b/include/re_types.h
@@ -5,6 +5,7 @@
*/
#include
+#include
#ifdef _MSC_VER
#include
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
so I added the stdint.h patch for now. After that the build fails on
linking baresip:
- -- 8< --
LD baresip
build-mips/src/play.o: In function `play_alloc':
/home/jow/devel/openwrt/trunk/build_dir/target-mips-linux-gnu/baresip-0.4.0/src/pl
Hi again,
it is all solved now.
Ultimatively the problem boiled down to a bad SYSROOT value which makes
things go wrong in various ways.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/ope
Hi,
the patch does not apply, can you rebase it?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
the patch does not apply, can you rebase it?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>> I was not aware openwrt lua was heavily patched. I am curious as to
>> what it will take to move forward to lua 5.2?
Since the Lua authors decided to rework the complete environment
handling (getfenv, setfenv, ...) in 5.2, LuCI will completely break.
It is a considerable effort to rework that
Hi,
your patch didn't apply due to syntax errors, I updated the package
manually in r29804 .
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
the patch didn't apply due to whitespace mangling; I updated the package
manually.
For the future:
- Make sure patches are applicable with -p1 (diff within feeds/)
- Reset PKG_RELEASE to 1 if the PKG_VERSION changes
~ Jow
___
openwrt-devel mailing
Your patch didn't apply, I redid it manually and committed the change in
r29809.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
the patch didn't apply, I folded the changes manually into r29817.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi.
Applying: New package: libJudy (Fixed)
fatal: patch fragment without header at line 8: @@ -0,0 +1,44 @@
Patch failed at 0001 New package: libJudy (Fixed)
The attached patch got its lines wrapped apparently.
~ Jow
___
openwrt-devel mailing list
ope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I need a same kind of magic to overcome this problem.
> Is there any?
Yes, patch scripts/config.sub - that is whats fored upon each package.
> Is the behavior of "Modifying a generic build tool during a build
> process for a single target" co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> Modifying the generic build tool to accept a new platform is certainly
> legitimate, nobody wants to patch a new CPU definition into each single
> package.
In general yes, in practice it should be unneeded though since we're
forced to replace c
Hi.
> Note it removes 600-usb_vbus_active_high.patch, that does not apply any
> more.
Unless upstream gained some logic to handle the inverted active state,
this is still needed, otherwise USB on the TQMA9263 will break if the
patch is not forward ported, therefore a NACK from me here.
~ Jow
___
I took a brief look and it looks like upstream now has its own
capabilities to specify an active high vbus [1], so it seems we can
drop the patch and set vbus_pin_inverted = 1 in the board-tqma9263.c
files at91_usbh_data struct.
~ Jow
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
is there any difference to the version from 20th?
As far as I can see it is identical just that this one got mangled by
your mailer.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http:/
Hey.
> I cannot get collectd-mod-iwinfo to work for the proprietary wl0
> drivers. They work fine on ath5k and ath9k.
Make sure iwinfo was compiled with wl support (wl must be enabled at
build time of libiwinfo to get enabled as backend).
> Before I try further, does collectd-mod-iwinfo support
The current code is supposed to infer the model from the PCI IDs of the
radio, apparently this is not possible and as I have no access to such a
model I cannot fix it either - I assumed ath5k exposes it the same way
madwifi does but apparently not.
~ Jow
___
Hi,
> Specifically, I'm lacking the ability to change channels (the
> important part)
option channel ?
> and have no ability to control antenna chains or adjust power.
option txpower, option rxantenna and option txantenna?
> What can I do to help improve this support, or who can I help?
You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So if you install the iwinfo cli frontend and run "iwinfo wl0 info",
does it output anything useful, does it identify the hw as "type wl" ?
Is "LoadPlugin iwinfo" in the enerated collectd.conf ?
Is "killall -9 collectd; collectd -f" reporting any erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I forgot: I observed a strange thing. In the default (autogenerated?)
> /etc/config/wireless, the device was named "radio0", while the
> correct name is "wlan0".
No, its not the correct name. The "radio0" name is an internal
identifer, it does
Hi,
the patch is whitespace mangled.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I believe your patch patch just hides the symptom of an actual problem
with cmake. Where the failing packages ones the use cmake for building?
If so I believe your issue has been fixed with r29982 .
~ Jow
-BEGIN PGP SIGNATURE-
Version: G
Hi,
applied in r29992 and r29993 - thank you!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The init script already attempts to resolve the device property first
(which should be set to ethX) and only then falls back to the ifname.
I suppose some or more state vars are not correctly set by the netifd
legacy compat scripts.
~ Jow
___
openwrt-de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r30367 and r30368 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8xqikACgkQdputYINPTPM0HACfcwhGl23F0AGsvoQAC/hZ0Ezg
5r0AoKGiJnK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So I finally got SSH access to some systems and reworked the hardware
detection to not rely on madwifi anymore.
I have committed the changes in https://dev.openwrt.org/changeset/30605
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/L
Hi.
> What is not so nice is the txpowerlist. As I had reported last year, the
> system reports 27dBm regardless which hardware is used.
Thats a mac80211 problem though, beyound the scope of iwinfo. It takes
the driver reported values and uses them.
> I can also confirm the following devices whi
> No, it does not yet, but it may not look for them yet either - after
> all there is nothing in the code for Picos until now.
It is supposed to find them, even if there is no entry in the hardware
table - so something is broken on this particular model.
Would it be possible for you to seen me a
801 - 900 of 1348 matches
Mail list logo
