[LEDE-DEV] Out of tree builds

[David Woodhouse]

Is there a simple trick I'm missing, to build for multiple targets from
the same build tree? 

I'm mostly just manually copying my .config file out of the way and
swapping it for a different one each time — but there's got to be a
better way, surely?

mv .config .config.wndr3800
mv .config.tdw8970 .config
make -j32 oldconfig world

-- 
dwmw2




smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Added wiki links to the LEDE site, can someone merge the PR?

[Alberto Bursi]

https://github.com/lede-project/web/pull/42

It's about adding wiki links on the main site, to let people know that 
there is also a wiki.

I'm sending a mail here because my last commit to the site was merged 
like a few month later, I'd rather get this PR merged sooner than that.

-Alberto
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC 0/1] x86: Add support for the PC Engines APU2 Board

[Ben Greear]

On 10/14/2016 10:19 AM, Chris Blake wrote:

This is an RFC to port the PC Engines APU2 board to LEDE. Currently this is 
based on my unofficial repo at https://github.com/riptidewave93/LEDE-APU2 and 
after a discussion on the lede-dev IRC on the best plan of action, which was to 
move this device to a profile under x86_64.

Things Working:
 - board detection
 - USB ports
 - LED/Button support
 - ath9k and ath10k - to support both wireless cards sold via PC Engines
 - SP5100 Watchdog
 - NCT5104D GPIO Driver

Not Working:
 - AES-NI CPU Acceleration


I have a patch that enables AES-NI for appropriate x86-64 CPUs.  You are welcome
to try getting it upstream and/or into LEDE:

http://dmz2.candelatech.com/?p=linux-4.7.dev.y/.git;a=commit;h=abd4e4982a674ab469916f0a50e01e69b739ce71

Thanks,
Ben

--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC 0/1] x86: Add support for the PC Engines APU2 Board

[Luiz Angelo Daros de Luca]

Chris,

You might be interested in
https://lists.openwrt.org/pipermail/openwrt-devel/2015-February/031200.html,
which was never commited.

Regards,

---
 Luiz Angelo Daros de Luca, Me.
luizl...@gmail.com

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] busybox: prevent globbing, word splitting

[Jan-Tarek Butt]

Double quote to prevent globbing and word splitting.

Signed-off-by: Jan-Tarek Butt 
---
 package/utils/busybox/files/cron | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/utils/busybox/files/cron b/package/utils/busybox/files/cron
index 19ecc43..a201374 100755
--- a/package/utils/busybox/files/cron
+++ b/package/utils/busybox/files/cron
@@ -14,7 +14,7 @@ validate_cron_section() {
 start_service () {
[ -z "$(ls /etc/crontabs/)" ] && return 1
 
-   loglevel=$(uci_get "system.@system[0].cronloglevel")
+   loglevel="$(uci_get "system.@system[0].cronloglevel")"
 
[ -z "${loglevel}" ] || {
/sbin/validate_data uinteger "${loglevel}" 2>/dev/null
@@ -28,7 +28,7 @@ start_service () {
ln -s /etc/crontabs /var/spool/cron/ 2>/dev/null
 
procd_open_instance
-   procd_set_param command "$PROG" -f -c /etc/crontabs -l ${loglevel:-5}
+   procd_set_param command "$PROG" -f -c /etc/crontabs -l "${loglevel:-5}"
procd_close_instance
 }
 
-- 
2.10.0


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Vagrant file for Lede development

[Alberto Bursi]

On 10/09/2016 07:05 PM, Simon H wrote:
> I'm looking to contribute in some small way once again.
> Not being a regular linux user, creating a build environment for
> Lede/OpenWRT has always been a time-consuming process for me.
>
> However, on other projects, I've begun to use Vagrant (specifically
> VVV for web development).
>
> Although completely new to vagrant, it's working well for me, and so i
> thought i'd give it a try for Lede.
>
> The result is on github:
>
> https://github.com/btsimonh/lede-vagrant
>
> If people think this is a good way to encourage developers to 'join
> the cause', then maybe we could host something similar in the Lede
> github, and add a 'start developing with Lede' page referencing it?
>
> looking forward to hearing comments/suggestions...
>
> best regards,
>
> Simon
>

Hm, another thing that might be useful to package with vagrant is the 
Image Builder. https://wiki.openwrt.org/doc/howto/obtain.firmware.generate

It's a thing that generates firmware images with a custom set of 
packages without recompiling from source (downloads packages from repos 
and creates the image).

This tool is useful for those that want to make a custom firmware image 
but have no need to recompile everything from source. (= it is a tool 
for end users, not developers)

The tool works only in linux 64bit, so again people without a linux 
system can't use it without setting up various things themselves.

I think you can reuse 99% of the current setup you use for the "lede 
development environment deployment", so it should be quick.

One usecase is making extroot-ready firmware images for devices with 4 
MiB of storage and USB/Sata/sdcard ports, so that they can use the 
external mass storage device to install packages.

Or also firmware images wil luci (web-interface) and 
announce/avahi/zeroconf already embedded, as currently none has yet 
changed anything about the buildbots and they still make barebones 
ssh-only images.

Or to fit the most packages possible in the embedded flash, as the 
imagebuilder dumps all packages in the root squashfs highly compressed 
read-only filesystem, while installing packages in the router goes in 
the overlay jffs2 partition which is much less compressed, but read-write.

-Alberto

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [RFC 0/1] x86: Add support for the PC Engines APU2 Board

[Chris Blake]

This is an RFC to port the PC Engines APU2 board to LEDE. Currently this is 
based on my unofficial repo at https://github.com/riptidewave93/LEDE-APU2 and 
after a discussion on the lede-dev IRC on the best plan of action, which was to 
move this device to a profile under x86_64.

Things Working:
 - board detection
 - USB ports
 - LED/Button support
 - ath9k and ath10k - to support both wireless cards sold via PC Engines
 - SP5100 Watchdog
 - NCT5104D GPIO Driver

Not Working:
 - AES-NI CPU Acceleration
 - PC Buzzer

Default Packages:
 - flashrom - BIOS Upgrades
 - lm-sensors - Temp Monitoring
 - wpad-mini - Wireless AP support
 - hwclock - RTC support

Things that still need working out:
 - AES-NI Kernel Support
 - Profile Specific Images - So far the ./image/Makefile does not seem to 
support 'profiles'. This will need to be fixed, so APU2 & Generic images can 
build without merging.
 - HWMon & ath10k - ath10k requires hwmon, but the module fails to build if 
hwmon was built as a module. Because if this, it's added to the kernel config. 
Is there a better way to do this, or a way around this problem?
 - pc buzzer/beep - Busybox has beep support, but I didn't find a way to build 
it without changing the default BusyBox config for all targets. Maybe "beep" 
should also be added as a standalone package? 
https://lists.openwrt.org/pipermail/openwrt-devel/2009-November/005227.html
 - x86_64 kernel config - Besudes hwmon, GPIO support had to be added. Should 
this be done here, or in the root target kernel config like other targets? 
Also, DEVMEM was added for flashrom. Is this an issue, or would it be OK to 
keep this in?
 - Default Packages - Currently the "goal" of my unofficial port was to make 
sure all features of the device were supported via my image. Is this the path 
LEDE wants to take, or should it be more of a "minimal" approach? AKA, no 
packages/ath*k

If there are any comments, suggestions, or visible improvements please let me 
know/reply with some patches.

Cc: Jo-Philipp Wich 

Signed-off-by: Chris Blake 

Chris Blake (1):
  x86: Add support for the PC Engines APU2 Board

 target/linux/x86/64/config-default |  12 +
 target/linux/x86/64/profiles/001-PCEngines.mk  |  20 +
 target/linux/x86/base-files/etc/board.d/01_leds|  22 ++
 target/linux/x86/base-files/etc/board.d/02_network |  26 ++
 target/linux/x86/base-files/etc/diag.sh|  37 ++
 target/linux/x86/base-files/lib/x86.sh |  13 +
 target/linux/x86/config-4.4|   1 +
 .../linux/x86/files/drivers/gpio/gpio-nct5104d.c   | 432 +
 target/linux/x86/files/drivers/leds/leds-apu2.c| 371 ++
 target/linux/x86/modules.mk|  36 ++
 .../x86/patches-4.4/800-add-apu2-led-driver.patch  |  29 ++
 .../801-sp5100_tco-add-apu2-support.patch  |  91 +
 .../patches-4.4/802-add-nct5104d-gpio-driver.patch |  27 ++
 13 files changed, 1117 insertions(+)
 create mode 100644 target/linux/x86/64/profiles/001-PCEngines.mk
 create mode 100755 target/linux/x86/base-files/etc/board.d/01_leds
 create mode 100755 target/linux/x86/base-files/etc/board.d/02_network
 create mode 100755 target/linux/x86/base-files/etc/diag.sh
 create mode 100755 target/linux/x86/base-files/lib/x86.sh
 create mode 100644 target/linux/x86/files/drivers/gpio/gpio-nct5104d.c
 create mode 100644 target/linux/x86/files/drivers/leds/leds-apu2.c
 create mode 100644 target/linux/x86/modules.mk
 create mode 100644 target/linux/x86/patches-4.4/800-add-apu2-led-driver.patch
 create mode 100644 
target/linux/x86/patches-4.4/801-sp5100_tco-add-apu2-support.patch
 create mode 100644 
target/linux/x86/patches-4.4/802-add-nct5104d-gpio-driver.patch

--
2.7.4

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] ct-bugcheck: fix globbing, word splitting and change formatting

[Ben Greear]

On 10/14/2016 08:58 AM, Jan-Tarek Butt wrote:

Double quote to prevent globbing and word splitting.
Use short syntax to enhance reading quallity.


I disagree that the short syntax helps reading quality,
but if others like it then I guess that change is fine with me.

Thanks,
Ben



Signed-off-by: Jan-Tarek Butt 
---
 package/utils/ct-bugcheck/src/bugchecker.sh | 14 +++---
 1 file changed, 3 insertions(+), 11 deletions(-)

diff --git a/package/utils/ct-bugcheck/src/bugchecker.sh 
b/package/utils/ct-bugcheck/src/bugchecker.sh
index be305af..eb221db 100755
--- a/package/utils/ct-bugcheck/src/bugchecker.sh
+++ b/package/utils/ct-bugcheck/src/bugchecker.sh
@@ -12,18 +12,10 @@ DO_BUGCHECK=0
 #  DO_BUGCHECK=1
 #  export DO_BUGCHECK

-if [ -f /etc/config/bugcheck ]
-then
-. /etc/config/bugcheck
-fi
+[ -f /etc/config/bugcheck ] && . /etc/config/bugcheck
+[ "$DO_BUGCHECK" -eq "0" ] && exit 0

-if [ $DO_BUGCHECK == 0 ]
-then
-exit 0
-fi
-
-while true
-  do
+while true; do
   $CHECKER
   sleep $SLEEPFOR
 done




--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] imx6: inittab: Use login.sh wrapper so we can configure console password

[Petr Štetiar]

In dc92917 there was introduced login.sh wrapper which allows
configuration of console passwords via UCI system ttylogin config
option.

Signed-off-by: Petr Štetiar 
---
 target/linux/imx6/base-files/etc/inittab | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/target/linux/imx6/base-files/etc/inittab 
b/target/linux/imx6/base-files/etc/inittab
index a6c0bc8..b944a93 100644
--- a/target/linux/imx6/base-files/etc/inittab
+++ b/target/linux/imx6/base-files/etc/inittab
@@ -1,4 +1,4 @@
 ::sysinit:/etc/init.d/rcS S boot
 ::shutdown:/etc/init.d/rcS K shutdown
-::askconsole:/bin/ash --login
-tty1::askfirst:/bin/ash --login
+::askconsole:/usr/libexec/login.sh
+tty1::askfirst:/usr/libexec/login.sh
-- 
1.9.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev