On Fri, May 3, 2019 at 11:49 AM, Rosen Penev wrote:
On Fri, May 3, 2019 at 4:50 AM Petr Štetiar wrote:
Rosen Penev [2019-05-01 10:08:10]:
Hi,
> Missing header for va_list.
shouldn't this go through upstream first? Thanks.
Sent
This was applied upstream.
-- ynezz
__
On 5/5/19 6:59 AM, Stefan Lippers-Hollmann wrote:
> Hi
>
> Successfully build-tested on:
> - ath79
> - ipq806x
> - lantiq
>
> Succeffully runtime tested on:
> - ipq806x
>
> On 2019-05-04, Hauke Mehrtens wrote:
>> This also syncs the configuration files with the default configuration
>> files, bu
On 5/4/19 2:57 PM, Tomasz Maciej Nowak wrote:
> Hi,
>
> W dniu 04.05.2019 o 00:04, Hauke Mehrtens pisze:
>> On 5/1/19 7:42 PM, Tomasz Maciej Nowak wrote:
>>> Replace SoC names with vendors in device names, in few cases, and add
>>> vendor to developemnt boards for easier identyfying potential firm
Linus Walleij [2019-05-05 14:23:27]:
Hi,
I'm wondering, if it would be possible to hook (adding just a short
references, there are enough examples in the tree already) metadata into the
upgrade process instead, it would mean adding SUPPORTED_DEVICES to
image/Makefile:
define Device/Default
Tomasz Maciej Nowak [2019-05-04 16:01:11]:
> W dniu 04.05.2019 o 00:38, Petr Štetiar pisze:
> >
> > SUPPORTED_DEVICES variable is used for this, so it's probably going to work,
> > but if we're willing to rename it, it might be a good idea to follow the DT
> > compatible naming scheme as used in
Kristian Evensen [2019-05-04 12:07:33]:
Hi,
> On Fri, May 3, 2019 at 6:32 PM Petr Štetiar wrote:
> > > In order to install OpenWRT, you first need to compile an initramfs
> > > (ramdisk)-image for the device.
> >
> > if the ramdisk image is needed, then we probably should enable it for that
> >
Commit "lantiq/xrx200: enable initramfs images" enabled creation of
initramfs images for all devices in lantiq's xrx200 subtarget, just
because FRITZ7362SL needs initramfs during OpenWrt instalation.
So this commits uses selective-ramdisk feature and adds
NEEDS_INITRAMFS=1 to FRITZ7362SL only.
Si
Hi,
I've added "lantiq/xrx200: enable initramfs images" into my staging tree[1],
where this patch tries to fix shortcoming of the commit eae6cac6a3 ("lantiq:
add support for AVM FRITZ!Box 7362 SL"), as one needs an initramfs image to
flash OpenWrt from stock firmware (as described in the commit lo
Currently it's not possible to enable building of initramfs images for
the devices which need them, leading to production of initramfs images
for every device under target which has FEATURES += ramdisk.
So this patch adds a possibility to enable FEATURES += selective-ramdisk
and then the device wh
This devices have LEDs connected to the SoC's GPIOs, so it makes no
sense to fiddle with ar8327 LED regs.
Tested-by: Adrian Schmutzler
Signed-off-by: Petr Štetiar
---
target/linux/ath79/dts/qca9563_tplink_archer-x7-v5.dtsi | 4
1 file changed, 4 deletions(-)
diff --git a/target/linux/ath7
While tinkering with PR#1984, I've found out, that the ar8327 switch initvals
are not in sync with ar71xx, so this series tries to fix that.
Petr Štetiar (2):
ath79: archer-x7-v5: remove confusing ar8327 initvals for LEDs
ath79: archer-x7-v5: sync ar8327 initial reg values with ar71xx
target
I've simply dumped content of this regs in ar71xx and wrote them to DTS.
Tested-by: Adrian Schmutzler
Signed-off-by: Petr Štetiar
---
target/linux/ath79/dts/qca9563_tplink_archer-x7-v5.dtsi | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/target/linux/ath79/dts/qca9563
Rosen Penev [2019-05-05 11:27:49]:
> On Fri, May 3, 2019 at 11:00 AM Rosen Penev wrote:
> >
> > On Fri, May 3, 2019 at 10:12 AM Petr Štetiar wrote:
> > >
> > > Rosen Penev [2019-05-01 10:05:20]:
> > >
> > > Hi,
> > >
> > > > Probably glibc too. argp_help takes a char *. not const char *.
> > >
On Fri, May 3, 2019 at 11:00 AM Rosen Penev wrote:
>
> On Fri, May 3, 2019 at 10:12 AM Petr Štetiar wrote:
> >
> > Rosen Penev [2019-05-01 10:05:20]:
> >
> > Hi,
> >
> > > Probably glibc too. argp_help takes a char *. not const char *.
> >
> > I'm wondering if we need to cary another patch forev
Branch: refs/heads/master
Home: https://github.com/sdwalker/sdwalker.github.io
Commit: 0bc96348a78eda66f9a81e4b1f65f955eda8f9a7
https://github.com/sdwalker/sdwalker.github.io/commit/0bc96348a78eda66f9a81e4b1f65f955eda8f9a7
Author: Stephen Walker
Date: 2019-05-05 (Sun, 05 May 2
meaning to not mount some specific parts witch cause trouble.
The patch is based on previous work of @mikma to combine OpenWrt with
lxd[0]. This patch however adds a detection copied from *virt-what* to
check /proc/1/environment for the string "container".
Thanks to @dangowrt for the cleanup.
[0
On Sunday, May 5, 2019 10:11:40 AM CEST Klaus Kudielka wrote:
> On 04.05.19 16:51, Christian Lamparter wrote:
> > On Friday, May 3, 2019 9:38:46 PM CEST Petr Štetiar wrote:
> >> Klaus Kudielka [2019-05-03 20:16:39]:
> >>
> >>> Let me remind you that the common one *alone* breaks sysupgrade for tho
This makes sysupgrade work on the D-Link DIR-685 after
initial factory install.
We create the platform.sh script to support sysupgrade
on more targets as we move on with sysupgrade support.
Signed-off-by: Linus Walleij
---
.../gemini/base-files/lib/upgrade/platform.sh | 54 +++
From: Markus Scheck
- SoC: MediaTek MT7628AN
- Flash:16MB (Winbond W25Q128JV)
- RAM: 64MB
- Serial: As marked on PCB, 3V3 logic, baudrate is 115200
- Ethernet: 3x 10/100 Mbps (switched, 2x LAN + WAN)
- WIFI0:MT7628AN 2.4GHz 802.11b/g/n
- WIFI1:MT7612EN 5GHz 802.11ac
- Ante
Hi,
On Sun, May 5, 2019 at 12:53 PM Tom Psyborg wrote:
> > - 1x 5GHz wifi (mt7621)
>
> mt7621 is not wifi chip, you should update the description or just
> leave mt76 if you intention is to specify supporting driver.
Thanks for spotting this typo. I know very well that mt7621 is not a
wifi chip,
On 03/05/2019, Kristian Evensen wrote:
> Head Weblink HDRM200 is a dual-sim router based on MT7620A. The detailed
> specifications are:
>
> - MT7620A (580MHz)
> - 64MB RAM
> - 16MB of flash (SPI NOR)
> - 6x 10/100Mbps Ethernet (MT7620A built-in switch)
> - 1x microSD slot
> - 1x miniPCIe slot (onl
Hello again,
On Sat, May 4, 2019 at 12:07 PM Kristian Evensen
wrote:
> Also, I am having some issues getting a ramdisk image to be built by
> default. After adding ramdisk to FEATURES, I still need to manually
> choose to build a ramdisk image. I have spent some time looking into
> the different
On 04.05.19 16:51, Christian Lamparter wrote:
On Friday, May 3, 2019 9:38:46 PM CEST Petr Štetiar wrote:
Klaus Kudielka [2019-05-03 20:16:39]:
Let me remind you that the common one *alone* breaks sysupgrade for those
four targets, as Tomasz already pointed out earlier.
Well, how could I know
On Sat, May 4, 2019 at 10:30 PM Paul Spooren wrote:
>
> meaning to not mount some specific parts witch cause trouble.
>
> The patch is based on previous work of @mikma to combine OpenWrt with
> lxd[0]. This patch however adds a detection copied from *virt-what* to
> check /proc/1/environment for t
Tomasz Maciej Nowak [2019-05-04 14:39:38]:
> W dniu 03.05.2019 o 13:21, Petr Štetiar pisze:
> > Tomasz Maciej Nowak [2019-05-01 19:43:54]:
> >
> > Hi,
> >
> >> for better identification. Also create SUPPORTED_DEVICES string from it
> >> which corresponds to dts compatible string.
> >>
> >> Sig
25 matches
Mail list logo
