The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Peter,
On Sun, Nov 26, 2017 at
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Zoltan,
On Wed, Sep 6, 2017 at
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On Sun, May 14, 2017 at 10:13 PM,
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Alan,
first I'd like to say th
s
binding/owl-loader")
Signed-off-by: Martin Blumenstingl
---
This patch should probably also be backported to the 17.01 branch
target/linux/lantiq/base-files/etc/hotplug.d/firmware/12-ath9k-eeprom | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/target/linux/lantiq/base
nux commit 7523e4dc5057e "module: use a structure to
encapsulate layout." moves some of the struct module members into a
separate struct module_layout.
Signed-off-by: Martin Blumenstingl
---
NOTE: This is compile-tested only
target/linux/generic/patches-4.9/205-backtrace_module_info.patch | 5 +++-
at 3:44 AM, Daniel Golle wrote:
> Hi Martin,
>
> On Sat, Jan 14, 2017 at 01:28:06AM +0100, Martin Blumenstingl wrote:
>> On Thu, Jan 12, 2017 at 3:35 PM, Daniel Golle wrote:
>> > Hi!
>> >
>> > The amount of patches on top of rt2x00 has grown into a huge pile
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Hauke,
(CC'ing Mathias as he w
t;
> This partly reverts this commit:
> commit 4995c64857a09c4cc92238ba0bd52cdb06c4c581
> Author: Martin Blumenstingl
> Date: Sun Dec 11 21:55:00 2016 +0100
>
> lantiq: specify console using stdout-path instead of cmdline argument
nit picking here: your patch actually fixes
6b94
at 2:01 PM, Hauke Mehrtens wrote:
>
>
> On 12/25/2016 07:12 PM, Martin Blumenstingl wrote:
>> Hi John, Hi Hauke,
>>
>> On Fri, Dec 9, 2016 at 8:08 AM, John Crispin wrote:
>>>
>>>
>>> On 09/12/2016 00:21, Hauke Mehrtens wrote:
>>>>
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi John, Hi Hauke,
On Fri, Dec 9,
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hello Magnus, Hi Felix,
On Sat, D
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On Sat, Dec 24, 2016 at 5:17 PM, a
Use devicetree's /chosen/stdout-path instead of the kernel command line
(embedded in the .dts-files) to specify the serial console. Using the
chosen node is recommended on devicetree based platforms.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/ACMP252.dts
all, while it's just copy and paste on others).
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/ACMP252.dts | 4
target/linux/lantiq/dts/ARV4510PW.dts | 4
target/linux/lantiq/dts/ARV4518PWR01.dtsi | 4
target/linux/lantiq/dts/ARV4519PW.dts | 4 ---
oved with a followup
[0]
https://www.kernel.org/doc/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
Martin Blumenstingl (2):
lantiq: specify console using stdout-path instead of cmdline argument
lantiq: remove "init" kernel command line parameter from bootargs
tar
devicetree.
This patchset was accepted upstream, more information can be found on
the linux-wireless list:
https://www.spinics.net/lists/linux-wireless/msg155474.html
Signed-off-by: Martin Blumenstingl
---
...on-dt-net-add-ath9k-wireless-device-bindi.patch | 67 +
...-helper-to-get
future upstream version which
will introduces an ieee80211 device tree property to disable bands.
Signed-off-by: Martin Blumenstingl
---
.../patches/557-ath9k-disable-bands-via-dt.patch | 32 ++
1 file changed, 32 insertions(+)
create mode 100644
package/kernel/mac80211
or data
inside an UBI volume).
Signed-off-by: Martin Blumenstingl
[add ath9k caldata mac address patcher]
[fixes DGN3500 wifi mac]
[fixes BTHOMEHUBV3A wifi mac]
[set invalid mac for BTHOMEHUB2B, FRITZ3370, FRITZ7320 & FRITZ7360SL to restore
previous random mac behavior]
Signed-off-by: Mat
inux-wireless&m=147254388611344&w=2
[3]
https://github.com/freebsd/freebsd/blob/50719b56d9ce8d7d4beb53b16e9edb2e9a4a7a18/sys/dev/ath/ath_hal/ah_eeprom_9287.c#L351
Signed-off-by: Martin Blumenstingl
---
...-define-for-the-EEPROM-eepmisc-endianness.patch | 95 +++
...ate-that-the-AR9003-E
155011.html
[2] http://www.spinics.net/lists/linux-wireless/msg155019.html
Martin Blumenstingl (6):
lantiq: Register the device tree node with the PCIe controller
lantiq: specify the PCIe controller's interrupt, size and address
cells
kernel: mac80211: backport ath9k device tree suppo
This allows adding devices to the PCIe controller in the .dts files.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/dts/vr9.dtsi b/target/linux/lantiq/dts/vr9.dtsi
This allows specifying PCI devices as children of the PCIe controller
node to pass configuration data to them.
Signed-off-by: Martin Blumenstingl
---
.../lantiq/patches-4.4/0151-lantiq-ifxmips_pcie-use-of.patch | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git
a
inux-wireless&m=147254388611344&w=2
[3]
https://github.com/freebsd/freebsd/blob/50719b56d9ce8d7d4beb53b16e9edb2e9a4a7a18/sys/dev/ath/ath_hal/ah_eeprom_9287.c#L351
Signed-off-by: Martin Blumenstingl
---
...-define-for-the-EEPROM-eepmisc-endianness.patch | 95 +++
...ate-that-the-AR9003-E
or data
inside an UBI volume).
Signed-off-by: Martin Blumenstingl
[add ath9k caldata mac address patcher]
[fixes DGN3500 wifi mac]
[fixes BTHOMEHUBV3A wifi mac]
[set invalid mac for BTHOMEHUB2B, FRITZ3370, FRITZ7320 & FRITZ7360SL to restore
previous random mac behavior]
Signed-off-by: Mat
https://www.spinics.net/lists/linux-wireless/msg155011.html
[2] http://www.spinics.net/lists/linux-wireless/msg155019.html
Martin Blumenstingl (6):
lantiq: Register the device tree node with the PCIe controller
lantiq: specify the PCIe controller's interrupt, size and address
cells
kern
This allows specifying PCI devices as children of the PCIe controller
node to pass configuration data to them.
Signed-off-by: Martin Blumenstingl
---
.../lantiq/patches-4.4/0151-lantiq-ifxmips_pcie-use-of.patch | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git
a
This allows adding devices to the PCIe controller in the .dts files.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/dts/vr9.dtsi b/target/linux/lantiq/dts/vr9.dtsi
devicetree.
This patchset was accepted upstream, more information can be found on
the linux-wireless list:
https://www.spinics.net/lists/linux-wireless/msg155474.html
Signed-off-by: Martin Blumenstingl
---
...on-dt-net-add-ath9k-wireless-device-bindi.patch | 67 +
...-helper-to-get
future upstream version which
will introduces an ieee80211 device tree property to disable bands.
Signed-off-by: Martin Blumenstingl
---
.../patches/557-ath9k-disable-bands-via-dt.patch | 32 ++
1 file changed, 32 insertions(+)
create mode 100644
package/kernel/mac80211
On Sun, Oct 30, 2016 at 11:46 AM, Antti Seppälä wrote:
> On 29 October 2016 at 00:22, Ben Mulvihill wrote:
>> On Fri, 2016-10-28 at 18:28 +0200, Christian Lamparter wrote:
>>> Hello,
>>>
>>> On Friday, October 28, 2016 4:30:56 PM CEST Ben Mulvihill wrote:
>>> > Add device tree binding for dwc2 us
On Sat, Oct 29, 2016 at 6:13 PM, Jo-Philipp Wich wrote:
> Hi Dirk,
>
> I guess it boils down to gcc 6 being unsupported yet, I would anticipate
> issues with other host builds as well.
>
> For now I suggest to downgrade to gcc 5.x
Arch Linux also uses gcc 6:
$ gcc --version
gcc (GCC) 6.2.1 2016083
On Fri, Oct 28, 2016 at 10:43 AM, Juan Rios wrote:
> anyone can help? its already working.
>
> Just need guidance about best place to put the configuration for it
> and register the callback...
maybe it would be best to place it inside the .dts?
if I had to implement it I'd see if I can adjust the
Hi Christian,
On Mon, Oct 3, 2016 at 3:34 PM, Christian Lamparter
wrote:
> On Monday, October 3, 2016 1:06:18 AM CEST Martin Blumenstingl wrote:
>> The validation of the received EEPROM data uses struct firmware's size
>> field, which contains the size in bytes. a
). The actual maximum size however is 2048 * sizeof(u16), or
in other words 4096 bytes (the kernel's FIELD_SIZEOF macro does the
same calculation, but is easier to read).
Signed-off-by: Martin Blumenstingl
---
target/linux/generic/files/drivers/misc/owl-loader.c | 5 -
1 file changed, 4 inserti
, so I cannot test
it. Thus it's compile-tested only.
Martin Blumenstingl (1):
kernel: owl-loader: fix EEPROM size validation for 4KiB EEPROMs
target/linux/generic/files/drivers/misc/owl-loader.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
--
2
On Sat, Oct 1, 2016 at 12:38 PM, Dennis Schneck wrote:
>
> Hello,
> i have a Speedport W504V | ARV8539PW22 with LEDE.
the subject says VDSL2 - that device however only has an ADSL modem
(instead of a VDSL modem) AFAIK.
On Sat, Oct 1, 2016 at 12:38 PM, Dennis Schneck wrote:
>
> Hello,
> i have a
Hi Stijn,
On Sat, Sep 24, 2016 at 2:18 PM, Stijn Segers
wrote:
> Hi Martin,
>
> I just tested your patch on LEDE r1648. I have two Unifis here. I
> inadvertently flashed one before checking its MAC addresses,
> but I did check the second one before and after. MAC before and after flash
> seems to
On Sat, Sep 24, 2016 at 12:14 AM, Dennis Schneck wrote:
> Hello Martin,
> sorry all is fine! Wireless works now!
> Thanks a lot!
great, have fun with your freed VGV7510KW22 :-)
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradea
Older busybox versions allowed using the local keyword outside of
functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not
allow this anymore (leading to the following error when executing the
script: "file: local: line nn: not in a function").
Signed-off-by: Martin Bl
On Sat, Sep 24, 2016 at 12:04 AM, Dennis Schneck wrote:
> Hi Martin,
>
> i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> 256+0 records in
> 256+0 records out
>
> whats next ?
reboot
s don't seem to be affected.
[0] http://lists.infradead.org/pipermail/lede-dev/2016-September/002921.html
Martin Blumenstingl (2):
ramips: do not "local" variables outside of a function
lantiq: do not "local" variables outside of a function
.../linux/lantiq/base-files/etc/hotplug
Older busybox versions allowed using the local keyword outside of
functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not
allow this anymore (leading to the following error when executing the
script: "file: local: line nn: not in a function").
Signed-off-by: Martin Bl
On Fri, Sep 23, 2016 at 11:28 PM, Dennis Schneck wrote:
>> ah, could you please try that again with:
>> FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> /etc/hotplug.d/firmware/10-rt2x00-
On Wed, Sep 21, 2016 at 8:26 PM, Dennis Schneck wrote:
> Hi,
> is i right that the Image:
> lede-lantiq-xrx200-VGV7510KW22BRN-squashfs-factory.bin
> is the right to Flash it on a O2 6431.
>
> Is there another way to Flash the Firmware
> without open the Device an solder PINs for Serial Console ?
On Fri, Sep 23, 2016 at 10:24 PM, Daniel Golle wrote:
> Hi again,
>
> On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote:
>>
>>
>> Sorry : mean asterisk-13.x instead of asterisk-1.8.x
>> Hi Daniel,
>> sorry about my poor english.
>>
>> Do I understand right, that it can be work with a
On Fri, Sep 23, 2016 at 9:57 PM, Dennis Schneck wrote:
>
> Hi Daniel,
> please see the attached files.
what do you get when you run:
FIRMWARE="RT3062.eeprom" /etc/hotplug.d/firmware/10-rt2x00-eeprom
Last time I used my VGV7510KW22 I was using brnboot (according to your
log your are using u-boot).
On Sun, Sep 18, 2016 at 11:29 PM, Martin Blumenstingl
wrote:
> ar71xx has an init-script for special devices where the ath10k OTP
> calibration data is stored on the PCIe card's EEPROM (and thus can only
> be read by ath10k). Unfortunately the OTP data uses the default mac
&g
re.
Signed-off-by: Martin Blumenstingl
---
.../linux/ar71xx/base-files/lib/preinit/82_patch_ath10k | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k
b/target/linux/ar71xx/base-files/lib/preinit/82_pat
al QCA.
The QCA988X directory received a small reorganization as a "hw2.0"
subdirectory was added - this patch also takes care of that as
board.bin was moved to that subdirectory.
Signed-off-by: Martin Blumenstingl
---
package/firmware/ath10k-firmware/Makefile | 18 +-
016-September/042162.html
Martin Blumenstingl (2):
ath10k-firmware: update the qca988x firmware to 10.2.4.70.54
ar71xx: Do not use a hardcoded ath10k firmware mac address
package/firmware/ath10k-firmware/Makefile | 18 +-
.../ar71xx/base-files/lib/preinit/
On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote:
>
>
> On 08/09/2016 23:58, Christian Lamparter wrote:
>> So yes, if it needs to go in a different location, that would be fine.
>> Based on your suggestion, I think the owl-loader.c code can be moved to:
>> target/linux/generic/files/drivers/net
Update the PKG_VERSION to indicate that this package now contains newer
firmware binaries (as all firmware versions were updated since 2014).
Signed-off-by: Martin Blumenstingl
---
package/firmware/ath10k-firmware/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
al QCA.
The QCA988X directory received a small reorganization as a "hw2.0"
subdirectory was added - this patch also takes care of that as
board.bin was moved to that subdirectory.
Signed-off-by: Martin Blumenstingl
---
package/firmware/ath10k-firmware/Makefile | 14 +++---
1 fil
users this
does not work out-of-the-box.
I have tested this for a few minutes, but maybe we can let this live in
Felix' tree for a few days to get test results from other people as
well.
[0] https://lists.openwrt.org/pipermail/openwrt-devel/2016-September/042162.html
Martin Blumenstingl (2
On Thu, Sep 8, 2016 at 11:58 PM, Christian Lamparter
wrote:
> Hello,
>
> On Thursday, September 8, 2016 9:34:07 AM CEST John Crispin wrote:
>> Hi,
>>
>> why is this code located under package/ and not as a kernel patch under
>> target/linux/generic ?
could you please explain why you would prefer t
uses NAND.
Additionally we have to define the IMAGE_SIZE for the AVM/EVA NOR
devices to ensure that the images are not discarded.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/image/Makefile | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/target/linux/la
On Tue, Aug 2, 2016 at 6:10 PM, Alexander Couzens wrote:
> On Tue, 2 Aug 2016 13:38:55 +
> Daniel Niasoff wrote:
>
>> I can provide remote ssh access if required. When using SSH you will
>> notice it feels sluggish due to this issue.
>>
>> Any ideas plase, I am really stuck here?
>
> I ca
From: Mathias Kresin
Signed-off-by: Mathias Kresin
Signed-off-by: Martin Blumenstingl
---
.../100-remove-cryptoapi-dependencies.patch| 90 --
.../mac80211/patches/530-ath9k_extra_leds.patch| 12 +--
...mfmac-register-wiphy-s-during-module_init.patch | 2
This folds 550-ath9k_add_ar9280_gpio_chip.patch into
548-ath9k_enable_gpio_chip.patch because the former patch only extends
code which is introduced in the latter.
Signed-off-by: Martin Blumenstingl
---
.../patches/548-ath9k_enable_gpio_chip.patch | 14 ++-
.../patches/549
This enables ath9k's built-in GPIO controller for all chip versions
(instead of an explicit whitelist). This also allows us to get rid of
some duplicate code between hw.c and gpio.c because hw.c already
determines the number of GPIOs.
Signed-off-by: Martin Blumenstingl
---
.../patche
This allows gpiolib to re-use ath9k's devicetree node as GPIO
controller.
Example:
ath9k: ath9k@0 {
#gpio-cells = <2>;
gpio-controller;
}
Now the ath9k node can be used just like any other GPIO controller:
gpios = <&ath9k 1 GPIO_ACTIVE_HIGH>;
ject.org/?p=lede/nbd/staging.git;a=commit;h=42b1e020a7ceb2992ab5597c74e8e892bf7fbc2b
Martin Blumenstingl (3):
kernel: mac80211: fold the AR9280 GPIO patch into the ath9k GPIO patch
kernel: mac80211: enable the gpio controller for all ath9k devices
kernel: mac80211: set the parent of the ath9k gpio_
This folds 550-ath9k_add_ar9280_gpio_chip.patch into
548-ath9k_enable_gpio_chip.patch because the former patch only extends
code which is introduced in the latter.
Signed-off-by: Martin Blumenstingl
---
.../patches/548-ath9k_enable_gpio_chip.patch | 14 ++-
.../patches/549
device as GPIO
controller in devicetree (once the patches for this have landed - these
are currently in discussion upstream).
As preparation for this all mac80211 patches are refreshed.
Martin Blumenstingl (3):
kernel: mac80211: fold the AR9280 GPIO patch into the ath9k GPIO patch
kernel: mac80
This allows gpiolib to re-use ath9k's devicetree node as GPIO
controller.
Example:
ath9k: ath9k@0 {
#gpio-cells = <2>;
gpio-controller;
}
Now the ath9k node can be used just like any other GPIO controller:
gpios = <&ath9k 1 GPIO_ACTIVE_HIGH>;
This enables ath9k's built-in GPIO controller for all chip versions
(instead of an explicit whitelist). This also allows us to get rid of
some duplicate code between hw.c and gpio.c because hw.c already
determines the number of GPIOs.
Signed-off-by: Martin Blumenstingl
---
.../patche
From: Mathias Kresin
Signed-off-by: Mathias Kresin
---
.../100-remove-cryptoapi-dependencies.patch| 90 --
.../mac80211/patches/530-ath9k_extra_leds.patch| 12 +--
.../patches/541-ath9k_rx_dma_stop_check.patch | 4 +-
.../patches/910-01-add-support-for-mt76
On Sat, Jun 25, 2016 at 9:26 PM, Christian Lamparter
wrote:
> The problem with the owl-loader is/was that it sticks around
> when it has initialized all the cards. Unloading a module by
> itself is tough. One way out would be to add it to ath9k's pci.c.
> The question is: will such a feature have
69 matches
Mail list logo
