Otherwise, a n00b like myself can get quite confused when moving a
package from core to feeds, for example.
(Hint: one *really* needs to clear out the tmp/info/.packageinfo...
entries for the stale package, but '-f' works as well.)
Signed-off-by: Brian Norris
---
scripts/feeds | 5 -
1
The following patches:
*
972-ath10k_fix-crash-due-to-wrong-handling-of-peer_bw_rxnss_override-parameter.patch
* 973-ath10k_fix-band_center_freq-handling-for-VHT160-in-recent-firmwares.patch
are replaced by this commit in the upstream kernel:
* 3db24065c2c8 ("ath10k: enable VHT160 and VHT80+80
The b43 and b43legacy driver now support DRIVER_11W_SUPPORT.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 8
package/kernel/mac80211/broadcom.mk | 4 ++--
.../kernel/mac80211/patches/ath/501-ath9k_ahb_init.patch |
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
https://www.kernel.org/doc/Documentation/devicetree/bindings/regulator/fixed-regulator.yaml
On 03.07.20 22:05, Luca Olivetti wrote:
El 3/7/20 a les 21:31, Luca Olivetti ha escrit:
I suppose it's the call to devm_regulator_get_optional, which should
lead to regulator/core.c
static struct regulator_dev *regulator_dev_lookup(struct device *dev,
El 3/7/20 a les 21:31, Luca Olivetti ha escrit:
I suppose it's the call to devm_regulator_get_optional, which should
lead to regulator/core.c
static struct regulator_dev *regulator_dev_lookup(struct device *dev,
const char *supply)
{
El 3/7/20 a les 21:10, John Crispin ha escrit:
On 03.07.20 21:07, Luca Olivetti wrote:
El 3/7/20 a les 20:07, Luca Olivetti ha escrit:
El 3/7/20 a les 20:06, John Crispin ha escrit:
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47,
On 03.07.20 21:10, John Crispin wrote:
On 03.07.20 21:07, Luca Olivetti wrote:
El 3/7/20 a les 20:07, Luca Olivetti ha escrit:
El 3/7/20 a les 20:06, John Crispin ha escrit:
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca
On 03.07.20 21:07, Luca Olivetti wrote:
El 3/7/20 a les 20:07, Luca Olivetti ha escrit:
El 3/7/20 a les 20:06, John Crispin ha escrit:
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37,
El 3/7/20 a les 20:07, Luca Olivetti ha escrit:
El 3/7/20 a les 20:06, John Crispin ha escrit:
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
https://www.kernel.org/doc/Documentation/devicetree/bindings/regulator/fixed-regulator.yaml
Oh, I see, but that's the one I had to
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 ---
Fix at least one rare wave-2
El 3/7/20 a les 20:06, John Crispin ha escrit:
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
On 03.07.20 19:57, Luca Olivetti wrote:
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
El 3/7/20 a les 19:49, John Crispin ha escrit:
On 03.07.20 19:47, Luca Olivetti wrote:
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
https://www.kernel.org/doc/Documentation/devicetree/bindings/regulator/fixed-regulator.yaml
El 3/7/20 a les 19:37, John Crispin ha escrit:
Why not use the gpio regulator ?
Because I don't know how :-(
https://www.kernel.org/doc/Documentation/devicetree/bindings/regulator/fixed-regulator.yaml
Oh, I see, but that's the one I had to *remove* because it didn't work.
Bye
--
Luca
Hi,
On 20-06-20, Baptiste Jonglez wrote:
> I should have added more details in the commit message: this fixes a
> serious regression where procd fails to start some services, for instance
> rpcd. See FS#3177.
Any feedback on this regression fix?
Thanks,
Baptiste
> This is the same regression
On 03.07.20 19:23, Luca Olivetti wrote:
El 3/7/20 a les 18:42, John Crispin ha escrit:
On 03.07.20 18:10, Luca Olivetti wrote:
Hello,
around 2 years ago, this patch
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=6eaf8b3d89571992a0aa7142cfab3f1dcef3c802#patch7
broke the
Hello,
around 2 years ago, this patch
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=6eaf8b3d89571992a0aa7142cfab3f1dcef3c802#patch7
broke the usb on my arv7518pw: when it tries to power up the usb it
returns error -537 (EPROBE_DEFER, see
Hi Puyou,
On Fri, Jul 03, 2020 at 09:51:37PM +0800, puyou...@gmail.com wrote:
> From: Puyou Lu
>
> Only tested on mt7621 currently.
>
> Signed-off-by: Puyou Lu
> ---
> target/linux/ramips/dts/AP-MT7621A-V60.dts | 13 +
This file was renamed into mt7621_mediatek_ap-mt7621a-v60.dts.
From: Puyou Lu
Only tested on mt7621 currently.
Signed-off-by: Puyou Lu
---
target/linux/ramips/dts/AP-MT7621A-V60.dts | 13 +
target/linux/ramips/dts/mt7621.dtsi| 18 +
target/linux/ramips/modules.mk | 5 +-
From: Puyou Lu
This driver works only on mt7621 currently, hope somebody can add support
for other similar chips.
Puyou Lu (1):
ramips: mt7621: add ralink pcm controller driver
target/linux/ramips/dts/AP-MT7621A-V60.dts | 13 +
target/linux/ramips/dts/mt7621.dtsi|
This can be useful when a DFS channel is configured, as the ACS channel
list is taken into account when switching channels after a radar event.
For example, this allows to prevent the SRD channels from being used in
that case.
Signed-off-by: Jan Hoffmann
---
Hello Hauke
On 7/3/20 12:54 AM, Hauke Mehrtens wrote:
> This resolves a hazard between a mtc0 and a mfc0 instruction after
> activating the DSP support. Without this fix the CPU could use the old
> value again and the DSP support would not be active.
Many thanks!
Tested-by: David Bauer
24 matches
Mail list logo
