Re: [OpenWrt-Devel] Enabling a config option based on selected target

2011-08-15 Thread Lukas Macura
Hi Angus, look here: https://homeproj.cesnet.cz/projects/besip/repository/entry/Trunk/OpenWrt/besip/Makefile into dependencies of besip-lite package (latest entries). Is it what you are searching for? With regards, Lukas Dne 16.8.2011 01:45, Angus Gratton napsal(a): > I've been porting OpenWRT

[OpenWrt-Devel] [PATCH] update usb-modeswitch to 1.1.19

2011-08-15 Thread Hanno Schupp
Signed-off-by: Your name Index: Makefile === --- Makefile(revision 28007) +++ Makefile(working copy) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=usb-modeswitch -PKG_VERSION:=1.1.8 +PKG_VERSION:=1.1.9 PKG_RELEA

[OpenWrt-Devel] [PATCH] update usb-modeswitch-data to make it compile again

2011-08-15 Thread Hanno Schupp
The update is required as the old filename usb-modeswitch-data-20110705.tar.bz2 is no longer hosted on http://www.draisberghof.de/usb_modeswitch/ BTW, the two openwrt.org backup servers do not hold either the old usb-modeswitch-data-20110705.tar.bz2 nor the new usb-modeswitch-data-20110805.tar.bz2

Re: [OpenWrt-Devel] where is pcdata coming from

2011-08-15 Thread Jo-Philipp Wich
-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

[OpenWrt-Devel] Enabling a config option based on selected target

2011-08-15 Thread Angus Gratton
I've been porting OpenWRT to run on the ZipIt Z2[1] handhelds. For usability purposes the system needs to load a larger console font & a valid keymap at boot time. To make this work seamlessly, I'd ideally like the config system to enable BUSYBOX_CONFIG_LOADFONT & BUSYBOX_CONFIG_LOADKMAP automatic

[OpenWrt-Devel] [PATCH] Update coova-chilli to 1.2.8

2011-08-15 Thread Hanno Schupp
Signed-off-by: Your name Index: Makefile === --- Makefile(revision 27980) +++ Makefile(working copy) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=coova-chilli -PKG_VERSION:=1.2.5 +PKG_VERSION:=1.2.8 PKG_RELEASE

Re: [OpenWrt-Devel] where is pcdata coming from

2011-08-15 Thread Hanno Schupp
After I sent the question I remembered that pcdata is not providing any data - it is just formatting data for output. And the variable model, that is being formatted is coming from luci.sys.sysinfo That function's code makes it all too clear: function sysinfo() local cpuinfo = fs.readfile

[OpenWrt-Devel] where is pcdata coming from

2011-08-15 Thread Hanno Schupp
In the status overview I see the statement <%=pcdata(model or "?")%> which displays the detected router model, if detected. So far so good. Three questions: 1) How can I access the same model data from the bash shell? 2) What other useful data is accessible under pcdata? 3) Which program does this

Re: [OpenWrt-Devel] [PATCH v2 1/1] kmod-input-xxx: missing dependency on kmod-input-core

2011-08-15 Thread Hauke Mehrtens
On 08/15/2011 02:08 AM, Philip Prindeville wrote: > On 8/10/11 12:16 AM, Hauke Mehrtens wrote: >> On 08/06/2011 11:31 PM, Philip Prindeville wrote: >>> On 8/6/11 10:09 AM, Hauke Mehrtens wrote: On 07/28/2011 03:31 AM, Philip Prindeville wrote: > Modules like input-gpio-keys rely on input-c