On 06/17/2011 10:54 PM, Aleksandar Radovanovic wrote:
On 06/17/2011 11:49 AM, D.S. Ljungmark wrote:
On Thu, 2011-06-16 at 19:49 +0200, Ithamar R. Adema wrote:
Hi,
On Thu, 2011-06-16 at 12:21 +0200, Jo-Philipp Wich wrote:
Maybe calling "reboot" at all is not such a great idea as i
On 06/17/2011 11:49 AM, D.S. Ljungmark wrote:
> On Thu, 2011-06-16 at 19:49 +0200, Ithamar R. Adema wrote:
>> Hi,
>>
>> On Thu, 2011-06-16 at 12:21 +0200, Jo-Philipp Wich wrote:
>>> Maybe calling "reboot" at all is not such a great idea as it
>>> attempts to run the (former) init scripts to stop th
Add support for cores with slow WDT clock (bcm5354)
Signed-off-by: Aleksandar Radovanovic
---
patches-2.6.32/900-bcm47xx_wdt-noprescale.patch | 89
patches-2.6.34/900-bcm47xx_wdt-noprescale.patch | 89
patches-2.6.35/900-bcm47xx_wdt
Hi all,
The following patch should finally fix the problem with bcm47xx watchdog
not working on some cores. So far, only bcm5354 based routers seem to be
affected, but there may be others I missed. Would appreciate if people
could give it a quick test on other chips and report if it's still not
wo
Hi Neo,
After creating a server socket in your program, set the FD_CLOEXEC file
descriptor flag on it, i.e. add something like
fcntl(sock, F_SETFD, FD_CLOEXEC);
The reason why this is happening is that, on *nix, by default, when you
create a child process using fork() and exec() (or system(), wh
have a patch
ready in a few days.
Regards,
Aleksandar
On 09/25/2010 07:57 PM, Alexey Loukianov wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> 25.09.2010 22:41, Aleksandar Radovanovic wrote:
>
>> Well, the thing is, I'm the developer of the original d
SSAGE-
> Hash: SHA1
>
> 25.09.2010 21:38, Aleksandar Radovanovic wrote:
>
>> Re the patch, I agree - applying that patch will effectively turn the
>> driver into a softdog.
>>
> To be honest: bcrm47xx_wdt driver isn't a hardware watchdog either
Hi Alexey,
I just tested the latest trunk (r23118) on my Asus WL-500gP v1 and can
confirm that the watchdog reset still works.
I also have a WL-500gP v2 in the office, which should (according to the
OpenWRT wiki) have the same SoC (BCM5354) as your D-Link. I'll give it a
try on Monday and let you
Anyone?
On 11/18/2009 08:36 PM, Aleksandar Radovanovic wrote:
> Fix a memory leak in hotplug2 environment handling.
> Bump hotplug2 to the latest svn revision, remove obsolete patches.
>
> Memory leak is caused by the way hotplug2 handles environment variables,
> using setenv
bserved by running "udevtrigger" and
noting the increase in hotplug2 VmRSS after each run.
This patch uses putenv() instead, which leaves storage management to
the caller, so that we can explicitly delete stuff when it's no longer
needed.
Signed-off-by: Aleksandar Rad
Hi all,
Tried compiling the current trunk for bcm47xx (and a couple of other
targets too) with 2.6.31.5 kernel and have hit a snag with jffs2 whiteouts.
Even though I use a plain jffs2 image (no union mounts, no mini_fo) and
my kernel .config indicates that CONFIG_UNION_MOUNT is off, the
filesyst
Hi all,
A common workaround for this is to use
[ "x$var" == "x" ] instead of [ -z "$var" ]
and
[ "x$var" != "x" ] instead of [ -n "$var" ]
which doesn't exhibit the mentioned problem.
Regards,
Aleksandar
Alina Friedrichsen wrote:
> Hi!
>
>
>> Thanks for explaining.. this makes perfectly s
Hi Matthieu,
I've written one for a pet project I've been working on a few months
back, but I never submitted a patch, shame on me :)
It has not been extensively tested and I don't know if there are any
better implementations floating around.
If you're interested in having a play with it, I'll t
Hi Florian,
Florian Fainelli wrote:
> Hi Aleksandar,
>
> Le Wednesday 21 January 2009 13:02:19 Aleksandar Radovanovic, vous avez
> écrit :
>
>> Hi,
>>
>> I'm trying to write a driver for my wl-500gP to export the watchdog
>> timer on BCM4712 to user
Hi,
I'm trying to write a driver for my wl-500gP to export the watchdog
timer on BCM4712 to userspace, via /dev/watchdog.
Since I have no access to chip datasheets, I've been digging through
SSB code, trying to figure out a a way to manipulate the watchdog.
The problem is that, if I use ssb_watc
Ok, great! This one was one of mine, just noticed it still hanging
around. Anyway, it's safe to remove it...
Cheers,
Aleksandar
Peter Denison wrote:
> On Fri, 9 May 2008, Aleksandar Radovanovic wrote:
>
>
>> Remove target/linux/brcm47xx/patches-2.6.25/410-aec62xx_pci_
Remove target/linux/brcm47xx/patches-2.6.25/410-aec62xx_pci_enable.patch
It's been included in the mainline since 2.6.24
Signed-off-by: Aleksandar Radovanovic <[EMAIL PROTECTED]>
Index: target/linux/brcm47xx/patches-2.6.25/410-aec62xx_pci_e
17 matches
Mail list logo
