Hi Bernhard,
Le jeudi 18 février 2010 12:54:28, Bernhard Loos a écrit :
Hello
This patch adds an pci driver for the rdc southbridge, where the gpio
and wdt config registers are located.
The custom reboot function is needed, beacuse the wdt works by
creating a nmi interrupt, and the normal
On 02/19/2010 08:08 PM, Felix Fietkau wrote:
I disagree with the way manufacturers typically set up board support
packages. Often you have to install something as root, which is annoying
for people that only have user accounts on some machines. Often you can
only have one globally installed
Hi All,
I support a 2mb version for a somewhat different reason. It seems to
me that the base router kernel/boot loader should be VERY small.
It optionally does a 'kexec' to a possibly attached USB/MMC memory
card. In this way router firmware can be totally upgraded. Can be as
large as
2010/2/21 Florian Fainelli flor...@openwrt.org:
Hi Bernhard,
Le jeudi 18 février 2010 12:54:28, Bernhard Loos a écrit :
Hello
This patch adds an pci driver for the rdc southbridge, where the gpio
and wdt config registers are located.
The custom reboot function is needed, beacuse the wdt
Annnd, I forgot to add the patch :/
Sorry about all the noise.
Bernhard
rdc.diff
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
How about the OpenWRT SDK? Is that still supported?
Yes it is still supported and works well.
It also contains a relocatable toolchain, so it doesn't matter where
you unpack it. But it is only suitable for userspace software, iirc it
does not
Le dimanche 21 février 2010 19:38:14, Jo-Philipp Wich a écrit :
Hi.
How about the OpenWRT SDK? Is that still supported?
Yes it is still supported and works well.
It also contains a relocatable toolchain, so it doesn't matter where
you unpack it. But it is only suitable for userspace
On 02/21/2010 07:45 PM, Florian Fainelli wrote:
Yes it is still supported and works well.
It also contains a relocatable toolchain, so it doesn't matter where
you unpack it. But it is only suitable for userspace software, iirc it
does not ship with and is not capable of compiling the
Leonid Evdokimov wrote:
Here is small patch, kerneldoc says:
The ext4 filesystem requires that this feature be enabled in order to
support filesystems that have the huge_file feature enabled [...]
which is enabled by default by mke2fs.ext4.
Without this option dmesg says:
Filesystem
At http://wiki.openwrt.org/inbox/techref/taskinit_discussion I've tried
to start a discussion of a solution to the problem of hotplug and init.d
dependency / race condition problems that exist in OpenWRT today.
If you have some ideas, please add to the page.
Regards,
Daniel
--
And that's my
10 matches
Mail list logo
