Signed-off-by: Daniel Golle dan...@makrotopia.org
---
package/kernel/linux/modules/block.mk | 16
target/linux/oxnas/Makefile | 4 ++--
target/linux/oxnas/config-3.14| 2 --
target/linux/oxnas/config-3.18| 2 --
4 files changed, 18 insertions(+), 6
On 12/12/2014 11:26, yangbo wrote:
Hi, Please remove me from spam list. Maybe I send similar mail to
offen... Thank you. ___
openwrt-devel mailing list openwrt-devel@lists.openwrt.org
Quoting Robert P. J. Day:
building for ar71xx:
...
make[2]: *** [package/kernel/lantiq/ltq-tapi/compile] Error 2
...
this build worked fine yesterday, pulled to update to current trunk
and now the above.
You are probably including asterisk in your build, right?
The reason is a change in
Y1S has 2 Gigabit LAN.
So I used the following:
y1 |\
y1s)
ucidef_set_interfaces_lan_wan eth0.1 eth0.2
ucidef_add_switch switch0 1 1
ucidef_add_switch_vlan switch0 1 0 1 2 3 5 6t 7
ucidef_add_switch_vlan switch0 2 4 6t
Quoting Hannu Nyman hannu.ny...@iki.fi:
Quoting Robert P. J. Day:
building for ar71xx:
...
make[2]: *** [package/kernel/lantiq/ltq-tapi/compile] Error 2
...
this build worked fine yesterday, pulled to update to current trunk
and now the above.
You are probably including asterisk in your
On 2014-12-12 05:16, Yousong Zhou wrote:
On 12 December 2014 at 00:42, Felix Fietkau n...@openwrt.org wrote:
On 2014-11-11 11:34, Yousong Zhou wrote:
ustream_ssl_check_conn() may be called by .notify_write while a previous
SSL_connect() is still in process. This can happen because the
Michael Heimpold wrote:
Remove 'series' as all other targets do not use this, too. It
should be obviously clear, that this target refer to a
whole CPU family.
Signed-off-by: Michael Heimpold m...@heimpold.de
---
Hi Michael,
Applied most of the series in r43646-43651, r43657, I've put an
On 12/12/2014 14:46, Zoltan HERPAI wrote:
Michael Heimpold wrote:
Remove 'series' as all other targets do not use this, too. It
should be obviously clear, that this target refer to a
whole CPU family.
Signed-off-by: Michael Heimpold m...@heimpold.de
---
Hi Michael,
Applied most
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
package/kernel/linux/modules/block.mk | 16
target/linux/oxnas/Makefile | 5 +++--
target/linux/oxnas/config-3.14| 2 --
target/linux/oxnas/config-3.18| 2 --
4 files changed, 19 insertions(+), 6
On 12 December 2014 at 19:36, Felix Fietkau n...@openwrt.org wrote:
On 2014-12-12 05:16, Yousong Zhou wrote:
On 12 December 2014 at 00:42, Felix Fietkau n...@openwrt.org wrote:
On 2014-11-11 11:34, Yousong Zhou wrote:
ustream_ssl_check_conn() may be called by .notify_write while a previous
On Thu, Dec 11, 2014 at 12:51 AM, Álvaro Fernández Rojas
nolt...@gmail.com wrote:
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com
---
diff --git a/target/linux/brcm63xx/config-3.14
b/target/linux/brcm63xx/config-3.14
index dd27f47..f94c567 100644
---
On 12/12/2014 15:12, Jonas Gorski wrote:
or the gpio-base problem, we should be able to register appropriate
platform data for it as OF_DEV_AUXDATA() in of_platform_populate.
e.g.
struct bgpio_pdata gpio0_pdata = {
.base = 0,
};
struct bgpio_pdata gpio1_pdata = {
On Thu, Dec 11, 2014 at 12:52 AM, Álvaro Fernández Rojas
nolt...@gmail.com wrote:
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com
---
diff --git a/target/linux/brcm63xx/patches-3.14/375-GPIO-DT-over-legacy.patch
b/target/linux/brcm63xx/patches-3.14/375-GPIO-DT-over-legacy.patch
new
On Fri, Dec 12, 2014 at 3:17 PM, John Crispin blo...@openwrt.org wrote:
On 12/12/2014 15:12, Jonas Gorski wrote:
or the gpio-base problem, we should be able to register appropriate
platform data for it as OF_DEV_AUXDATA() in of_platform_populate.
e.g.
struct bgpio_pdata gpio0_pdata = {
On 12/12/2014 15:33, Jonas Gorski wrote:
On Fri, Dec 12, 2014 at 3:17 PM, John Crispin blo...@openwrt.org wrote:
On 12/12/2014 15:12, Jonas Gorski wrote:
or the gpio-base problem, we should be able to register appropriate
platform data for it as OF_DEV_AUXDATA() in of_platform_populate.
Hi Luis,
i just added a fix to my local tree and will push during the evening.
it fixes the duplicate uartf pinmux problem. please note that when
enabling uart the uartlite used for tty0 gets moved to tty1 so you need
to fix up the cmdline
John
On 02/12/2014 01:50, Luis Soltero wrote:
This patch adds soc support for QCA9561 and TP9343.
TP9343 is a reduced version of QCA9561, which can be found in TP-LINK routers
in China.
The qca956x_wmac has not yet been supported by ath9k.
tested on TL-WDR6500 and TL-WR882N v1 (Chinese version)
Signed-off-by: Weijie Gao
The mvebu image Makefile directly calls the padjffs2 utility, while there's an
generic make function to do just that. Switch to it
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On boards with large page size, the rootfs we generate might end up using less
PEB than the minimum number required by UBI for a dynamic volume.
Change the rootfs to a static volume, which removes such a requirement, and
isn't changing anything, since our rootfs is in read only anyway.
Create a generic board relying on the board mechanism we just introduced.
So far, the behaviour hasn't really changed, the same boards are supported,
with the same options.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
target/linux/mvebu/boards/generic.mk | 18
Even though we always build all the board images for a given target, some
options widely differ from one board to another when it comes to hardware
configuration.
Such an option for example is the NAND setup, which depends on the NAND chip
itself, that obviously varies from one board to another.
The Mirabox has different NAND options than the one used in the generic board,
mostly because of its 512k page size.
Add a new board for it.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
target/linux/mvebu/boards/generic.mk | 1 -
target/linux/mvebu/boards/mirabox.mk | 13
This adds a LED trigger for each SATA port if the kernel config option
CONFIG_ATA_LEDS is set.
In order not to cause any oldconfig confusion on targets, the option depends
on CONFIG_ARCH_WANTS_LIBATA_LEDS, so target maintainers have to opt-in in
order to use this (it could e.g. be useful on
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
target/linux/oxnas/config-3.14| 1 +
target/linux/oxnas/config-3.18| 1 +
target/linux/oxnas/files/arch/arm/boot/dts/ox820-kd20.dts | 2 ++
... and i assume this is already en-route to upstream ?
On 12/12/2014 17:07, Daniel Golle wrote:
This adds a LED trigger for each SATA port if the kernel config
option CONFIG_ATA_LEDS is set. In order not to cause any oldconfig
confusion on targets, the option depends on
On 2014-12-05 15:36, Cristian Morales Vega wrote:
Avoids flooding the network with multicast data.
Signed-off-by: Cristian Morales Vega crist...@samknows.com
---
Since I guess not all the switches support this... Good idea? Is some OpenWRT
package expecting to receive the multicast
On 12/12/2014 17:07, Daniel Golle wrote:
++#ifdef CONFIG_ATA_LEDS
++ap-ledtrig = kzalloc(sizeof(struct led_trigger), GFP_KERNEL);
++#endif
can you change all of these to the new IS_ENABLED() api
John
___
openwrt-devel mailing list
On 2014-12-09 11:47, John Szakmeister wrote:
This fixes an issue where the toolchain/prepare step could run, but some
of the necessary host tools might be missing.
Signed-off-by: John Szakmeister j...@szakmeister.net
---
This is a resend of a patch I sent earlier
On 2014-12-11 23:36, Dan Staples wrote:
Currently, the only way for cgi scripts to determine if the request
was made over SSL seems to be to check if the SERVER_PORT environment
variable is set to 443, which is less than ideal. This sets the HTTPS
environment variable, like the first version
Switch to a dumber implementation that will be easier to maintain in the long
run, with only if statements instead of having nested subst calls.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
include/kernel.mk | 15 +++
1 file changed, 11 insertions(+), 4
x64 is handled by the x86 architecture in Linux, add a case for it in
LINUX_KARCH.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
include/kernel.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/kernel.mk b/include/kernel.mk
index
Hi,
This is the fourth attempt at using the defconfig mechanism for the
kernel configuration instead of having full fledged configuration
written by hand, and very tedious to maintain.
Changes from v3:
- Simplify a bit the LINUX_KARCH logic in order to use findstring
instead of a long list
This adds a LED trigger for each SATA port if the kernel config option
CONFIG_ATA_LEDS is set.
In order not to cause any oldconfig confusion on targets, the option depends
on CONFIG_ARCH_WANTS_LIBATA_LEDS, so target maintainers have to opt-in in
order to use this (it could e.g. be useful on
On Fri, Dec 12, 2014 at 5:02 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Now that we use the defconfigs, we can remove all the options at their default
value.
This causes a lot of kernel-config changes for e.g bcm63xx_smp with
3.18, several of which are unwanted (e.g. enabling of
On 2014-12-12 17:02, Maxime Ripard wrote:
x64 is handled by the x86 architecture in Linux, add a case for it in
LINUX_KARCH.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Applied the first two patches in this series.
- Felix
___
On Fri, Dec 12, 2014 at 04:21:02PM +0100, Maxime Ripard wrote:
On boards with large page size, the rootfs we generate might end up using less
PEB than the minimum number required by UBI for a dynamic volume.
Change the rootfs to a static volume, which removes such a requirement, and
isn't
cosmetics. clean a style issue introduced by r43674.
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
target/linux/generic/patches-3.14/834-ledtrig-libata.patch | 2 +-
target/linux/generic/patches-3.18/834-ledtrig-libata.patch | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff
Align this file with the style of most other modules.mk.
Signed-off-by: Michael Heimpold m...@heimpold.de
---
This is a rebased version because previous patch do no apply cleanly
anymore. While at, adjust the wording a little bit.
BR, mhei
target/linux/mxs/modules.mk | 74
We've been carrying around that patch for a while now and didn't
ever encounter any problem on non-UBI flashtypes. So I guess the
8kB extra space won't hurt on modern platforms which might even make
use of their U-Boot environment being stored in UBI.
Let me know if there are any targets missing
From: Gergely Kiss mail.g...@gmail.com
Fix extroot functionality for devices where rootfs is on a ubifs partition
Signed-off-by: Gergely Kiss mail.g...@gmail.com
Tested-by: Gergely Kiss mail.g...@gmail.com
---
Originally created by forum user Hiro.AK47 for the 14.07 branch.
I've created a new
Actually I don't know what port 7 is.
Port 5 is not required for Y1.
2014-12-12 22:20 GMT+08:00 John Crispin blo...@openwrt.org:
On 12/12/2014 12:21, 郭传鈜 wrote:
Y1S has 2 Gigabit LAN. So I used the following: y1 |\ y1s)
ucidef_set_interfaces_lan_wan eth0.1 eth0.2 ucidef_add_switch
Works great to power-off the kd20 ;)
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
target/linux/oxnas/config-3.14| 4
target/linux/oxnas/config-3.18| 4
target/linux/oxnas/files/arch/arm/boot/dts/ox820-kd20.dts | 5 +
Good evening,
I've flashed a Netgear WNDR3400 v1 with final official Barrier
Breaker image.
I've discovered that all mac addresses are the same for lan, wan and
wireless, which I find odd.
My search found this patch:
Aigale Ai-BR100 is a router with mt7620a soc.
There are only 2 lights on the board (WAN and WLAN) so I used the wlan light as
the status led.
Signed-off-by: 郭传鈜 gch981...@gmail.com
---
target/linux/ramips/base-files/etc/board.d/01_leds | 4 +
.../linux/ramips/base-files/etc/board.d/02_network
define speed-map and include kmod-hwmon-gpiofan in kd20 profile
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
target/linux/oxnas/files/arch/arm/boot/dts/ox820-kd20.dts | 2 ++
target/linux/oxnas/profiles/100-Generic.mk| 2 +-
2 files changed, 3 insertions(+), 1
i think this should the opt-in not opt-out. target maintainers should
set it only if they have boards with the env stored inside ubi.
John
On 12/12/2014 23:59, Daniel Golle wrote:
We've been carrying around that patch for a while now and didn't
ever encounter any problem on non-UBI
Hi lynxis,
ah the stray ath10k fw warning ... thanks, one todo less on my list :)
John
On 13/12/2014 08:19, Alexander Couzens wrote:
It moves firmware patch code behind an extra check on board_name.
Otherwise it will calculate firmware checksum for unaffected boards.
It also reduce
On 13/12/2014 08:04, Yousong Zhou wrote:
+define Profile/AIBR100
+ NAME:=Aigale Ai-BR100
+ PACKAGES:=\
+ kmod-usb-core \
+ kmod-usb-ohci \
+ kmod-ledtrig-usbdev \
+ kmod-usb2
+endef
kmod-ledtrig-usbdev should be
48 matches
Mail list logo
