- Update socat to 1.7.2.0
(main reason: avoids compile-error against kernel 3.3.5 with ext2_fs.h which
seems to got removed/changed to not being used from userspace from current
kernel)
- remove 502-no_sslv2.patch which doesn't apply surely and looks quite outdated
to me, socat isn't linked
Does anyone else find it troubling that x86 has been as stagnant as it is?
+1
I'm just about changing some Alix.1D to OpenWRT
What is required? maybe I can contribute (though admidettly I wouldn't know
what to change to get 3.3.5 instead of 2.6.39 built for this platform :()
Michael
Hi,
a formal question, rather cosmetic: played around with the WR842 today. (Which
is a really nice box with USB, 8/32MB for very few money..)
It's using the TL-MR3x20 board which seems 99% fine but it has different
buttons:
- labeled WPS / Reset which is mapped to wps right now
- labeled Wifi
Hi,
is anyone using nfsroot on ramips/rt305x platform? I couldn't get it working
without this patch[1]. So my questions are, is nfsroot working for someone on
this platform? If not, is it this patch ok (or it's a total nonsense)? Is
there a better solution? Thanks for any pointers.
1.
This updates U-Boot for the Marvell Kirkwood family to 2012.04.01.
Signed-off-by: Daniel Golle dgo...@allnet.de
diff --git a/package/uboot-kirkwood/Makefile b/package/uboot-kirkwood/Makefile
index cdf35a4..f7fb4cf 100644
--- a/package/uboot-kirkwood/Makefile
+++ b/package/uboot-kirkwood/Makefile
dockstar board support is based on sheevaplug, all changes made upstream to
sheevaplug were made for dockstar as well.
Signed-off-by: Daniel Golle dgo...@allnet.de
diff --git a/package/uboot-kirkwood/files/board/Marvell/dockstar/Makefile
iconnect board support apparently used sheevaplug as a template as well, so
same game once again.
Signed-off-by: Daniel Golle dgo...@allnet.de
diff --git a/package/uboot-kirkwood/files/board/Marvell/iconnect/Makefile
b/package/uboot-kirkwood/files/board/Marvell/iconnect/Makefile
index
On Sat, 2012-05-12 at 14:17 -0600, Philip Prindeville wrote:
Gabor is retiring old versions of 2.6.x regularly (thanks, Gabor!).
Alas, he's one step away from retiring 2.6.39.4 which is what x86 is
currently at.
Does anyone else find it troubling that x86 has been as stagnant as it is?
Thanks Mirko
Since I don't have much experience on json-rpc. can you give me some example?
I have tried
curl http://192.168.1.1/cgi-bin/luci/rpc/net/devices
it give me nothing.
I have installed those two packages:
CONFIG_PACKAGE_luci-mod-rpc=m
CONFIG_PACKAGE_luci-lib-json=m
Thanks again
On 5/13/12 7:44 PM, David Woodhouse wrote:
On Sat, 2012-05-12 at 14:17 -0600, Philip Prindeville wrote:
Gabor is retiring old versions of 2.6.x regularly (thanks, Gabor!).
Alas, he's one step away from retiring 2.6.39.4 which is what x86 is
currently at.
Does anyone else find it troubling
On 5/13/12 3:12 PM, Michael Markstaller wrote:
Does anyone else find it troubling that x86 has been as stagnant as it is?
+1
I'm just about changing some Alix.1D to OpenWRT
What is required? maybe I can contribute (though admidettly I wouldn't know
what to change to get 3.3.5 instead of
Hi
ok, I have to create a JSON request. this one is working:
curl -v -H Accept: application/json -H Content-type: application/json -X POST -d '{jsonrpc:1.0,method: login,
params: {username:root, password:x}, id:0}' http://192.168.1.1/cgi-bin/luci/rpc/auth
Will look into more. then report
Any updates on this?
If the debugging symbols are frequently needed with snapshots, would it be
possibly perhaps to have /trunk and /trunk_debug directories? Then if someone
wanted or needed debugging symbols, they could use the /trunk_debug snapshot
for their device?
I realize that this
13 matches
Mail list logo
