Re: [LEDE-DEV] [PATCH 1/4] brcm2708: convert to metadata

Applied, thanks! El 17/12/2017 a las 15:18, Christian Lamparter escribió: This patch converts all the raspberrypi images to utilize the common metadata-based image verification. Note: the CM1 and CM3 currently use the same "rpi-cm" boardname. Signed-off-by: Christian Lamparter

Re: [LEDE-DEV] Policies for changes to LEDE stable branches, or LEDE patches in general?

Hi Bjørn, El 25/04/2017 a las 13:43, Bjørn Mork escribió: > Hello, > > I note that a recent commit to the lede-17.01 branch has added a few > driver patches which have barely hit the mainline kernel: > > https://github.com/lede-project/source/commit/1ab41265c39354332630bcba0ec704abd2e790f0 > >

Re: [LEDE-DEV] [PATCH] brcm2708: backport upstream thermal driver

Maybe you should also provide a new kernel module in modules.mk for this one... Acked-by: Álvaro Fernández Rojas <nolt...@gmail.com> El 02/04/2017 a las 0:34, Rafał Miłecki escribió: > From: Rafał Miłecki <ra...@milecki.pl> > > Signed-off-by: Rafał Miłecki <ra...@mileck

Re: [LEDE-DEV] [PATCH] brcm2708: backport upstream sdhost controller driver

You only added CONFIG_MMC_BCM2835_UPSTREAM symbol for bcm2708, missing bcm2709 and bcm2710, which will break buildbot for those subtargets. Apart from that, what's the purpose of adding a disabled driver? Maybe you should create a branch in your staging repo in which this driver is enabled by

Re: [LEDE-DEV] [PATCH] brcm2708: include upstream bcm2835-rpi-zero DT binary in image

NACK, If you want to test something with the alternative device trees then you can modify a single line while doing so. Apart from that there are other alternative device trees for the other models, so why only adding the pi-zero one? I guess because that's the one you're using for testing...

Re: [LEDE-DEV] [PATCH] brcm2708: include upstream bcm2835-rpi-zero DT binary in image

Hi Rafał, Yeah, you're right, but I've been busy with other stuff and I didn't want to reply until I had tested your patches. I will reply now but I haven't been able to test them yet. Regards, Álvaro. El 14/04/2017 a las 0:27, Rafał Miłecki escribió: > Hi Alvaro, > > On 03/31/2017 10:42 PM,

Re: [LEDE-DEV] [PATCH] brcm2708: rename all patches from raspberrypi git tree to use 999 prefix

El 23/03/2017 a las 18:38, Rafał Miłecki escribió: > On 2017-03-23 18:29, Felix Fietkau wrote: >> On 2017-03-22 21:36, Rafał Miłecki wrote: >>> From: Rafał Miłecki >>> >>> Right now all brcm2708 patches are extracted from the non-mainline >>> raspberrypi/linux git tree. Many of

Re: [LEDE-DEV] Compile error on Raspberri Pi 3

Hello, That's weird because neither the buildbot nor my local setup are failing. Could you try again with a clean checkout of LEDE? Which distro are you using? Regards, Álvaro. El 23/02/2017 a las 13:35, Perry Couprie escribió: > Hi, > > Ik compiled lede for raspberri pi 2 and it compiled. >

Re: [LEDE-DEV] Backporting stuff to lede-17.01

0:53, Álvaro Fernández Rojas escribió: > Hi Rafał, > > El 02/02/2017 a las 12:32, Rafał Miłecki escribió: >> Hi, >> >> There are few changes that recently went into master and I'd like to >> see in lede-17.01. Let me what do you think, if backporting any of >>

Re: [LEDE-DEV] Backporting stuff to lede-17.01

Hi Rafał, El 02/02/2017 a las 12:32, Rafał Miłecki escribió: > Hi, > > There are few changes that recently went into master and I'd like to > see in lede-17.01. Let me what do you think, if backporting any of > these is a bad idea. > > 1) bgmac support for external PHYs > 6a853776a502 ("kernel:

Re: [LEDE-DEV] [PATCH v2] include: Cortex-A53 is also an AArch64 CPU

ACK. El 3/11/16 a las 19:16, Florian Fainelli escribió: > Specifying a mtune option with cortex-a53 is also valid for an aarch64 > toolchain > > Fixes: SVN 48964 > Signed-off-by: Florian Fainelli > --- > Changes in v2: > - add the option to the aarch64 architecture

Re: [LEDE-DEV] getver.sh regression

That one is working fine after a small fix: https://gist.github.com/Noltari/0c395c57b94598bdf96e6a292c7b5888 (You're missing one "|"). El 13/7/16 a las 11:45, Jonas Gorski escribió: > On 13 July 2016 at 11:16, Álvaro Fernández Rojas <nolt...@gmail.com> wrote: >> App

Re: [LEDE-DEV] fstools testing help

I will try to test it on RPi tonight. Regards, Álvaro. El 30/6/16 a las 9:21, John Crispin escribió: > Hi, > > i have just merged to fstools patches into my staging tree that address > a double mount issue and add back ext4 support. the ext4 patch > previously broke rPi and other ext4 targets,

[LEDE-DEV] brcm2708: take over maintainership

Hello Florian, Do you mind if I take over brcm2708's maintainership? https://git.lede-project.org/?p=source.git;a=blob;f=target/linux/brcm2708/Makefile;hb=HEAD#l14 Regards, Álvaro. ___ Lede-dev mailing list Lede-dev@lists.infradead.org

Re: [LEDE-DEV] [PATCHv3 1/1] [brcm63xx] Add initial support for EVG2000

Hello Graham, Pulled into my staging tree with some changes (whitespace fixes, cleanups...): https://git.lede-project.org/?p=lede/noltari/staging.git;a=shortlog;h=refs/heads/brcm63xx-next Regards, Álvaro. El 23/5/16 a las 0:56, Xotic750 escribió: > From: Graham Fairweather

Re: [LEDE-DEV] [PATCHv4 1/1] [brcm63xx] Fix the logged CPU variant

NACK, this doesn't add any funcionality and original firmwares show these SoCs as their generic CPU IDs (e.g: 6368 for the 6369). El 23/5/16 a las 0:46, Xotic750 escribió: From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used,