Re: [OpenWrt-Devel] [PATCH 2/2] mpc85xx: Add Gianfar PTP as a module

2013-02-20 Thread Wojciech Dubowik
On 02/20/2013 08:15 PM, Gabor Juhos wrote: 2013.02.20. 9:14 keltezéssel, Wojciech Dubowik írta: PTP for gianfar can be built as a module. This part is applied with minor changes. Add device tree entry to P1010RDB to enable ptp as pps clock. However I have skipped this part. Clock timings a

Re: [OpenWrt-Devel] [PATCH 2/2] mpc85xx: Add Gianfar PTP as a module

2013-02-20 Thread Gabor Juhos
2013.02.20. 9:14 keltezéssel, Wojciech Dubowik írta: > PTP for gianfar can be built as a module. This part is applied with minor changes. > Add device tree entry to P1010RDB to enable ptp as pps clock. However I have skipped this part. > Clock timings are not tested. Please resend it as a spe

Re: [OpenWrt-Devel] [PATCH 1/2] kernel: Add Freescale Gianfar driver as a module

2013-02-20 Thread Gabor Juhos
2013.02.20. 9:14 keltezéssel, Wojciech Dubowik írta: > Signed-off-by: Wojciech Dubowik Applied with some changes. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 7:22 PM, Jonh Wendell wrote: > 2013/2/20 Felix Fietkau mailto:n...@openwrt.org>> > > On 2013-02-20 6:57 PM, Jonh Wendell wrote: > > 2013/2/20 Felix Fietkau mailto:n...@openwrt.org> > >> > > > > What I meant was

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: Supports IdleTimeout uci config option

2013-02-20 Thread Jonh Wendell
Hi, I just rebased against trunk and changed the patch to use procd as well. From: Jonh Wendell Date: Thu, 6 Sep 2012 16:45:29 -0300 Subject: [PATCH] [package] dropbear: Supports IdleTimeout uci config option Signed-off-by: Jonh Wendell --- package/network/services/dropbear/files/dropbear.init

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Felix Fietkau > On 2013-02-20 6:57 PM, Jonh Wendell wrote: > > 2013/2/20 Felix Fietkau mailto:n...@openwrt.org>> > > > > What I meant was: why do you need to rename the resolv.conf file? > > > > > > Ahh. Because I don't want to use the dns servers dhcp gives to me. > You don't need

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 6:57 PM, Jonh Wendell wrote: > 2013/2/20 Felix Fietkau mailto:n...@openwrt.org>> > > What I meant was: why do you need to rename the resolv.conf file? > > > Ahh. Because I don't want to use the dns servers dhcp gives to me. You don't need to modify anything scripts for that. Ju

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Jo-Philipp Wich > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Ahh. Because I don't want to use the dns servers dhcp gives to me. > > What about simply setting "option peerdns 0" on the dhcp interface then? > hmmm, I hadn't seen this option. So, netifd reads that option... int

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Ahh. Because I don't want to use the dns servers dhcp gives to me. What about simply setting "option peerdns 0" on the dhcp interface then? ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Felix Fietkau > What I meant was: why do you need to rename the resolv.conf file? > Ahh. Because I don't want to use the dns servers dhcp gives to me. > - Felix > > On 2013-02-20 6:45 PM, Jonh Wendell wrote: > > Because in my environment I need to pass some args to netifd (like -r).

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
What I meant was: why do you need to rename the resolv.conf file? - Felix On 2013-02-20 6:45 PM, Jonh Wendell wrote: > Because in my environment I need to pass some args to netifd (like -r). > Right now, I'm patching /etc/init.d/network. The patch proposes a less > intrusive solution. > > It's b

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
Because in my environment I need to pass some args to netifd (like -r). Right now, I'm patching /etc/init.d/network. The patch proposes a less intrusive solution. It's based on what other modules, like net-snmp do. 2013/2/20 Felix Fietkau > On 2013-02-20 6:32 PM, Jonh Wendell wrote: > > If tha

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Bastian Bittorf
* Jonh Wendell [20.02.2013 18:41]: > +[ -f $DEFAULT ] && . $DEFAULT > +service_start /sbin/netifd $OPTION this is not pretty, nifty and simple. (but must be!) use: [ -f "$DEFAULT" ] && read OPTIONS <"$DEFAULT" why should the user need to know your variable name. this passes the content

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 6:32 PM, Jonh Wendell wrote: > If that file exists, read it and pass the content > of the OPTIONS variable to netifd daemon. > > For instance, this would be a valid content for this file: > OPTIONS="-r /tmp/resolv.XXX" > > Signed-off-by: Jonh Wendell Why do you need this? - Felix

[OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
If that file exists, read it and pass the content of the OPTIONS variable to netifd daemon. For instance, this would be a valid content for this file: OPTIONS="-r /tmp/resolv.XXX" Signed-off-by: Jonh Wendell --- package/network/config/netifd/files/etc/init.d/network |5 - 1 file changed

Re: [OpenWrt-Devel] [hard floating point]

2013-02-20 Thread Florian Fainelli
Alberich, On 02/20/2013 03:53 PM, Florian Fainelli wrote: Hello Alberich, On 02/20/2013 02:46 PM, Alberich de megres wrote: Hi Florian, I think you are right: the point is the toolchain. At the moment we could not release anything. The toolchain targets a normal glibc, I was expecting buildro

Re: [OpenWrt-Devel] [hard floating point]

2013-02-20 Thread Florian Fainelli
Hello Alberich, On 02/20/2013 02:46 PM, Alberich de megres wrote: Hi Florian, I think you are right: the point is the toolchain. At the moment we could not release anything. The toolchain targets a normal glibc, I was expecting buildroot would interpert it, or at least give the oportunity to us

Re: [OpenWrt-Devel] Linksys E4200v1 Support

2013-02-20 Thread Tijs Van Buggenhout
On Wednesday 20 February 2013 14:11:53 Hauke Mehrtens wrote: > On 02/18/2013 10:51 AM, Tijs Van Buggenhout wrote: > > On Monday 18 February 2013 04:30:14 Chirag Chhatriwala wrote: > > > > Tijs: > > > > Are you using your settings on vlan0ports & vlan1ports > > OR > > > > vlan1ports & vlan2ports

[OpenWrt-Devel] Lantiq - Ath9k eeprom data

2013-02-20 Thread Elliott Rose
The Ath9K radio on the BTHH2B board, Lantiq Xway Danube 50712, requires eeprom calibration/fixup data which is stored on the first 16k of NAND flash. The data amounts to some 3137 bytes, the remainder are 00. I have rev 1.3 and 1.5 boards and these data are identical on both - the Mac address i

Re: [OpenWrt-Devel] Linksys E4200v1 Support

2013-02-20 Thread Cezary Jackiewicz
Dnia 2013-02-20, o godz. 14:11:53 Hauke Mehrtens napisał(a): > On my e3200 Ethernet works with the default config. Are there more > problems discussed in this tread? On my e3200 also ethernet seems to work, but often hangs up with: [ 121.98] bgmac bcma0:1: Hardware reported transmission fo

Re: [OpenWrt-Devel] [hard floating point]

2013-02-20 Thread Alberich de megres
Hi Florian, I think you are right: the point is the toolchain. At the moment we could not release anything. The toolchain targets a normal glibc, I was expecting buildroot would interpert it, or at least give the oportunity to use different libc than uclibc when using an external toolchain, as whe

Re: [OpenWrt-Devel] Linksys E4200v1 Support

2013-02-20 Thread Hauke Mehrtens
On 02/18/2013 10:51 AM, Tijs Van Buggenhout wrote: > On Monday 18 February 2013 04:30:14 Chirag Chhatriwala wrote: > > Tijs: > > Are you using your settings on vlan0ports & vlan1ports > OR > > vlan1ports & vlan2ports > > I had a glance at vlanports assignment in OpenWRT, Tomato and DD-WRT and >

Re: [OpenWrt-Devel] [hard floating point]

2013-02-20 Thread Florian Fainelli
Hello Alberich, On 02/19/2013 04:06 PM, Alberich de megres wrote: Hi FLorian, The board contains a Broadcom SoC similar to the one in the raspberry pi (not the same), we have a kernel working for it, but when tryingo to port the openwrt all blowed up. For the moment I did: (it is a work in pro

Re: [OpenWrt-Devel] android rootfs using proot and openwrt

2013-02-20 Thread Petr Štetiar
hhm [2013-02-17 23:29:11]: > I just put online a small project. It uses OpenWrt for the rootfs, > which is one of its main components. More info and downloads are at > https://sites.google.com/site/taldewandroid/ > > Any feedback, questions, comments etc. would be appreciated :-). Hi, I'm mayb

[OpenWrt-Devel] [PATCH 1/2] kernel: Add Freescale Gianfar driver as a module

2013-02-20 Thread Wojciech Dubowik
Signed-off-by: Wojciech Dubowik --- package/kernel/modules/netdevices.mk | 34 ++ 1 file changed, 34 insertions(+) diff --git a/package/kernel/modules/netdevices.mk b/package/kernel/modules/netdevices.mk index aec4948..df4d571 100644 --- a/package/kernel/module

[OpenWrt-Devel] [PATCH 2/2] mpc85xx: Add Gianfar PTP as a module

2013-02-20 Thread Wojciech Dubowik
PTP for gianfar can be built as a module. Add device tree entry to P1010RDB to enable ptp as pps clock. Clock timings are not tested. Signed-off-by: Wojciech Dubowik --- package/kernel/modules/other.mk | 17 + .../patches-3.7/140-p1010rdb-dts-ptp-timer.pa