[OpenWrt-Devel] [PATCH 5/5] [package/udev] Add udev tools package

2008-03-19 Thread Jeremy Kerr
This change adds a sub-package 'udevtools' build from the udev sources. This includes the utilities: ata_id cdrom_id dasd_id scsi_id path_id usb_id volume_id And installs the generic udev rules distributed in the lib/udev dir. Installing this package will set up the pe

[OpenWrt-Devel] [PATCH 3/5] [package/kexec] Use new kexec tools

2008-03-19 Thread Jeremy Kerr
Horms' new kexec-tools repository has a number of updates and fixes for kexec, and also supports the PS3. This change updates the kexec repo, and adds a few build-system patches to make it work with OpenWRT. Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]> --- package/kexec-tools/Makefile

[OpenWrt-Devel] [PATCH 1/5] [target/ps3] Bump kernel version to 2.6.24

2008-03-19 Thread Jeremy Kerr
2.6.24 has some kexec changes that are useful for ps3, so update. This requires a patch to fix a build error with CONFIG_KEXEC && !CONFIG_DEBUGGER. Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]> --- target/linux/generic-2.6/patches-2.6.24/701-fix-compilation-for-CONFIG_DEBUGGER=n-and-CONFIG_KEX

[OpenWrt-Devel] [PATCH 2/5] [toolchain] provide a cleaner way to specify a biarch toolchain build

2008-03-19 Thread Jeremy Kerr
Currently, to build a biarch toolchain, we need to explicitly give options to the binutils and gcc configure commands: CONFIG_EXTRA_BINUTILS_CONFIG_OPTIONS="--enable-targets=powerpc64-linux-uclibc" CONFIG_EXTRA_GCC_CONFIG_OPTIONS="--enable-biarch --enable-targets=powerpc64-linux-uclibc" This cha

[OpenWrt-Devel] [PATCH 4/5] [package/udev] Group input devices under /dev/input

2008-03-19 Thread Jeremy Kerr
This change adds a udev rules file to group input devices (via symlinks) under their usual expected location of /dev/input. Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]> --- package/udev/Makefile |2 ++ package/udev/files/20-input-grouping.rules |9 + 2 file

Re: [OpenWrt-Devel] Dynamic modules for Apache + php5 module

2008-03-19 Thread Michael
On Tue, 18 Mar 2008 12:06:57 am Stefan Monnier wrote: > > Question: Why the #@&* would you want apache with php5 on your router? > > > > Answer: There are a few configuration tools around for things like xmail > > and asterisk that I wanted to play around with.. that happen to be > > written in ph

[OpenWrt-Devel] [PATCH] Package Makefile for faad2

2008-03-19 Thread Cortland Setlow
This makefile works to build a fixed-point version of faad2 that supports AAC low complexity. An mpd using it takes about 10% CPU on my Asus WL500g Premium. However, this makefile fails to package the faad2 properly and the shared library must be manually installed. The modification of mpd's

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, nööh wrote: > Robert P. J. Day schrieb: > >> Updating feed 'ifx_feeds' from '${TOPDIR}/../ifx_feeds' ... > >> Create index file './feeds/ifx_feeds.index' > >> Collecting package info: done > > > > ?. i have no idea where *those* lines are coming from. my > > output ends

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread nööh
Robert P. J. Day schrieb: >> Updating feed 'ifx_feeds' from '${TOPDIR}/../ifx_feeds' ... >> Create index file './feeds/ifx_feeds.index' >> Collecting package info: done > > ?. i have no idea where *those* lines are coming from. my > output ends with the xwrt stuff. what does *that* stuff re

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, [EMAIL PROTECTED] wrote: > hello Robert, > > pls see below my steps ... > > $ rm -Rf package/feeds/ ah, that might have been my problem, as doing a "make distclean" doesn't get rid of that directory, which it should, no? and the fact that it was still there certainly screwed

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Ralph.Hempel
hello Robert, > which confuses me since i thought the point of the new > symlinks creation process was to create just directory level > symlinks, not all those lower-level, individual symlinks on a > per-package basis, but that's what's happening here. This approach allows you to install only ded

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Ralph.Hempel
hello Robert, pls see below my steps ... $ rm -Rf package/feeds/ $ rm -Rf tmp/ $ scripts/feeds update -a Updating feed 'packages' from 'https://svn.openwrt.org/openwrt/packages' ... At revision 10627. Create index file './feeds/packages.index' Collecting package info: done Updating feed 'xwrt' fr

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, [EMAIL PROTECTED] wrote: > hi, > > > > As far as I understood the feeds concept, you are supposed link in > > > individual packages from the feeds, using > > > > > > $ scripts/feeds search > > > $ scripts/feeds install ... > > in the meantime the symlink target should be chan

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, Robert P. J. Day wrote: > On Wed, 19 Mar 2008, [EMAIL PROTECTED] wrote: > > > hi, > > > > > > As far as I understood the feeds concept, you are supposed link in > > > > individual packages from the feeds, using > > > > > > > > $ scripts/feeds search > > > > $ scripts/feeds in

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, [EMAIL PROTECTED] wrote: > hi, > > > > As far as I understood the feeds concept, you are supposed link in > > > individual packages from the feeds, using > > > > > > $ scripts/feeds search > > > $ scripts/feeds install ... > > in the meantime the symlink target should be chan

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Ralph.Hempel
hi, > > As far as I understood the feeds concept, you are supposed link in > > individual packages from the feeds, using > > > > $ scripts/feeds search > > $ scripts/feeds install ... in the meantime the symlink target should be changed in such way, package/symlinks: - $(SCRIPT_DIR)/feed

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, Harald Schiöberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > > > p.s. i looked for a config option that might control the above but > > didn't see one. perhaps a build option along the lines of: > > > > Additional feeds you'd like to use? > > [ ] o

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Harald Schiöberg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert P. J. Day wrote: >> but I also share the opionion that somehow integrating this in the >> config system would be beneficial. > > it's not that it's a big deal, so much that the current situation is > simply inconsistent -- processing all src e

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, Harald Schiöberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > p.s. i looked for a config option that might control the above > > but didn't see one. perhaps a build option along the lines of: > > > > Additional feeds you'd like to use? > > [ ] openwrt

Re: [OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Harald Schiöberg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > p.s. i looked for a config option that might control the above but > didn't see one. perhaps a build option along the lines of: > > Additional feeds you'd like to use? > [ ] openwrt > [ ] xwrt > > and so on. or have i totally misun

[OpenWrt-Devel] should "make package/symlinks" process xwrt symlinks as well?

2008-03-19 Thread Robert P. J. Day
just being my normally pedantic self (you must be getting used to that by now) but, after i do a configuration and a "make package/symlinks", i notice (of course) that i now have the symlink: package/openwrt-packages -> ../feeds/packages fair enough, but the feeds/packages/ directory corresp

[OpenWrt-Devel] [PATCH] "make distclean" should remove the "openwrt-packages" symlink.

2008-03-19 Thread Robert P. J. Day
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> --- if you're removing the entire feeds directory, it would seem to make sense to delete that symlink as well. diff --git a/include/toplevel.mk b/include/toplevel.mk index 2094e2f..45cde9f 100644 --- a/include/toplevel.mk +++ b/include/tople

Re: [OpenWrt-Devel] dev.openwrt.org doesn't mention svn checkout of "packages" branch

2008-03-19 Thread Robert P. J. Day
On Wed, 19 Mar 2008, Gregers Petersen wrote: > Robert P. J. Day wrote: > > just noticed that, in the instructions for checking out the dev > > branches on the https://dev.openwrt.org/ page, the git checkout > > instructions mention both branches, but the svn instructions mention > > only trunk,

Re: [OpenWrt-Devel] dev.openwrt.org doesn't mention svn checkout of "packages" branch

2008-03-19 Thread Florian Fainelli
Hi, Le mercredi 19 mars 2008, Robert P. J. Day a écrit : > just noticed that, in the instructions for checking out the dev > branches on the https://dev.openwrt.org/ page, the git checkout > instructions mention both branches, but the svn instructions mention > only trunk, not packages. just an

Re: [OpenWrt-Devel] dev.openwrt.org doesn't mention svn checkout of "packages" branch

2008-03-19 Thread Gregers Petersen
Robert P. J. Day wrote: > just noticed that, in the instructions for checking out the dev > branches on the https://dev.openwrt.org/ page, the git checkout > instructions mention both branches, but the svn instructions mention > only trunk, not packages. just an oversight? Try to read a little

[OpenWrt-Devel] dev.openwrt.org doesn't mention svn checkout of "packages" branch

2008-03-19 Thread Robert P. J. Day
just noticed that, in the instructions for checking out the dev branches on the https://dev.openwrt.org/ page, the git checkout instructions mention both branches, but the svn instructions mention only trunk, not packages. just an oversight? rday -- ===

Re: [OpenWrt-Devel] what is the purpose of "make symlinkclean"?

2008-03-19 Thread Felix Fietkau
Robert P. J. Day wrote: > i can see how it's defined in include/toplevel.mk: > > ... > symlinkclean: > -find package -type l | xargs rm -f > rm -rf tmp > ... > > but under what circumstances would you use it? it would clearly > remove, say, the "openwrt-packages" symlink under

Re: [OpenWrt-Devel] [PATCH] Make SDK and imagebuilder *not* dependent on all packages.

2008-03-19 Thread Felix Fietkau
Robert P. J. Day wrote: > Detach the building of sdk and imagebuilder from "Select all packages > by default", since those really represent two distinct build > operations from normal package selection. > > Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> Committed in r10621 - Felix __

Re: [OpenWrt-Devel] [PATCH] PPS-tools

2008-03-19 Thread Felix Fietkau
Frithjof Hammer wrote: > This patch contains a package with two PPS-tools and a header file, > i extracted from http://wiki.enneenne.com/index.php/LinuxPPS_support. > > Signed-off-by: Frithjof Hammer <[EMAIL PROTECTED]> Committed (with modifications) in r10620 - Felix ___

Re: [OpenWrt-Devel] [PATCH] linux-pps

2008-03-19 Thread Felix Fietkau
Frithjof Hammer wrote: > This Patch adds PPS (Pulse per Second) Support to Openwrt 2.6.23 > (its deprecated before 2.6.23). Its common to use PPS to sync your > PC Clock with GPS or DCF77 clocks via NTPd. > > I've taken this Patch from http://wiki.enneenne.com/index.php/LinuxPPS_support > > Sig