Re: [OpenWrt-Devel] rdc gpio and watchdog driver
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 reboot fixups don't work in irq context. So we still need the reboot fixup if I understand correctly? The code in platfrom.c is rather messed up at the moment, I plan to clean this up later. Yes, we will need to clean that up. There are also some kernel patches missing, one that removes the original wdt driver, and something that removes the rdc reboot fixup and removes the dependencie of rdc from the x86 reboot fixups in the Kconfig file, but the patch should work just fine without those. I have tested your patch but the watchdog driver did not trigger a reboot on my AR525W. Do you have a patch to get watchdog working yet? -- Best regards, Florian Fainelli Email: flor...@openwrt.org Web: http://openwrt.org IRC: [florian] on irc.freenode.net --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Compiling outside of buildroot
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 instance of the SDK, which makes it annoying to support multiple different versions, or even just multiple minor variations of the toolchain. That's true, but for most of people it is a convenient way to just have to install an SDK and start developing. One issue with pre-compiled SDK's is gcc hardcoded absolute paths to libraries that make relocation difficult. There are scripts that change the absolute paths to relative one. Then it is possible to install a precompiled SDK in the user accessible location you want. With OpenWRT, it is possible to have multiple different version installed at the same time. You can simply choose a different location for every variant where you build OpenWRT, e.g. build one in /opt/OpenWRT/platform/variant1 and another one in /opt/OpenWRT/platform/variant2 By sourcing a (to be written) script say /opt/OpenWRT/platform/the_variant/settings.rc you switch between different variants. Why do you want to call it outside of the tree? You can keep your packages as a separate feed, which makes it easy to keep track of your own work without having to fully integrate it into the OpenWrt tree. Personally, I like a complete separation between open source and propriety code. So when developing propriety code which uses OpenWRT as a platform, I prefer to use a fixed tree of OpenWRT stuff (packaged and installed somewhere) and have an entirely separate tree of propriety code in which I can simply call make. Then the resulting binaries, kmods and images should land somewhere in my propriety tree. Please note that I'm not saying that the system with the feeds is not working properly! I just want to offer an OpenWRT based SDK for a certain board (including kernel headers and .config actually) as an easy to install package and an archive with only the propriety stuff. One then only needs to install the SDK, unpack the archive with the propriety code and run make. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 2mb flash not OpenWRT-Target?
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 needed. A known good version can be on one card and an under development on another. And so on. It's a MUCH better development model. Wiz On Sat, 20 Feb 2010, Daniel Dickinson wrote: [NON-Text Body part not included] ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] rdc gpio and watchdog driver
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 works by creating a nmi interrupt, and the normal reboot fixups don't work in irq context. So we still need the reboot fixup if I understand correctly? No, only the code in reboot.c. Which I forgot to add to svn ... I attached a new patch including it. The code in platfrom.c is rather messed up at the moment, I plan to clean this up later. Yes, we will need to clean that up. There are also some kernel patches missing, one that removes the original wdt driver, and something that removes the rdc reboot fixup and removes the dependencie of rdc from the x86 reboot fixups in the Kconfig file, but the patch should work just fine without those. I have tested your patch but the watchdog driver did not trigger a reboot on my AR525W. Do you have a patch to get watchdog working yet? With the reboot.c file, it should work. -- Best regards, Florian Fainelli Email: flor...@openwrt.org Web: http://openwrt.org IRC: [florian] on irc.freenode.net --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] rdc gpio and watchdog driver
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
Re: [OpenWrt-Devel] Compiling outside of buildroot
-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 ship with and is not capable of compiling the kernel sources. ~ JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuBfZUACgkQdputYINPTPPT2ACfYM2yIS3pRMwpfC+HaoYg25jX 5cgAoJQ/VAkfSL2KBqlh09LuSzV+D0NC =+zBM -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Compiling outside of buildroot
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 software, iirc it does not ship with and is not capable of compiling the kernel sources. You can however, use the compiled and relocatable toolchain in the SDK to compile other kernel sources (vanilla, git ...) -- Best regards, Florian Fainelli Email: flor...@openwrt.org Web: http://openwrt.org IRC: [florian] on irc.freenode.net --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Compiling outside of buildroot
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 kernel sources. You can however, use the compiled and relocatable toolchain in the SDK to compile other kernel sources (vanilla, git ...) So if the kernel headers and config are added to the SDK, one could compile out of tree kmods too? Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ext4 driver requires CONFIG_LBD for most of ext4 partitions
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 with huge files cannot be mounted read-write without CONFIG_LBD. while mounting ext4 partition. I tested ext4 with linux-2.6.30.10 kernel. _Seems_, relevant option was renamed to CONFIG_LBDAF in later kernels. Hello Leonid, a patch fixing this issue was applied in trunk in r19799 ( https://dev.openwrt.org/changeset/19799 ) Hauke signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Hotplug / Init Race Conditions, Discussion
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 crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
