05.10.2017 01:20, Sergey Ryazanov:
On Mon, Oct 2, 2017 at 2:33 AM, Sergey Ryazanov wrote:
Some boards have identical hardware id and differ only in hardware
revision (e.g. Acher C20 and Archer C20i). Such case confuse image
inspection code and it selects wrong board info structure.
Rework the
On Mon, Oct 2, 2017 at 2:33 AM, Sergey Ryazanov wrote:
> Some boards have identical hardware id and differ only in hardware
> revision (e.g. Acher C20 and Archer C20i). Such case confuse image
> inspection code and it selects wrong board info structure.
>
> Rework the board detection code to make
creating sdcard image using gen_at91_sdcard_img.sh for sama5 platform
and sdcard image partition layout is:
P0: Boot (fat32) - Contains(at91bootstrap,u-boot,zImage & dtb)
p1: Rootfs (ext4)
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/image/Makefile
This patch seriese is about generating sdcard images for sama5 socs
and enabled necessary kernel and filesystem changes to generate sdimage.
Sandeep Sheriker Mallikarjun (3):
at91: Enable SDHCI for sama5 in default config
at91: Add ext4 filesystem
at91: creating sdcard image for sama5
targ
Enabled SDHCI for sama5 in kernel default config and this is needed
to mount sdcard rootfs partition during boot.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/sama5/config-default | 5 +
1 file changed, 5 insertions(+)
diff --git a/target/linux/at91/sama5/config-defaul
Add ext4 filesystem for creating sdcard image with ext4 rootfs and
removing ext2 as it superset of ext4.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/at91/Makefile b/target/linux/at91/
This patch serires is to fix:
1. Show up in menuconfig, only when sama5 is selected as target device.
2. Fixed install command insead of manually copying to bin folder.
Sandeep Sheriker Mallikarjun (2):
at91bootstrap: Add BUILD_SUBTARGET variable
at91bootstrap: remove manual copy of binari
configuring a legacy(i.e sam9x soc) device as a subtarget in menuconfig.
The bootloader menu shows both legacy and sama5 u-boot targets and if
user selects sama5 as uboot target for legacy devices. The build fails
due to incorrect cpu flags. To avoid these build error removing sama5
platform from u
Added sama5 to BUILD_SUBTARGET variable.This will populate at91bootstrap
menu options in bootloader menu only when SAMA5 devices are selected as
SUBTARGET and to avoid showing up this menu when legacy device is
selected as SUBTARGET and fixed typo mistake: sama5d3 -> sama5d2.
Signed-off-by: Sandee
removed copying of binaries to BIN_DIR during install and using
default/install to install binaries to BIN_DIR folder.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
package/boot/at91bootstrap/at91bootstrap.mk | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/pa
Added new package uboot-at91_sama5 to build uboot binaries for
Microchip(Atmel AT91) sama5 socs.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
package/boot/uboot-at91_sama5/Makefile | 82 ++
1 file changed, 82 insertions(+)
create mode 100644 package/boot/uboo
This patch series fixes the uboot-at91 build error's. In case when a
uboot package is selected of a different subtarget device, the build
will fail due to wrong cpu type.
Sandeep Sheriker Mallikarjun (2):
uboot-at91: remove sama5 platform
uboot-at91_sama5: Add New package uboot-at91_sama5
Hi Antonio,
please always include the LEDE dev mailing list!
Please have a look at:
https://github.com/lede-project/source/blame/master/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj344.c
https://github.com/lede-project/source/blame/master/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj5
Add sysfs 'mode' attribute to swconfig controlled LEDs.
swconfig 'link state' LEDs blink in the presence of port traffic. This
behaviour becomes more obvious as switches start to support
get_port_stats() e.g. commits 0369e358916ef092a1644334f5dd1412051b68a4,
3056d09b4046e0eb0f6de0f3f5432cd9fa86fc
The SERVICE_SET_NAME belongs to enum SERVICE_SET_, not SERVICE_ATTR_NAME.
Signed-off-by: Pierre Lebleu
---
service/service.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/service/service.c b/service/service.c
index 02a29fa..9c798aa 100644
--- a/service/service.c
+++ b/s
2017-10-04 12:54 GMT+02:00 Mathias Kresin :
> 2017-10-04 12:49 GMT+02:00 :
>> From: Pierre Lebleu
>>
>
> ^^^ and here should be an explanation why SERVICE_SET_NAME should be
> used in favour of SERVICE_ATTR_NAME.
The SERVICE_SET_NAME belongs to enum SERVICE_SET_, not SERVICE_ATTR_NAME.
>
>>
The idea behind this patch is to allow you to create some firewall
rules within the service itself rather than an instance.
Indeed, I have a wrapper script which launches several different
services but no daemon by itself, so I can not create an instance for
it.
Or, if I create an instance without
From: Pierre Lebleu
It gives the ability to create firewall data within the
service itself rather than within an instance.
Signed-off-by: Pierre Lebleu
---
service/service.c | 45 +++--
service/service.h | 2 ++
2 files changed, 45 insertions(+), 2 dele
2017-10-04 12:49 GMT+02:00 :
> From: Pierre Lebleu
>
^^^ and here should be an explanation why SERVICE_SET_NAME should be
used in favour of SERVICE_ATTR_NAME.
> Signed-off-by: Pierre Lebleu
> ---
> service/service.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/serv
From: Pierre Lebleu
Signed-off-by: Pierre Lebleu
---
service/service.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/service/service.c b/service/service.c
index 02a29fa..9c798aa 100644
--- a/service/service.c
+++ b/service/service.c
@@ -267,7 +267,7 @@ service_handle_set(s
The LEDE Community is proud to announce the third service release of
stable LEDE 17.01 series.
LEDE 17.01.3 “Reboot” incorporates a fair number of fixes back ported
from the development branch during the last sixteen weeks.
---
Some selected highlights of the service release are:
* Linux kernel
21 matches
Mail list logo
