Re: [OpenWrt-Devel] upstream opkg
Hi, Yocto made opkg unusable for us. Current upstream is *far* too big for use in OpenWrt. The now required libarchive alone is larger than our current opkg version. I took a look at packaging current opkg a while back and got stuck at bringing libarchive down to a sane size, therfor I gave up on it. ~ Jo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/4] tools: firmware-utils: add region code support to mktplinkfw
On 21 April 2016 at 08:33, Matthias Schiffer
wrote:
> @@ -324,6 +351,17 @@ static int check_options(void)
> else
> hw_rev = 1;
>
> + if (country) {
> + region = find_region(country);
> + if (region == (uint32_t)-1) {
> + char *end;
> + region = strtoul(country, &end, 0);
> + if (*end) {
> + ERR("unknown region code \"%s\"", country);
> + }
> + }
> + }
I'm wondering if this wouldn't be better to just make find_region
return signed int.
What about failing to build firmware if a provided country can't be
converted into an unsigned int? Right now you set "region" field in
the header to ULONG_MAX if country is invalid. This tool usually
refuses to build firmware if something goes wrong, e.g.:
ERR("either board or hardware id must be specified");
return -1;
ERR("unknown/unsupported board id \"%s\"", board_id);
return -1;
ERR("flash layout is not specified");
return -1;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/4] ar71xx: fix giving extra arguments to Build/mktplinkfw
On 21 April 2016 at 08:33, Matthias Schiffer wrote: > @@ -967,8 +968,8 @@ define Device/tl-wr2543-v1 > BOARDNAME := TL-WR2543N > DEVICE_PROFILE := TLWR2543 > TPLINK_HWID := 0x25430001 > -IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade "-v > 3.13.99" > -IMAGE/factory.bin := append-rootfs | mktplinkfw factory "-v 3.13.99" > +IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade -v 3.13.99 > +IMAGE/factory.bin := append-rootfs | mktplinkfw factory -v 3.13.99 > endef > TARGET_DEVICES += tl-wr2543-v1 Any idea why we don't use variables in the first place? E.g. VERSION := 3.13.99 -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/4] tools: firmware-utils: add region code support to mktplinkfw
On 04/21/2016 11:28 AM, Rafał Miłecki wrote:
> On 21 April 2016 at 08:33, Matthias Schiffer
> wrote:
>> @@ -324,6 +351,17 @@ static int check_options(void)
>> else
>> hw_rev = 1;
>>
>> + if (country) {
>> + region = find_region(country);
>> + if (region == (uint32_t)-1) {
>> + char *end;
>> + region = strtoul(country, &end, 0);
>> + if (*end) {
>> + ERR("unknown region code \"%s\"", country);
>> + }
>> + }
>> + }
>
> I'm wondering if this wouldn't be better to just make find_region
> return signed int.
>
> What about failing to build firmware if a provided country can't be
> converted into an unsigned int? Right now you set "region" field in
> the header to ULONG_MAX if country is invalid. This tool usually
> refuses to build firmware if something goes wrong, e.g.:
>
> ERR("either board or hardware id must be specified");
> return -1;
>
> ERR("unknown/unsupported board id \"%s\"", board_id);
> return -1;
>
> ERR("flash layout is not specified");
> return -1;
>
I don't think returning signed makes sense, uint32_t is also used in the
struct (and everywhere else).
Regarding the error case: Yes, I forgot the 'return -1' there, I'll send a v2.
Matthias
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/4] ar71xx: fix giving extra arguments to Build/mktplinkfw
On 04/21/2016 11:30 AM, Rafał Miłecki wrote: > On 21 April 2016 at 08:33, Matthias Schiffer > wrote: >> @@ -967,8 +968,8 @@ define Device/tl-wr2543-v1 >> BOARDNAME := TL-WR2543N >> DEVICE_PROFILE := TLWR2543 >> TPLINK_HWID := 0x25430001 >> -IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade "-v >> 3.13.99" >> -IMAGE/factory.bin := append-rootfs | mktplinkfw factory "-v 3.13.99" >> +IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade -v 3.13.99 >> +IMAGE/factory.bin := append-rootfs | mktplinkfw factory -v 3.13.99 >> endef >> TARGET_DEVICES += tl-wr2543-v1 > > Any idea why we don't use variables in the first place? E.g. > VERSION := 3.13.99 > For the version, this would make sense, but can be done in a separate patch. For the region code, we will eventually need to build multiple factory images with different arguments, so in that case, using additional arguments for the mktplinkfw build step makes sense. Matthias signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Will finish to try next week
Le 14 avr. 2016 20:20, "Baptiste Clenet" a écrit :
> 2016-04-14 16:58 GMT+02:00 John Crispin :
> >
> >
> > On 14/04/2016 16:38, Baptiste Clenet wrote:
> >> Marc, yes it has been added by John Crispins.
> >>
> >> I had nothing in etc/config/wireless, which is the right definition
> >> for this driver? (I don't find any documentation). Tom, Adam, yes it
> >> is defined.
> >>
> >> 2016-04-12 13:30 GMT+02:00 Adam Kent :
> >>> Hi Baptiste
> >>>
> >>> Which board exactly? You may need to add the "wmac" definition to the
> >>> relevant dts file. Have a look in
> >>> target/linux/ramips/dts/.dts and make sure there's
> >>> this:
> >>>
> >>> wmac@1030 {
> >>> status = "okay";
> >>> };
> >>>
> >>> - Adam
> >>>
> >>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
> wrote:
> Hi,
>
> I flashed the current tree on mt7688 board and no interface showed up
> for wifi. Should I do something? I would like to try the mt76 wifi
> driver on this board. (I added it with in menuconfig)
>
> Cheers,
>
> --
> Baptiste
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >>
> >>
> >>
> >
> >
> > are you loading the mt76 driver ?
> modprobe mt76?
> It is already loaded:
> cfg80211 215619 3 mt7603e
> mac80211 389306 3 mt7603e
> mt76 15734 2 mt7603e
> mt7603e27964 0
> mt76x2e34300 0
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> --
> Baptiste
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 4/4] ar71xx: build TP-LINK Archer C7 images with US region code
Since December 2015, the Archer C7 comes with an US-specific firmware. This firmware will only allow upgrades with images that contain the US region code in the firmware header. The "universal" firmware distributed in the rest of the world doesn't care about the region code, so we can just unconditionally set the region to US for now. When other region-specific firmwares appear, we'll need to create a factory image for each of them. Signed-off-by: Matthias Schiffer --- target/linux/ar71xx/image/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ar71xx/image/Makefile b/target/linux/ar71xx/image/Makefile index 2699b64..2b2e868 100644 --- a/target/linux/ar71xx/image/Makefile +++ b/target/linux/ar71xx/image/Makefile @@ -414,6 +414,7 @@ define Device/archer-c7-v2 BOARDNAME := ARCHER-C7 DEVICE_PROFILE := ARCHERC7 TPLINK_HWID := 0xc702 +IMAGE/factory.bin := append-rootfs | mktplinkfw factory -C US endef define Device/tl-wdr7500-v3 -- 2.8.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 3/4] ar71xx: fix giving extra arguments to Build/mktplinkfw
The build command will always get the whole argument string in $(1),
regardless of whitespace. We need to use word/wordlist to split the string
after the first word.
Whitespace and quotation will be given to the command verbatim (make will
ignore it), so to give multiple arguments, no quotation marks may be used.
Fixes: r47174 ("ar71xx/image: add options argument to mktplinkfw step")
Signed-off-by: Matthias Schiffer
---
target/linux/ar71xx/image/Makefile | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index e4e2fcf..2699b64 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Makefile
@@ -49,14 +49,15 @@ endef
# -X reserve bytes in the firmware image (hexval prefixed with 0x)
define Build/mktplinkfw
-$(STAGING_DIR_HOST)/bin/mktplinkfw \
- -H $(TPLINK_HWID) -W $(TPLINK_HWREV) -F $(TPLINK_FLASHLAYOUT)
-N OpenWrt -V $(REVISION) $2 \
+ -H $(TPLINK_HWID) -W $(TPLINK_HWREV) -F $(TPLINK_FLASHLAYOUT)
-N OpenWrt -V $(REVISION) \
-m $(TPLINK_HEADER_VERSION) \
-k $(word 1,$^) \
-r $@ \
-o $@.new \
-j -X 0x4 \
-a $(call rootfs_align,$(FILESYSTEM)) \
- $(if $(findstring sysupgrade,$1),-s) && mv $@.new $@ || rm -f $@
+ $(wordlist 2,$(words $(1)),$(1)) \
+ $(if $(findstring sysupgrade,$(word 1,$(1))),-s) && mv $@.new
$@ || rm -f $@
endef
# mktplinkfw-initramfs
@@ -64,7 +65,7 @@ endef
# -c combined image
define Build/mktplinkfw-initramfs
$(STAGING_DIR_HOST)/bin/mktplinkfw \
- -H $(TPLINK_HWID) -W $(TPLINK_HWREV) -F $(TPLINK_FLASHLAYOUT)
-N OpenWrt -V $(REVISION) $2 \
+ -H $(TPLINK_HWID) -W $(TPLINK_HWREV) -F $(TPLINK_FLASHLAYOUT)
-N OpenWrt -V $(REVISION) $(1) \
-m $(TPLINK_HEADER_VERSION) \
-k $@ \
-o $@.new \
@@ -75,14 +76,14 @@ endef
define Build/tplink-safeloader
-$(STAGING_DIR_HOST)/bin/tplink-safeloader \
- -B $(TPLINK_BOARD_NAME) \
- -V $(REVISION) \
- -k $(word 1,$^) \
- -r $@ \
- -o $@.new \
- $2 \
- -j \
- $(if $(findstring sysupgrade,$1),-S) && mv $@.new $@ || rm -f $@
+ -B $(TPLINK_BOARD_NAME) \
+ -V $(REVISION) \
+ -k $(word 1,$^) \
+ -r $@ \
+ -o $@.new \
+ -j \
+ $(wordlist 2,$(words $(1)),$(1)) \
+ $(if $(findstring sysupgrade,$(word 1,$(1))),-S) && mv $@.new
$@ || rm -f $@
endef
define Build/loader-common
@@ -967,8 +968,8 @@ define Device/tl-wr2543-v1
BOARDNAME := TL-WR2543N
DEVICE_PROFILE := TLWR2543
TPLINK_HWID := 0x25430001
-IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade "-v 3.13.99"
-IMAGE/factory.bin := append-rootfs | mktplinkfw factory "-v 3.13.99"
+IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade -v 3.13.99
+IMAGE/factory.bin := append-rootfs | mktplinkfw factory -v 3.13.99
endef
TARGET_DEVICES += tl-wr2543-v1
--
2.8.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 2/4] tools: firmware-utils: add region code support to mktplinkfw
Signed-off-by: Matthias Schiffer
---
tools/firmware-utils/src/mktplinkfw.c | 51 +++
1 file changed, 46 insertions(+), 5 deletions(-)
diff --git a/tools/firmware-utils/src/mktplinkfw.c
b/tools/firmware-utils/src/mktplinkfw.c
index 695d4f5..7127932 100644
--- a/tools/firmware-utils/src/mktplinkfw.c
+++ b/tools/firmware-utils/src/mktplinkfw.c
@@ -28,6 +28,7 @@
#include "md5.h"
#define ALIGN(x,a) ({ typeof(a) __a = (a); (((x) + __a - 1) & ~(__a - 1)); })
+#define ARRAY_SIZE(a) (sizeof((a)) / sizeof((a)[0]))
#define HEADER_VERSION_V1 0x0100
#define HEADER_VERSION_V2 0x0200
@@ -45,7 +46,7 @@ struct fw_header {
charfw_version[36];
uint32_thw_id; /* hardware id */
uint32_thw_rev; /* hardware revision */
- uint32_tunk1;
+ uint32_tregion; /* region code */
uint8_t md5sum1[MD5SUM_LEN];
uint32_tunk2;
uint8_t md5sum2[MD5SUM_LEN];
@@ -90,6 +91,8 @@ static uint32_t hw_id;
static char *opt_hw_rev;
static uint32_t hw_rev;
static uint32_t opt_hdr_ver = 1;
+static char *country;
+static uint32_t region;
static int fw_ver_lo;
static int fw_ver_mid;
static int fw_ver_hi;
@@ -170,6 +173,11 @@ static struct flash_layout layouts[] = {
}
};
+static const char *const regions[] = {
+ "UN", /* universal */
+ "US",
+};
+
/*
* Message macros
*/
@@ -206,6 +214,24 @@ static struct flash_layout *find_layout(const char *id)
return ret;
}
+static uint32_t find_region(const char *country) {
+ uint32_t i;
+
+ for (i = 0; i < ARRAY_SIZE(regions); i++) {
+ if (strcasecmp(regions[i], country) == 0)
+ return i;
+ }
+
+ return -1;
+}
+
+static const char * get_region_country(uint32_t region) {
+ if (region < ARRAY_SIZE(regions))
+ return regions[region];
+ else
+ return "unknown";
+}
+
static void usage(int status)
{
fprintf(stderr, "Usage: %s [OPTIONS...]\n", progname);
@@ -217,6 +243,7 @@ static void usage(int status)
" -L overwrite kernel load address with (hexval prefixed
with 0x)\n"
" -Huse hardware id specified with \n"
" -W use hardware revision specified with \n"
+" -C set region code to \n"
" -F use flash layout specified with \n"
" -kread kernel image from the file \n"
" -rread rootfs image from the file \n"
@@ -324,6 +351,18 @@ static int check_options(void)
else
hw_rev = 1;
+ if (country) {
+ region = find_region(country);
+ if (region == (uint32_t)-1) {
+ char *end;
+ region = strtoul(country, &end, 0);
+ if (*end) {
+ ERR("unknown region code \"%s\"", country);
+ return -1;
+ }
+ }
+ }
+
layout = find_layout(layout_id);
if (layout == NULL) {
ERR("unknown flash layout \"%s\"", layout_id);
@@ -437,6 +476,7 @@ static void fill_header(char *buf, int len)
strncpy(hdr->fw_version, version, sizeof(hdr->fw_version));
hdr->hw_id = htonl(hw_id);
hdr->hw_rev = htonl(hw_rev);
+ hdr->region = htonl(region);
if (boot_info.file_size == 0)
memcpy(hdr->md5sum1, md5salt_normal, sizeof(hdr->md5sum1));
@@ -645,9 +685,6 @@ static int inspect_fw(void)
inspect_fw_phexdec("Version 1 Header size", sizeof(struct fw_header));
- if (ntohl(hdr->unk1) != 0)
- inspect_fw_phexdec("Unknown value 1", hdr->unk1);
-
memcpy(md5sum, hdr->md5sum1, sizeof(md5sum));
if (ntohl(hdr->boot_len) == 0)
memcpy(hdr->md5sum1, md5salt_normal, sizeof(md5sum));
@@ -674,6 +711,7 @@ static int inspect_fw(void)
inspect_fw_pstr("Firmware version", hdr->fw_version);
inspect_fw_phex("Hardware ID", ntohl(hdr->hw_id));
inspect_fw_phex("Hardware Revision", ntohl(hdr->hw_rev));
+ inspect_fw_phexpost("Region code", ntohl(hdr->region),
get_region_country(ntohl(hdr->region)));
printf("\n");
@@ -748,7 +786,7 @@ int main(int argc, char *argv[])
while ( 1 ) {
int c;
- c = getopt(argc, argv,
"a:H:E:F:L:m:V:N:W:ci:k:r:R:o:xX:hsSjv:");
+ c = getopt(argc, argv,
"a:H:E:F:L:m:V:N:W:C:ci:k:r:R:o:xX:hsSjv:");
if (c == -1)
break;
@@ -768,6 +806,9 @@ int main(int argc, char *argv[])
case 'W':
opt_hw_rev = optarg;
break;
+ case 'C':
+ country = optarg;
+ break;
case 'L':
sscanf(optarg, "0x%x", &kernel_la);
[OpenWrt-Devel] [PATCH v2 1/4] tools: firmware-utils: clean up mktplinkfw
Remove the whole board list from mktplinkfw, as OpenWrt doesn't use it and
it was severely out of sync with the list of built images for ar71xx.
Also:
* fix -Wall warnings
* add const where appropriate
Signed-off-by: Matthias Schiffer
---
tools/firmware-utils/Makefile | 2 +-
tools/firmware-utils/src/mktplinkfw.c | 468 +++---
2 files changed, 35 insertions(+), 435 deletions(-)
diff --git a/tools/firmware-utils/Makefile b/tools/firmware-utils/Makefile
index ec814b0..20f26e2 100644
--- a/tools/firmware-utils/Makefile
+++ b/tools/firmware-utils/Makefile
@@ -40,7 +40,7 @@ define Host/Compile
$(call cc,encode_crc)
$(call cc,nand_ecc)
$(call cc,mkplanexfw sha1)
- $(call cc,mktplinkfw md5)
+ $(call cc,mktplinkfw md5, -Wall)
$(call cc,mktplinkfw2 md5)
$(call cc,tplink-safeloader md5, -Wall)
$(call cc,pc1crypt)
diff --git a/tools/firmware-utils/src/mktplinkfw.c
b/tools/firmware-utils/src/mktplinkfw.c
index bf7c619..695d4f5 100644
--- a/tools/firmware-utils/src/mktplinkfw.c
+++ b/tools/firmware-utils/src/mktplinkfw.c
@@ -31,52 +31,6 @@
#define HEADER_VERSION_V1 0x0100
#define HEADER_VERSION_V2 0x0200
-#define HWID_ANTMINER_S1 0x04440101
-#define HWID_ANTMINER_S3 0x04440301
-#define HWID_GL_INET_V10x0801
-#define HWID_GS_OOLITE_V1 0x3C000101
-#define HWID_OMY_X10x06660201
-#define HWID_ONION_OMEGA 0x0471
-#define HWID_TL_MR10U_V1 0x00100101
-#define HWID_TL_MR13U_V1 0x00130101
-#define HWID_TL_MR3020_V1 0x3021
-#define HWID_TL_MR3220_V1 0x3221
-#define HWID_TL_MR3220_V2 0x3222
-#define HWID_TL_MR3420_V1 0x3421
-#define HWID_TL_MR3420_V2 0x3422
-#define HWID_TL_WA701N_V1 0x07010001
-#define HWID_TL_WA701N_V2 0x07010002
-#define HWID_TL_WA7210N_V2 0x7212
-#define HWID_TL_WA7510N_V1 0x7511
-#define HWID_TL_WA801ND_V1 0x08010001
-#define HWID_TL_WA830RE_V1 0x08300010
-#define HWID_TL_WA830RE_V2 0x0832
-#define HWID_TL_WA801ND_V2 0x08010002
-#define HWID_TL_WA801ND_V3 0x08010003
-#define HWID_TL_WA901ND_V1 0x09010001
-#define HWID_TL_WA901ND_V2 0x09010002
-#define HWID_TL_WA901ND_V4 0x09010004
-#define HWID_TL_WDR4300_V1_IL 0x43008001
-#define HWID_TL_WDR4900_V1 0x4901
-#define HWID_TL_WR703N_V1 0x07030101
-#define HWID_TL_WR720N_V3 0x07200103
-#define HWID_TL_WR720N_V4 0x07200104
-#define HWID_TL_WR741ND_V1 0x07410001
-#define HWID_TL_WR741ND_V4 0x07410004
-#define HWID_TL_WR740N_V1 0x0741
-#define HWID_TL_WR740N_V3 0x0743
-#define HWID_TL_WR743ND_V1 0x07430001
-#define HWID_TL_WR743ND_V2 0x07430002
-#define HWID_TL_WR841N_V1_50x08410002
-#define HWID_TL_WR841ND_V3 0x08410003
-#define HWID_TL_WR841ND_V5 0x08410005
-#define HWID_TL_WR841ND_V7 0x08410007
-#define HWID_TL_WR941ND_V2 0x09410002
-#define HWID_TL_WR941ND_V4 0x09410004
-#define HWID_TL_WR1043ND_V10x10430001
-#define HWID_TL_WR1043ND_V20x10430002
-#define HWID_TL_WR1041N_V2 0x10410002
-#define HWID_TL_WR2543N_V1 0x25430001
#define MD5SUM_LEN 16
@@ -119,13 +73,6 @@ struct flash_layout {
uint32_trootfs_ofs;
};
-struct board_info {
- char*id;
- uint32_thw_id;
- uint32_thw_rev;
- char*layout_id;
-};
-
/*
* Globals
*/
@@ -136,8 +83,6 @@ static char *version = "ver. 1.0";
static char *fw_ver = "0.0.0";
static uint32_t hdr_ver = HEADER_VERSION_V1;
-static char *board_id;
-static struct board_info *board;
static char *layout_id;
static struct flash_layout *layout;
static char *opt_hw_id;
@@ -167,12 +112,12 @@ static uint32_t reserved_space;
static struct file_info inspect_info;
static int extract = 0;
-char md5salt_normal[MD5SUM_LEN] = {
+static const char md5salt_normal[MD5SUM_LEN] = {
0xdc, 0xd7, 0x3a, 0xa5, 0xc3, 0x95, 0x98, 0xfb,
0xdd, 0xf9, 0xe7, 0xf4, 0x0e, 0xae, 0x47, 0x38,
};
-char md5salt_boot[MD5SUM_LEN] = {
+static const char md5salt_boot[MD5SUM_LEN] = {
0x8c, 0xef, 0x33, 0x5b, 0xd5, 0xc5, 0xce, 0xfa,
0xa7, 0x9c, 0x28, 0xda, 0xb2, 0xe9, 0x0f, 0x42,
};
@@ -217,7 +162,7 @@ static struct flash_layout layouts[] = {
}, {
.id = "16Mppc",
.fw_max_len = 0xf8,
- .kernel_la = 0x,
+ .kernel_la = 0x ,
.kernel_ep = 0xc000,
.rootfs_ofs = 0x2a,
}, {
@@ -225,242 +170,6 @@ static struct flash_layout layouts[] = {
}
};
-static struct board_info boards[] = {
- {
- .id = "TL-MR10Uv1",
- .hw_id = HWID_TL_MR10U_V1,
- .hw_rev = 1,
- .layout_id = "4Mlzma",
- }
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
I just tried. I get the same results as Baptiste — i.e. don’t get a radio0
device.
I removed the “disabled enabled” line from /etc/config/wireless.
I believe I built this image with the “default” MT7688 profile and I checked
the mt76 wireless driver was built-in.
Thoughts?
-m
--
Marc Nicholas
CTO, Wimoto Technologies Inc.
Unit 2, 300 Don Park Road, Markham, Ontario L3R 3A1 CANADA
+1.416.414.6272
On April 21, 2016 at 11:45:58 AM, Baptiste Clenet (bapcle...@gmail.com) wrote:
Will finish to try next week
Le 14 avr. 2016 20:20, "Baptiste Clenet" a écrit :
2016-04-14 16:58 GMT+02:00 John Crispin :
>
>
> On 14/04/2016 16:38, Baptiste Clenet wrote:
>> Marc, yes it has been added by John Crispins.
>>
>> I had nothing in etc/config/wireless, which is the right definition
>> for this driver? (I don't find any documentation). Tom, Adam, yes it
>> is defined.
>>
>> 2016-04-12 13:30 GMT+02:00 Adam Kent :
>>> Hi Baptiste
>>>
>>> Which board exactly? You may need to add the "wmac" definition to the
>>> relevant dts file. Have a look in
>>> target/linux/ramips/dts/.dts and make sure there's
>>> this:
>>>
>>> wmac@1030 {
>>> status = "okay";
>>> };
>>>
>>> - Adam
>>>
>>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
>>> wrote:
Hi,
I flashed the current tree on mt7688 board and no interface showed up
for wifi. Should I do something? I would like to try the mt76 wifi
driver on this board. (I added it with in menuconfig)
Cheers,
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>>
>>
>
>
> are you loading the mt76 driver ?
modprobe mt76?
It is already loaded:
cfg80211 215619 3 mt7603e
mac80211 389306 3 mt7603e
mt76 15734 2 mt7603e
mt7603e 27964 0
mt76x2e 34300 0
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
To add to that, an ifconfig radio0 yields “no such device”.
-m
--
Marc Nicholas
CTO, Wimoto Technologies Inc.
Unit 2, 300 Don Park Road, Markham, Ontario L3R 3A1 CANADA
+1.416.414.6272
On April 21, 2016 at 12:27:23 PM, Marc Nicholas (m...@wimoto.com) wrote:
I just tried. I get the same results as Baptiste — i.e. don’t get a radio0
device.
I removed the “disabled enabled” line from /etc/config/wireless.
I believe I built this image with the “default” MT7688 profile and I checked
the mt76 wireless driver was built-in.
Thoughts?
-m
--
Marc Nicholas
CTO, Wimoto Technologies Inc.
Unit 2, 300 Don Park Road, Markham, Ontario L3R 3A1 CANADA
+1.416.414.6272
On April 21, 2016 at 11:45:58 AM, Baptiste Clenet (bapcle...@gmail.com) wrote:
Will finish to try next week
Le 14 avr. 2016 20:20, "Baptiste Clenet" a écrit :
2016-04-14 16:58 GMT+02:00 John Crispin :
>
>
> On 14/04/2016 16:38, Baptiste Clenet wrote:
>> Marc, yes it has been added by John Crispins.
>>
>> I had nothing in etc/config/wireless, which is the right definition
>> for this driver? (I don't find any documentation). Tom, Adam, yes it
>> is defined.
>>
>> 2016-04-12 13:30 GMT+02:00 Adam Kent :
>>> Hi Baptiste
>>>
>>> Which board exactly? You may need to add the "wmac" definition to the
>>> relevant dts file. Have a look in
>>> target/linux/ramips/dts/.dts and make sure there's
>>> this:
>>>
>>> wmac@1030 {
>>> status = "okay";
>>> };
>>>
>>> - Adam
>>>
>>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
>>> wrote:
Hi,
I flashed the current tree on mt7688 board and no interface showed up
for wifi. Should I do something? I would like to try the mt76 wifi
driver on this board. (I added it with in menuconfig)
Cheers,
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>>
>>
>
>
> are you loading the mt76 driver ?
modprobe mt76?
It is already loaded:
cfg80211 215619 3 mt7603e
mac80211 389306 3 mt7603e
mt76 15734 2 mt7603e
mt7603e 27964 0
mt76x2e 34300 0
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Is the firmware getting loaded (/lib/firmware/mt7628_e2.bin)? It looks
like the fix in 48958 for this is in github.com/openwrt-mirror/ but not
in github.com/openwrt/.
On Thu, 2016-04-21 at 12:27 -0400, Marc Nicholas wrote:
> To add to that, an ifconfig radio0 yields “no such device”.
>
>
> -m
>
> --
> Marc Nicholas
> CTO, Wimoto Technologies Inc.
> Unit 2, 300 Don Park Road, Markham, Ontario L3R 3A1 CANADA
> +1.416.414.6272
>
> On April 21, 2016 at 12:27:23 PM, Marc Nicholas (m...@wimoto.com)
> wrote:
>
> >
> > I just tried. I get the same results as Baptiste — i.e. don’t get a
> > radio0 device.
> >
> >
> > I removed the “disabled enabled” line from /etc/config/wireless.
> >
> >
> > I believe I built this image with the “default” MT7688 profile and I
> > checked the mt76 wireless driver was built-in.
> >
> >
> > Thoughts?
> >
> >
> > -m
> >
> > --
> > Marc Nicholas
> > CTO, Wimoto Technologies Inc.
> > Unit 2, 300 Don Park Road, Markham, Ontario L3R 3A1 CANADA
> > +1.416.414.6272
> >
> > On April 21, 2016 at 11:45:58 AM, Baptiste Clenet
> > (bapcle...@gmail.com) wrote:
> >
> > > Will finish to try next week
> > >
> > > Le 14 avr. 2016 20:20, "Baptiste Clenet" a
> > > écrit :
> > > 2016-04-14 16:58 GMT+02:00 John Crispin
> > > :
> > > >
> > > >
> > > > On 14/04/2016 16:38, Baptiste Clenet wrote:
> > > >> Marc, yes it has been added by John Crispins.
> > > >>
> > > >> I had nothing in etc/config/wireless, which is the
> > > right definition
> > > >> for this driver? (I don't find any documentation). Tom,
> > > Adam, yes it
> > > >> is defined.
> > > >>
> > > >> 2016-04-12 13:30 GMT+02:00 Adam Kent
> > > :
> > > >>> Hi Baptiste
> > > >>>
> > > >>> Which board exactly? You may need to add the "wmac"
> > > definition to the
> > > >>> relevant dts file. Have a look in
> > > >>> target/linux/ramips/dts/.dts and make
> > > sure there's
> > > >>> this:
> > > >>>
> > > >>> wmac@1030 {
> > > >>> status = "okay";
> > > >>> };
> > > >>>
> > > >>> - Adam
> > > >>>
> > > >>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
> > > wrote:
> > > Hi,
> > >
> > > I flashed the current tree on mt7688 board and no
> > > interface showed up
> > > for wifi. Should I do something? I would like to try
> > > the mt76 wifi
> > > driver on this board. (I added it with in menuconfig)
> > >
> > > Cheers,
> > >
> > > --
> > > Baptiste
> > > ___
> > > openwrt-devel mailing list
> > > openwrt-devel@lists.openwrt.org
> > >
> > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > > are you loading the mt76 driver ?
> > > modprobe mt76?
> > > It is already loaded:
> > > cfg80211 215619 3 mt7603e
> > > mac80211 389306 3 mt7603e
> > > mt76 15734 2 mt7603e
> > > mt7603e27964 0
> > > mt76x2e34300 0
> > > > ___
> > > > openwrt-devel mailing list
> > > > openwrt-devel@lists.openwrt.org
> > > >
> > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> > >
> > >
> > >
> > > --
> > > Baptiste
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Is the firmware getting loaded (/lib/firmware/mt7628_e2.bin)? It looks like the fix in 48958 for this is in github.com/openwrt-mirror/ but not in github.com/openwrt/. Yes, the firmware is getting loaded based on the boot logs. I’ve gotten a bit further and have AP mode running. But can’t for the life of me get STA to work….can’t even scan for APs. :-/ Thanks! -m -- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: add support for Planex MZK-EX300NP
Hi,
fails to apply for some reason, please rebase and resend. there is one
small nitpick inline.
On 14/04/2016 16:59, YuheiOKAWA wrote:
> MZK-EX300NP is MT7620A based wifi repeater.
> Built-in power supply.
> 64MiB RAM, 8MiB SPI Flash, non Wired Ethernet.
>
> Signed-off-by: YuheiOKAWA
> ---
> target/linux/ramips/base-files/etc/board.d/01_leds | 1 +
> .../linux/ramips/base-files/etc/board.d/02_network | 1 +
> target/linux/ramips/base-files/etc/diag.sh | 1 +
> target/linux/ramips/base-files/lib/ramips.sh | 3 +
> .../ramips/base-files/lib/upgrade/platform.sh | 1 +
> target/linux/ramips/dts/MZK-EX300NP.dts| 132
> +
> target/linux/ramips/image/mt7620.mk| 2 +
> target/linux/ramips/mt7620/profiles/planex.mk | 16 +++
> 8 files changed, 157 insertions(+)
> create mode 100644 target/linux/ramips/dts/MZK-EX300NP.dts
> create mode 100644 target/linux/ramips/mt7620/profiles/planex.mk
>
> diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds
> b/target/linux/ramips/base-files/etc/board.d/01_leds
> index 5816e60..e8305d0 100755
> --- a/target/linux/ramips/base-files/etc/board.d/01_leds
> +++ b/target/linux/ramips/base-files/etc/board.d/01_leds
> @@ -118,6 +118,7 @@ dir-615-h1)
> ucidef_set_led_default "status" "Status LED (amber)"
> "$board:amber:status" "0"
> set_wifi_led "rt2800pci-phy0::radio"
> ;;
> +mzk-ex300np|\
> dir-620-d1)
> set_wifi_led "$board:green:wifi"
> ;;
> diff --git a/target/linux/ramips/base-files/etc/board.d/02_network
> b/target/linux/ramips/base-files/etc/board.d/02_network
> index 4b65d36..db2e6d9 100755
> --- a/target/linux/ramips/base-files/etc/board.d/02_network
> +++ b/target/linux/ramips/base-files/etc/board.d/02_network
> @@ -160,6 +160,7 @@ ramips_setup_interfaces()
> "0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "9@eth0"
> ;;
> d105|\
> + mzk-ex300np|\
this should be below hpm and not above it
John
> hpm|\
> na930|\
> wli-tx4-ag300n)
> diff --git a/target/linux/ramips/base-files/etc/diag.sh
> b/target/linux/ramips/base-files/etc/diag.sh
> index daa7fb1..8692da9 100644
> --- a/target/linux/ramips/base-files/etc/diag.sh
> +++ b/target/linux/ramips/base-files/etc/diag.sh
> @@ -151,6 +151,7 @@ get_status_led() {
> whr-600d)
> status_led="$board:orange:wifi"
> ;;
> + mzk-ex300np|\
> rt-n10-plus|\
> tew-691gr|\
> tew-692gr|\
> diff --git a/target/linux/ramips/base-files/lib/ramips.sh
> b/target/linux/ramips/base-files/lib/ramips.sh
> index 5f1df7b..b1cb2eb 100755
> --- a/target/linux/ramips/base-files/lib/ramips.sh
> +++ b/target/linux/ramips/base-files/lib/ramips.sh
> @@ -292,6 +292,9 @@ ramips_board_detect() {
> *"MZK-DP150N")
> name="mzk-dp150n"
> ;;
> + *"MZK-EX300NP")
> + name="mzk-ex300np"
> + ;;
> *"MZK-W300NH2"*)
> name="mzk-w300nh2"
> ;;
> diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
> b/target/linux/ramips/base-files/lib/upgrade/platform.sh
> index c329dce..d8e6f66 100755
> --- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
> +++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
> @@ -87,6 +87,7 @@ platform_check_image() {
> mr-102n|\
> mt7628|\
> mzk-dp150n|\
> + mzk-ex300np|\
> mzk-w300nh2|\
> mzk-wdpr|\
> nbg-419n|\
> diff --git a/target/linux/ramips/dts/MZK-EX300NP.dts
> b/target/linux/ramips/dts/MZK-EX300NP.dts
> new file mode 100644
> index 000..51e87ad
> --- /dev/null
> +++ b/target/linux/ramips/dts/MZK-EX300NP.dts
> @@ -0,0 +1,132 @@
> +/dts-v1/;
> +
> +/include/ "mt7620a.dtsi"
> +
> +/ {
> + compatible = "ralink,mt7620a-soc";
> + model = "Planex MZK-EX300NP";
> +
> + palmbus@1000 {
> + gpio1: gpio@638 {
> + status = "okay";
> + };
> +
> + gpio3: gpio@688 {
> + status = "okay";
> + };
> +
> + spi@b00 {
> + status = "okay";
> +
> + m25p80@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "jedec,spi-nor";
> + reg = <0 0>;
> + linux,modalias = "m25p80", "w25q64";
> + spi-max-frequency = <1000>;
> +
> + partition@0 {
> + label = "u-boot";
> + reg = <0x0 0x3>;
> + read-only;
> + };
> +
> + partition@3 {
> + label = "u-boot-env";
> +
[OpenWrt-Devel] IEEE 802.11s
Hi all, I am a newbie to embedded devices. I have used openwrt for building mesh network. I am able to build firmware from the source code and get it working. But I want to modifying certain things in Mesh Routing algorithm HWMP, kind of implementing a new routing algorithm. In generic linux kernel source code, I am able to figure the location of the files for IEEE 802.11. But when I look into the source code of OpenWRT, I am unable to find the same. Is there any place where I should look for the IEEE 802.11 and IEEE 802.11 Mesh ? I am kind of what to implement my own routing algorithm for Mesh. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] IEEE 802.11s
Hi all, I am a newbie to embedded devices. I have used openwrt for building mesh network. I am able to build firmware from the source code and get it working. But I want to modifying certain things in Mesh Routing algorithm HWMP, kind of implementing a new routing algorithm. In generic linux kernel source code, I am able to figure the location of the files for IEEE 802.11. But when I look into the source code of OpenWRT, I am unable to find the same. Is there any place where I should look for the IEEE 802.11 and IEEE 802.11 Mesh ? I am kind of what to implement my own routing algorithm for Mesh. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: add support for Planex CS-QR10
Hi,
this one also fails to apply. please rebase/resend
JOhn
On 12/04/2016 14:16, YuheiOKAWA wrote:
> CS-QR10 is MT7620A based IP Camera.
>
> the camera and sound does not work with kernel 4.4.
> - camera chip is sn9c291.
> - sound chip is wm8960.
>
> Signed-off-by: YuheiOKAWA
> ---
> target/linux/ramips/base-files/etc/board.d/01_leds | 3 +-
> .../linux/ramips/base-files/etc/board.d/02_network | 1 +
> target/linux/ramips/base-files/etc/diag.sh | 1 +
> target/linux/ramips/base-files/lib/ramips.sh | 3 +
> .../ramips/base-files/lib/upgrade/platform.sh | 1 +
> target/linux/ramips/dts/CS-QR10.dts| 163
> +
> target/linux/ramips/image/mt7620.mk| 2 +
> target/linux/ramips/mt7620/profiles/planex.mk | 19 +++
> 8 files changed, 192 insertions(+), 1 deletion(-)
> create mode 100644 target/linux/ramips/dts/CS-QR10.dts
> create mode 100644 target/linux/ramips/mt7620/profiles/planex.mk
>
> diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds
> b/target/linux/ramips/base-files/etc/board.d/01_leds
> index 5816e60..e319f36 100755
> --- a/target/linux/ramips/base-files/etc/board.d/01_leds
> +++ b/target/linux/ramips/base-files/etc/board.d/01_leds
> @@ -30,7 +30,8 @@ br-6475nd|\
> mzk-w300nh2)
> set_wifi_led "$board:amber:wlan"
> ;;
> -a5-v11)
> +a5-v11|\
> +cs-qr10)
> ucidef_set_led_default "power" "POWER" "$board:red:power" "1"
> ;;
> ai-br100)
> diff --git a/target/linux/ramips/base-files/etc/board.d/02_network
> b/target/linux/ramips/base-files/etc/board.d/02_network
> index 4b65d36..416b13c 100755
> --- a/target/linux/ramips/base-files/etc/board.d/02_network
> +++ b/target/linux/ramips/base-files/etc/board.d/02_network
> @@ -159,6 +159,7 @@ ramips_setup_interfaces()
> ucidef_add_switch "switch0" \
> "0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "9@eth0"
> ;;
> + cs-qr10|\
> d105|\
> hpm|\
> na930|\
> diff --git a/target/linux/ramips/base-files/etc/diag.sh
> b/target/linux/ramips/base-files/etc/diag.sh
> index daa7fb1..233d15c 100644
> --- a/target/linux/ramips/base-files/etc/diag.sh
> +++ b/target/linux/ramips/base-files/etc/diag.sh
> @@ -32,6 +32,7 @@ get_status_led() {
> status_led="$board:green:power"
> ;;
> a5-v11|\
> + cs-qr10|\
> d105|\
> dcs-930l-b1|\
> ex2700|\
> diff --git a/target/linux/ramips/base-files/lib/ramips.sh
> b/target/linux/ramips/base-files/lib/ramips.sh
> index 5f1df7b..2df2591 100755
> --- a/target/linux/ramips/base-files/lib/ramips.sh
> +++ b/target/linux/ramips/base-files/lib/ramips.sh
> @@ -88,6 +88,9 @@ ramips_board_detect() {
> *"CF-WR800N")
> name="cf-wr800n"
> ;;
> + *"CS-QR10")
> + name="cs-qr10"
> + ;;
> *"CY-SWR1100")
> name="cy-swr1100"
> ;;
> diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
> b/target/linux/ramips/base-files/lib/upgrade/platform.sh
> index c329dce..af7fb12 100755
> --- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
> +++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
> @@ -34,6 +34,7 @@ platform_check_image() {
> broadway|\
> carambola|\
> cf-wr800n|\
> + cs-qr10|\
> d105|\
> dap-1350|\
> db-wrt01|\
> diff --git a/target/linux/ramips/dts/CS-QR10.dts
> b/target/linux/ramips/dts/CS-QR10.dts
> new file mode 100644
> index 000..08299e3
> --- /dev/null
> +++ b/target/linux/ramips/dts/CS-QR10.dts
> @@ -0,0 +1,163 @@
> +/dts-v1/;
> +
> +/include/ "mt7620a.dtsi"
> +
> +/ {
> + compatible = "ralink,mt7620a-soc";
> + model = "Planex CS-QR10";
> +
> + palmbus@1000 {
> + gpio0: gpio@600 {
> + status = "okay";
> + };
> +
> + gpio1: gpio@638 {
> + status = "okay";
> + };
> +
> + gpio2: gpio@660 {
> + status = "okay";
> + };
> +
> + gpio3: gpio@688 {
> + status = "okay";
> + };
> +
> + i2c@900 {
> + status = "okay";
> + };
> +
> + i2s: i2s@a00 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pcm_i2s_pins>;
> + };
> +
> + spi@b00 {
> + status = "okay";
> +
> + m25p80@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "jedec,spi-nor";
> + reg = <0 0>;
> + linux,modalias = "m25p80", "mx25l6405d";
> + spi-max-frequency = <1000>;
> +
> +
[OpenWrt-Devel] [PATCH] oxnas: add missing semicolon
A missing semicolon in the gpio-keys-polled section of ox820-akitio.dts
caused the build to break. Add it.
Signed-off-by: Daniel Golle
---
target/linux/oxnas/files/arch/arm/boot/dts/ox820-akitio.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/oxnas/files/arch/arm/boot/dts/ox820-akitio.dts
b/target/linux/oxnas/files/arch/arm/boot/dts/ox820-akitio.dts
index 5da4fa4..4dc969c 100644
--- a/target/linux/oxnas/files/arch/arm/boot/dts/ox820-akitio.dts
+++ b/target/linux/oxnas/files/arch/arm/boot/dts/ox820-akitio.dts
@@ -76,7 +76,7 @@
label = "power";
gpios = <&GPIOA 11 1>;
linux,code = <116>;
- }
+ };
reset {
label = "reset";
gpios = <&GPIOB 6 1>;
--
2.8.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] lantiq: Fix typo in LED diag script.
Signed-off-by: Vittorio Gambaletta
---
--- a/target/linux/lantiq/base-files/etc/diag.sh
+++ b/target/linux/lantiq/base-files/etc/diag.sh
@@ -25,7 +25,7 @@
;;
done)
status_led_off
- [ -n "$running" ] & {
+ [ -n "$running" ] && {
status_led="$running"
status_led_on
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] lantiq: Fix status LED on TDW89X0 after boot is completed.
After recent patches, the status LED on this router would stay switched off after boot is completed. A switched off status LED often indicates a boot failure (eg. kernel panic), so fix this and get back to the previous behaviour. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/dts/TDW89X0.dtsi +++ b/target/linux/lantiq/dts/TDW89X0.dtsi @@ -8,6 +8,7 @@ /* the power led can't be controlled, use the wps led instead */ boot = &wps; failsafe = &wps; + running = &wps; dsl = &dsl; internet = &internet; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: ath9k: add GPIO support for AR9280 chip
From: Michal Cieslakiewicz Date: Thu, 21 Apr 2016 23:03:28 +0200 Subject: [PATCH] mac80211: ath9k: add GPIO support for AR9280 chip Enable access to GPIO on Atheros wireless chip AR9280. Support for 9280 is added to existing 9285/9287 subsystem because these 3 chips differ only in number of GPIO pins. Signed-off-by: Michal Cieslakiewicz --- Tested successfully on Netgear WNDR3700v1h2 (aka v2). This device has two AR9280 units and both are recognized properly and reported in /sys/kernel/debug/gpio. In WNDR3700v2 only local WiFi LEDs are connected to wireless chips, other controls are wired to SoC GPIO. .../patches/550-ath9k_add_ar9280_gpio_chip.patch | 27 ++ 1 file changed, 27 insertions(+) create mode 100644 package/kernel/mac80211/patches/550-ath9k_add_ar9280_gpio_chip.patch diff --git a/package/kernel/mac80211/patches/550-ath9k_add_ar9280_gpio_chip.patch b/package/kernel/mac80211/patches/550-ath9k_add_ar9280_gpio_chip.patch new file mode 100644 index 000..3fe7e43 --- /dev/null +++ b/package/kernel/mac80211/patches/550-ath9k_add_ar9280_gpio_chip.patch @@ -0,0 +1,27 @@ +From: Michal Cieslakiewicz +Date: Thu, 21 Apr 2016 23:00:54 +0200 +Subject: [PATCH] mac80211: ath9k: add GPIO support for AR9280 chip + +Enable access to GPIO on Atheros wireless chip AR9280. +Support for 9280 is added to existing 9285/9287 subsystem +because these 3 chips differ only in number of GPIO pins. + +Signed-off-by: Michal Cieslakiewicz +--- +--- a/drivers/net/wireless/ath/ath9k/gpio.c b/drivers/net/wireless/ath/ath9k/gpio.c +@@ -88,11 +88,13 @@ static void ath9k_register_gpio_chip(str + struct ath9k_gpio_chip *gc; + u16 ng; + +- /* for now only AR9285 and AR9287 are recognized */ ++ /* supported chips are AR9280, AR9285 and AR9287 */ + if (AR_SREV_9287(sc->sc_ah)) + ng = AR9287_NUM_GPIO; + else if (AR_SREV_9285(sc->sc_ah)) + ng = AR9285_NUM_GPIO; ++ else if (AR_SREV_9280(sc->sc_ah)) ++ ng = AR928X_NUM_GPIO; + else + return; + -- 2.8.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] IEEE 802.11s
Prabhu, OpenWRT does not have source code of projects inside its own source. All needed sources, including the linux kernel, is downloaded during the build. You'll only find kernel patches and the kernel packages definition (which packs modules). If you want to see the result kernel source, build OpenWRT once and check builddir. Regards, Em qui, 21 de abr de 2016 16:34, Prabhu Janakaraj escreveu: > Hi all, > I am a newbie to embedded devices. I have used openwrt for building mesh > network. I am able to build firmware from the source code and get it > working. > > But I want to modifying certain things in Mesh Routing algorithm HWMP, > kind of implementing a new routing algorithm. > > In generic linux kernel source code, I am able to figure the location of > the files for IEEE 802.11. But when I look into the source code of OpenWRT, > I am unable to find the same. Is there any place where I should look for > the IEEE 802.11 and IEEE 802.11 Mesh ? > > I am kind of what to implement my own routing algorithm for Mesh. > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > -- Luiz Angelo Daros de Luca luizl...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH/RFC] dnsmasq: run as dedicated UID/GID
Running dnsmasq in a dedicated user/group allows matching its outgoing
traffic more easily using iptables' owner match.
Add UID/GID to the package metadata and append the user/group
parameters to the init script.
Signed-off-by: Daniel Golle
---
package/network/services/dnsmasq/Makefile | 1 +
package/network/services/dnsmasq/files/dnsmasq.init | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/network/services/dnsmasq/Makefile
b/package/network/services/dnsmasq/Makefile
index a5c3740..9a0f165 100644
--- a/package/network/services/dnsmasq/Makefile
+++ b/package/network/services/dnsmasq/Makefile
@@ -34,6 +34,7 @@ define Package/dnsmasq/Default
CATEGORY:=Base system
TITLE:=DNS and DHCP server
URL:=http://www.thekelleys.org.uk/dnsmasq/
+ USERID:=dnsmasq=65453:dnsmasq=65453
endef
define Package/dnsmasq
diff --git a/package/network/services/dnsmasq/files/dnsmasq.init
b/package/network/services/dnsmasq/files/dnsmasq.init
index 61ded6a..83fcbb0 100644
--- a/package/network/services/dnsmasq/files/dnsmasq.init
+++ b/package/network/services/dnsmasq/files/dnsmasq.init
@@ -218,6 +218,8 @@ dnsmasq() {
mkdir -p /tmp/hosts /tmp/dnsmasq.d
xappend "--addn-hosts=/tmp/hosts"
xappend "--conf-dir=/tmp/dnsmasq.d"
+ xappend "--user=dnsmasq"
+ xappend "--group=dnsmasq"
echo >> $CONFIGFILE
@@ -589,7 +591,7 @@ start_service() {
if [ ! -f "$TIMESTAMPFILE" ]; then
touch "$TIMESTAMPFILE"
- chown nobody.nogroup "$TIMESTAMPFILE"
+ chown dnsmasq.dnsmasq "$TIMESTAMPFILE"
fi
echo "# auto-generated config file from /etc/config/dhcp" > $CONFIGFILE
--
2.8.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] lantiq: Fix status LED on TDW89X0 after boot is completed.
Am 21.04.2016 um 23:43 schrieb Vittorio Gambaletta (VittGam): After recent patches, the status LED on this router would stay switched off after boot is completed. A switched off status LED often indicates a boot failure (eg. kernel panic), so fix this and get back to the previous behaviour. NAK This change was intentional. Personally, I don't like the idea of using the WPS led as permanent (running) status led. I've never tried it, but I may be possible to use WPS with hostapd and show the status of the WPS action using the WPS led. I like to prevent such a double use of leds. The basic idea was to let the WPS led blink as long as the device boots and switch it off at the time the boot has finished. Which means an unsuccessful boot is indicated by a still blinking WPS led. Mathias Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/dts/TDW89X0.dtsi +++ b/target/linux/lantiq/dts/TDW89X0.dtsi @@ -8,6 +8,7 @@ /* the power led can't be controlled, use the wps led instead */ boot = &wps; failsafe = &wps; + running = &wps; dsl = &dsl; internet = &internet; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] lantiq: Fix typo in LED diag script.
Am 21.04.2016 um 23:43 schrieb Vittorio Gambaletta (VittGam):
Signed-off-by: Vittorio Gambaletta
Acked-by: Mathias Kresin
---
--- a/target/linux/lantiq/base-files/etc/diag.sh
+++ b/target/linux/lantiq/base-files/etc/diag.sh
@@ -25,7 +25,7 @@
;;
done)
status_led_off
- [ -n "$running" ] & {
+ [ -n "$running" ] && {
status_led="$running"
status_led_on
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: fix brnImage build
Use the kernel with the appended dtb as base, otherwise the kernel will panic with "no dtb found". Signed-off-by: Mathias Kresin --- target/linux/lantiq/image/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/lantiq/image/Makefile b/target/linux/lantiq/image/Makefile index c3cb48a..e63c134 100644 --- a/target/linux/lantiq/image/Makefile +++ b/target/linux/lantiq/image/Makefile @@ -37,7 +37,7 @@ define PatchKernelLzma endef define MkBrnImage - mkbrncmdline -i $(KDIR)/vmlinux-$(5) -o $(KDIR)/vmlinux-$(5)-brn BRN-BOOT $(7) + mkbrncmdline -i $(KDIR)/vmlinux-$(5).tmp -o $(KDIR)/vmlinux-$(5)-brn BRN-BOOT $(7) $(call CompressLzma,$(KDIR)/vmlinux-$(5)-brn,$(KDIR)/vmlinux-$(5)-brn.lzma) mkbrnimg -s $(1) -m $(2) -p $(3) -o $(4) $(KDIR)/vmlinux-$(5)-brn.lzma $(KDIR)/root.$(6) endef -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
