Re: [OpenWrt-Devel] how to stop a inittab service without reboot

Has inittab a higher prio or is inittab simply the oldest way of starting a service? Thanks, Claudio On 19.10.2015 11:28, John Crispin wrote: > there is no dynamic reload feature for this in procd yet > > > On 19/10/2015 11:20, Claudio Thomas wrote: >> Hi, >> on my /etc/ini

Re: [OpenWrt-Devel] how to stop a inittab service without reboot

that's what I was assuming :-( thanks a lot, Claudio On 19.10.2015 11:28, John Crispin wrote: > there is no dynamic reload feature for this in procd yet > > > On 19/10/2015 11:20, Claudio Thomas wrote: >> Hi, >> on my /etc/inittab I've the following line

[OpenWrt-Devel] how to stop a inittab service without reboot

Hi, on my /etc/inittab I've the following line ttyQE1::askfirst:/bin/ash --login I've already removed the line and killed the process, but its restarts again. I know that commenting it out and rebooting is a way to stop this "service", but is there a way to stop it without rebooting? Like som

[OpenWrt-Devel] CC-release kernel version

On 09.04.2015 15:44, Michael Richardson wrote: > And, it would be be nice if all the "drivers" were up-to-date... :- which will be the CC-release kernel version? 3.18? Thanks, Claudio -- Working on OpenWrt CC for Xmodus GSM Router XM1710E __

Re: [OpenWrt-Devel] Designated Driver

+1 On 07.04.2015 21:47, Hartmut Knaack wrote: > That Doodle poll turned out to be spamed/trolled, and everyone could even > change or delete other votes. Since this was just communicated over this > mailing list, and subscribers are at least basically verified, why not have a > good old fashioned

Re: [OpenWrt-Devel] How to Custom admin page on openwrt ?

On 12.03.2015 09:45, Tymon wrote: > > Thank you for your answer, Claudio Thomas: > > I use the default utility called dnsmasq ( a light-weigh > dns server and dhcp server) on openwrt 12.09. > Of course the dhcp-server function is enabled and > PC-wi

Re: [OpenWrt-Devel] How to Custom admin page on openwrt ?

On 12.03.2015 08:24, Tymon wrote: > > *Hi all,* > > * As we all known, the default method to access the router's > administration web page(Luci) is to type "http://192.168.1.1 > " on the browser. I am curious about how can the > router recognize the"http://192.168.1.1 <

Re: [OpenWrt-Devel] minimal work needed to build just the toolchain

> errors but Im try to use other way to build the firmware if i get > problem in it i will tell you and i wait your reply > > 2015-03-04 18:23 GMT+02:00 Claudio Thomas <mailto:c...@xmodus-systems.de>>: > > On 03.03.2015 13:17, John Crispin wrote: >> On

Re: [OpenWrt-Devel] minimal work needed to build just the toolchain

On 03.03.2015 13:17, John Crispin wrote: > On 03/03/2015 12:27, Claudio Thomas wrote: >> Hi, >> >> the same question was already discussed on 2008-01, but it seems to me, >> that some iterim steps are no more necessary... I guess that there has >> been some impr

[OpenWrt-Devel] minimal work needed to build just the toolchain

Hi, the same question was already discussed on 2008-01, but it seems to me, that some iterim steps are no more necessary... I guess that there has been some improvements made in the last 7 years :-) Therefore, I would thankful for a confirmation of my assumption. Actually I do the following: 1. m

Re: [OpenWrt-Devel] barrier breaker 14.07 stable release location

Hi Madhu, the releases of OpenWrt firmwares can be found at http://downloads.openwrt.org/. For BB 14.07 stable for example http://downloads.openwrt.org/barrier_breaker/14.07/. But to get the right firmware for your device you need to know what target and profile you need. To find out if there is

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

Hi, do I understand it correctly. For CC is 3.14 planed? Thanks, Claudio -- Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router On 05.12.2014 09:07, John Crispin wrote: > i intentionally don't set a date. i have done so in the p

Re: [OpenWrt-Devel] jffs takes about 18 minutes to get ready on 3.10 kernel (probably solved)

Hi, On 29.10.2014 23:32, Claudio Thomas wrote: > On 29.10.2014 13:37, Bastian Bittorf wrote: >> * Claudio Thomas [29.10.2014 13:18]: >>> [ 800.742671] jffs2: notice: (888) jffs2_build_xattr_subsystem: >> how large is the partitionsize? > "rootfs_data" cre

Re: [OpenWrt-Devel] jffs takes about 18 minutes to get ready on 3.10 kernel

On 29.10.2014 13:37, Bastian Bittorf wrote: > * Claudio Thomas [29.10.2014 13:18]: >> [ 800.742671] jffs2: notice: (888) jffs2_build_xattr_subsystem: > how large is the partitionsize? "rootfs_data" created automatically, ofs=0x96, len=0x326 > while we are at i

[OpenWrt-Devel] jffs takes about 18 minutes to get ready on 3.10 kernel

Hi, compiling/installing the same sources+config, but with 3.8 kernel all is fine... But when compilng with 3.10 the jffs takes about 18 minutes to get ready: [ 2.655217] Freeing unused kernel memory: 160K (c045f000 - c0487000) procd: Console is alive procd: - preinit - Press the [f] key and hi

[OpenWrt-Devel] alternative for "pyserial+python-mini"

Hi, "python-mini" is missing in oldpackages (trunk), is there an alternative for "python-mini"? I need it for pyserial, which depends on "python-mini", and still exists in oldpackages (trunk). What about "micropython+micropython-lib"? Has anyone already tested this as replacement? Thanks, Claudio

Re: [OpenWrt-Devel] git.infradead.org offline? mirror for mtd-utils-1.4.5?

Thanks a lot, Claudio -- Working on OpenWrt BB for XM1700E <http://www.xmodus-systems.de/en/terminals/routers.html> On 24.10.2014 10:11, Bastian Bittorf wrote: > * Claudio Thomas [24.10.2014 10:08]: >> ist there somewhere a mirror for mtd-utils-1.4.5? git.infradead.org >

[OpenWrt-Devel] git.infradead.org offline? mirror for mtd-utils-1.4.5?

Hi, ist there somewhere a mirror for mtd-utils-1.4.5? git.infradead.org seems to be (temporary) dead: Cloning into 'mtd-utils-1.4.5'... fatal: unable to connect to git.infradead.org: git.infradead.org: Name or service not known Thanks, Claudio -- Working on OpenWrt BB for XM1700E

[OpenWrt-Devel] best or common place to save the devicetree

Hi, where is the best or common place to save the devicetree-source-code? Some projects (like brcm63xx) save them as a file in the target/subdirectory "dts/" and other projects it is saved as a kernel patch... Thanks, Claudio -- Working on OpenWrt BB for XM1700E

Re: [OpenWrt-Devel] naming for new subtarget in mpc83xx

Hi Imre, On 23.09.2014 11:54, Claudio Thomas wrote: > On 23.09.2014 11:41, Imre Kaloz wrote: >> On Tue, 23 Sep 2014 11:10:17 +0200, Claudio Thomas >> wrote: >> >> >> Well, RB333 is MPC8321, RB600 is MPC8323 and we support the >> MPC8377EWLAN board, which

Re: [OpenWrt-Devel] naming for new subtarget in mpc83xx

Hi Imre, On 23.09.2014 11:41, Imre Kaloz wrote: > > On Tue, 23 Sep 2014 11:10:17 +0200, Claudio Thomas > wrote: > > > >> The RB600/RB300 uses a MPC8377, the XM1700 uses a MPC8306. They are >> quite similar, but not equal. > > Well, RB333 is MPC8321,

Re: [OpenWrt-Devel] naming for new subtarget in mpc83xx

Hi Imre, On 23.09.2014 09:53, Imre Kaloz wrote: > Hi Claudio, > > On Tue, 23 Sep 2014 09:44:03 +0200, Claudio Thomas > wrote: > >> I would like to add a new device to /target/linux/mpc83xx witch needs a >> special kernel. > > In what way is it special? Why c

[OpenWrt-Devel] naming for new subtarget in mpc83xx

Hi, I would like to add a new device to /target/linux/mpc83xx witch needs a special kernel. As I see in other targets this is done usually by adding a first subtarget, moving the actual config to it and adding a a first profile. Is there a special naming convention for the first subtarget? Should

Re: [OpenWrt-Devel] Missing mpc83xx in BB-RC3

On 16.09.2014 18:45, Hauke Mehrtens wrote: > On 09/16/2014 02:52 PM, Claudio Thomas wrote: >> On 16.09.2014 14:44, Felix Fietkau wrote: >>> On 2014-09-16 13:47, Claudio Thomas wrote: >>>> Hi, >>>> I until now was still using the trunk for testing an

Re: [OpenWrt-Devel] Missing mpc83xx in BB-RC3

On 16.09.2014 14:44, Felix Fietkau wrote: > On 2014-09-16 13:47, Claudio Thomas wrote: >> Hi, >> I until now was still using the trunk for testing and working, but today >> I the first time checked out the 14.07/openwrt.git at git.openwrt.git. >> Is there a reason why MP

[OpenWrt-Devel] Missing mpc83xx in BB-RC3

Hi, I until now was still using the trunk for testing and working, but today I the first time checked out the 14.07/openwrt.git at git.openwrt.git. Is there a reason why MPC83xx is not included in BB-RC3? Best regards, Claudio ___ openwrt-devel mailing l

Re: [OpenWrt-Devel] Moving all feeds to OpenWrt GitHub organisation

Hi, On 10.08.2014 19:14, Florian Fainelli wrote: > > Hello, > > Le 10 août 2014 09:44, "Etienne Champetier" > mailto:champetier.etie...@gmail.com>> a > écrit : > > Le 10 août 2014 18:18, "Stefan Monnier" > a écrit : > > > > > > > It would be great to have all feed

Re: [OpenWrt-Devel] concept of package/compile output

Hello Thomas, On 06.08.2014 13:44, thomas.lan...@lantiq.com wrote: > Hello Claudio, > > Claudio Thomas wrote on 2014-08-06: >> Hi, >> is there a special concept what the package/compile output (without V=s) >> shows? > These are the real targets the build system is

[OpenWrt-Devel] concept of package/compile output

Hi, is there a special concept what the package/compile output (without V=s) shows? Sometime you see something like.. make[3] -C package/libs/librpc compile make[3] -C package/network/utils/iwinfo compile make[3] -C package/system/uci compile what corresponds to the make-rules make

[OpenWrt-Devel] Makefile CFLAGS & CPU_TYPE

rgets. -- Mit freundlichen Grüßen / Best regards Claudio Thomas Dipl.-Ing. der technischen Informatik (M.Sc.) Leitung IT / Head of IT Tel: +49 (0)2773 7444-137 Fax: +49 (0)2773 7444-3137 Homepage: http://www.xmodus-systems.de E-Mail: c...@xmodus-systems.de GPG: http://xmodus-systems.de/gpg/ct

Re: [OpenWrt-Devel] [PATCH] [mpc83xx] add menuconfig-option for rb333 and rb600

On 25.07.2014 12:25, Imre Kaloz wrote: > Hi, > > On Fri, 25 Jul 2014 11:34:49 +0200, Claudio Thomas > wrote: > >> Hi, as reaction of the following email: >> On 15.07.2014 15:05, Claudio Thomas wrote: >>> Subject: [OpenWrt-Devel] When to use Target Profile or Su

Re: [OpenWrt-Devel] [PATCH] [mpc83xx] add menuconfig-option for rb333 and rb600

Hi, as reaction of the following email: On 15.07.2014 15:05, Claudio Thomas wrote: > Subject: [OpenWrt-Devel] When to use Target Profile or Subtarget > > Hi, > I'm adapting the "Freescale MPC83xx" platform, so that multiple devices > can be selected. > Actuall

[OpenWrt-Devel] [PATCH] [mpc83xx] add menuconfig-option for rb333 and rb600

Add new target-profile for both boards in menuconfig. Replaced unconditional Makefile directives with such that depends on menuconfig settings. The default behaviour remains to be as it was: to compile for both. Signed-off-by: Claudio Thomas --- target/linux/mpc83xx/Makefile | 12

[OpenWrt-Devel] [PATCH] [mpc83xx] add menuconfig-option for rb333 and rb600

Add new target-profile for both boards in menuconfig. Replaced unconditional Makefile directives with such that depends on menuconfig settings. The default behaviour remains to be as it was: to compile for both. Signed-off-by: Claudio Thomas --- target/linux/mpc83xx/Makefile | 12

Re: [OpenWrt-Devel] When to use Target Profile or Subtarget

Hallo Jow, thank you for your fast reply. So far I see there are subtargets needed because each board has another kernel image (name?). KERNELNAME:="uImage dtbImage.rb600 dtbImage.rb333" Claudio On 15.07.2014 15:23, Jo-Philipp Wich wrote: > Hi. > > Profiles influence image generation and packag

[OpenWrt-Devel] When to use Target Profile or Subtarget

o select the Board implementation (like "A1x/XBurst/AU1x00/RT288x"), or a mix of both. Is there a "official definition" when to use what? The difference is not obvious to me. -- Mit freundlichen Grüßen / Best regards Claudio Thomas Dipl.-Ing. der technischen Informatik (

Re: [OpenWrt-Devel] Few question about compiling your own firmware images

Hi John, I've never done it, but you should change it easy in the menu config: # make menuconfig [*] Image configuration -> [*] Preinit configuration options ---> (10.0.0.1) IP Address for preinit network messages ---> (10.0.0.255) Broadcast address for preinit network messages An alternative way

[OpenWrt-Devel] [PATCH] [mpc83xx] add missing kernelnames into Makefile

add missing kernelnames to Makefile because those files are needed in 'target/linux/mpc83xx/image/Makefile'. Without them a compilation for mpc83xx is not possible - the buildbot stops with the error "No such file or directory" Signed-off-by: Claudio Thomas --- target/li