Hi Stefan,
With your patch, system.hostname is still broken, and you have to reconfigure
all zabbix agent.
I prefer to patch zabbix (if busybox hostname is a nogo)
Regards,
Etienne
Stefan Hellermann a écrit :
>Hi Etienne,
>
>we don't really need busybox hostname, we can read it directly from
Hi Etienne,
yes, "system.hostname" is still broken, and "system.users.num" is also
broken, the last one needs busybox who.
I'm using "agent.hostname" instead of "system.hostname", I don't need
"system.users.num" and deploy my configuration files from a central place.
But you're right, it's probab
* Stefan Hellermann [21.01.2014 10:09]:
> What do the maintainers of openwrt/busybox think? Is it useful to have a
> hostname binary on a router/access point? Maybe for shell scripts or
> some web-interface? If yes, can you add it?
is the applet 'hostname' really just needed for getting the hostn
Hi all,
for the hostname problem we can just update zabbix to 2.2.x
see https://svn.zabbix.com/browse/ZBX-5616
For the who part, is there a way to know the number of connected users in /proc
or ...
- Mail original -
> De: "Bastian Bittorf"
> À: "OpenWrt Development List"
> Envoyé: Mar
Some boards have the WLAN EEPROM stored in flash in big-endian format,
whereas the driver requires the EEPROM in little-endian format. The
conv=swab option in dd is particularly useful in this case. This patch
backports this feature from busybox-1.22.
Signed-off-by: Matti Laakso
---
Index: trunk
ARV752DPW and ARV752DPW22 have the RT2860 eeprom stored in flash as
big-endian, but the driver needs it in little-endian format. We have to
swab it before handing it over. This requires my earlier patch for busybox.
Funnily enough, ARV752DPW works also with the incorrect eeprom, but
undoubtedly un
Hello Matti,
I was the one who sent the patch for getting swab support in busybox.
Here you can find the patch that I sent:
https://dl.dropboxusercontent.com/u/4708147/busybox/bb_swab.patch
However, Denys Vlasenko committed a modified version of the patch because,
according to him, my version wa
Together with other contributors at the now defunct psidoc site, I
have produced a device tree and some patches to get the BT Home Hub 2B
(Lantiq Danube-S) working with recent trunk builds. More work is needed
before they are ready for submitting, but before going any further, I'd
be very grateful
Signed-off-by: Michael Heimpold
---
I sent this patch already upstream to Lennart Poettering, however,
he didn't respond yet.
libs/libdaemon/Makefile|4 +--
.../patches/001-daemon_set_verbosity.patch | 30
2 files changed, 32 insert
> "JC" == John Crispin writes:
JC> * unit most likely runs on a ghz arm soc made by marvell
IIRC, semiaccurate reported that it uses an atom processor.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
openwrt-devel mailing list
openwrt-de
On 21/01/2014 21:35, James Cloos wrote:
>> "JC" == John Crispin writes:
> JC> * unit most likely runs on a ghz arm soc made by marvell
>
> IIRC, semiaccurate reported that it uses an atom processor.
>
> -JimC
> --
> James Cloos OpenPGP: 1024D/ED7DAEA6
i beg to differ, please get your
Hi Ben,
oh dear, how i hate the ebu ...
i will start by testing this patch on the fritz3370 where i have been
seeing jffs2 errors.
in general i am all for merging this, i will need a few days to think
about this.
John
On 21/01/2014 20:50, Ben Mulvihill wrote:
> Together with other contribu
On Tue, 21 Jan 2014, Ben Mulvihill wrote:
The nand driver currently in trunk works fine, provided ...
what is the current status of nand flash support? I asked about this within the
last couple of weeks and was told that supporing devices with nand flash would
require major surgery to the sq
Hi John,
On Jan 21, 2014, at 21:41 , John Crispin wrote:
>
> On 21/01/2014 21:35, James Cloos wrote:
>>> "JC" == John Crispin writes:
>> JC> * unit most likely runs on a ghz arm soc made by marvell
>>
>> IIRC, semiaccurate reported that it uses an atom processor.
That truly was
On Thu, Jan 16, 2014 at 4:32 AM, Aaron Z wrote:
> Perhaps marketing is watching this thread? It now reads:
> "Open Source is a vehicle for other communities, such as DD-WRT, Open WRT,
> and Tomato, to create their own custom versions of open source firmware for
> the product. OpenWRT developers
> "SM" == Sebastian Moeller writes:
SM> That truly was reported on semiaccurate.com as an atom part:
SM>
http://semiaccurate.com/2014/01/06/linksys-wrt1900ac-spritual-successor-wrt54g/
Thanks for finding that!
SM> (but later updated with a correction)
-JimC
--
James Cloos Ope
2014/1/21 Matti Laakso :
> Some boards have the WLAN EEPROM stored in flash in big-endian format,
> whereas the driver requires the EEPROM in little-endian format. The
> conv=swab option in dd is particularly useful in this case. This patch
> backports this feature from busybox-1.22.
Since this is
2014/1/21 James Cloos :
>> "SM" == Sebastian Moeller writes:
>
> SM> That truly was reported on semiaccurate.com as an atom part:
> SM>
> http://semiaccurate.com/2014/01/06/linksys-wrt1900ac-spritual-successor-wrt54g/
>
> Thanks for finding that!
>
> SM> (but later updated with a correcti
Hi John,
Thank you. I had assumed this would probably only be of any use
on the HH2B. If you are going to try it (or bits of it) out on
the fritz3370, I should perhaps add that BTSimonh's patch for
the 3.3.8 kernel (I take it he didn't ever submit it here?)
also reset the chip in the chip select f
I should perhaps have said "provided there are no bad blocks on
the part of the nand occupied by the squashfs", and "provided
that ubox mount_root is patched so that it distinguishes between
jffs2 on nor and jffs2 on nand". But I suspect I shouldn't really
be using a squashfs image on nand at all.
With this new version of zabbix we do not need
uname and hostname anymore, see
https://svn.zabbix.com/browse/ZBX-5616
Only compile tested for now
Signed-off-by: Etienne CHAMPETIER
---
admin/zabbix/Makefile | 10 ++
admin/zabbix/patches/001-cross_compile.pa
On 21/01/2014 21:55, David Lang wrote:
> On Tue, 21 Jan 2014, Ben Mulvihill wrote:
>
>> The nand driver currently in trunk works fine, provided ...
>
> what is the current status of nand flash support? I asked about this
> within the last couple of weeks and was told that supporing devices
> with
Hi,
i am pretty sure the pinmux is set correctly on the board, however i
will reverify it.
do you have a link to btsimonh's 3.3.8 patch ?
John
On 21/01/2014 23:52, Ben Mulvihill wrote:
> Hi John,
>
> Thank you. I had assumed this would probably only be of any use
> on the HH2B. If you are
On Tue, Jan 21, 2014 at 08:50:03PM +0100, Ben Mulvihill wrote:
> Any enlightenment you can provide will be gratefully received.
I have not tested this patch yet but it could be related to your
problem...
Luka
>From ad77bb90cbebcd107e81722e1fbdcff91fe55614 Mon Sep 17 00:00:00 2001
From: Antonio
It was originally posted at
http://sourceforge.net/projects/hh2b4ever/files/
The file is 904-MIPS-lantiq-nand.patch in
http://sourceforge.net/projects/hh2b4ever/files/Patches-20120414.zip
There is also a compilation of bits and pieces from the original
factory firmware, including the nand driver
25 matches
Mail list logo
