On Tue, Jun 07, 2016 at 02:42:36PM +0200, Zoltan HERPAI wrote:
> May I ask you to point to which e-mail are you referring to? We are
> yet to see an official line from LEDE on what they want to see to
> happen in OpenWrt.
>
i don't think you'll get anything more official than jow's mail from may
2
On Thu, May 26, 2016 at 12:38:42AM -0400, Daniel Curran-Dickinson wrote:
> I'm sorry [...]
>
no worries. :)
> despite how overly strong you come into this discussion.
>
yeah, i'm known for being not exactly the greatest diplomat. :}
___
openwrt-devel mai
glueing of the heatsinks isn't exactly
precision work. in fact, only the crystal next to the ram stopped the
sink from sliding off entirely. :D
> 2016-05-18 23:00 GMT+02:00 Oswald Buddenhagen :
> > i'll do that if you don't beat me to it (which you can easily do if you
> >
tical packages must be installed into
the jffs2 once the device has booted.
U-boot support was not attempted.
Signed-off-by: Oswald Buddenhagen
---
.../linux/lantiq/base-files/etc/board.d/02_network | 8 +
.../etc/hotplug.d/firmware/10-rt2x00-eeprom| 2 +-
target/linux/lanti
On Wed, May 18, 2016 at 01:19:59PM +0200, Mathias Kresin wrote:
> But I need to identify the boot_sel pins first. I have looked at it
> only briefly and was only able to identify one of the boot_sel pins:
> R77. Unfortunately this pin alone doesn't switch the SoC to UART mode.
> Did you found alrea
There is no such property. It was probably meant as the counterpart
to lantiq,external-clock, but the internal clock always exists anyway.
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/ARV4518PWR01.dts | 8
target/linux/lantiq/dts/GIGASX76X.dts| 1 -
2 files changed
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/FRITZ7320.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/lantiq/dts/FRITZ7320.dts
b/target/linux/lantiq/dts/FRITZ7320.dts
index 475da7a..04581c5 100644
--- a/target/linux/lantiq/dts/FRITZ7320.dts
+++ b/target
They clearly are meant to be, and the bootloader (presumably) sets them
up accordingly, but it's nicer to state it explicitly in the DT.
Entirely untested.
Signed-off-by: Oswald Buddenhagen
---
target/linux/lantiq/dts/ARV4520PW.dts| 1 +
target/linux/lantiq/dts/BTHOMEHUBV2B.dt
This property makes no sense for inputs.
Or maybe it does? the lantiq,output devicetree mapping is undocumented,
and consequently its relationship with lantiq,open-drain. So i can't
preclude the possibility that there is an unexpected relation ...
Signed-off-by: Oswald Buddenhagen
---
t
- NAND/UBI support is completely irrelevant for my box, and for
lantiq/Danube in general (IIRC). It appears to me that it would make
sense to split it off from the xway target.
- My box has no USB port and no other sensible option to connect
mass storage devices, so anything related to that m
gh for the above configuration plus
dropbear. Luci and other non-critical packages must be installed into
the jffs2 once the device has booted.
U-boot support was not attempted.
Signed-off-by: Oswald Buddenhagen
---
.../linux/lantiq/base-files/etc/board.d/02_network | 8 +
.../etc/hotplug.d/f
Mathias Kresin kresin.me> writes:
> Use the kernel with the appended dtb as base, otherwise the kernel will
> panic with "no dtb found".
>
indeed. confirmed to work now.
(and i'll freely admit that i failed to figure out how that appended image
ends up in the symbols __dtb_start/__dtb_end (the
12 matches
Mail list logo
