17/01/2019 05:38, Rosen Penev:
On Sun, Jan 13, 2019 at 12:28 PM Tomasz Maciej Nowak wrote:
When using Image Builder and building image for Cortex A53 or
A72 subtargets, it'll fail with following message:
Collected errors:
* opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864.
From f6c780752d5812b24a923286700a58f174d792ae Mon Sep 17 00:00:00 2001
From: Jeff Kletsky
Date: Wed, 16 Jan 2019 12:32:15 -0800
Subject: [PATCH] ath79: Add GL.iNet AR-300M-Lite: Setup with eth0 as LAN
AR300M-Lite is single-Ethernet variant of the AR300M series
Its eth0 would otherwise be
I'm somewhat apprehensive about this applying to all targets that consume GRUB2.
On x86 and x86_64 images, I believe sysupgrade lays down every
partition in the image over its equivalent already on the device.
Since the bootloader (MBR, presumably, for most x86 targets) lives in
the early part of
On Sun, Jan 13, 2019 at 12:28 PM Tomasz Maciej Nowak wrote:
>
> When using Image Builder and building image for Cortex A53 or
> A72 subtargets, it'll fail with following message:
>
> Collected errors:
> * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864.
> * opkg_install_cmd:
CPU: FSL P1020 (2x 800MHz E500 PPC)
RAM: 1GB DDR3
FLASH: 256MiB NAND
WiFi: 2x Atheros AR9382 2x2:2 abgn
ETH: 2x BCM54616S - 1x BCM53128 8-port switch
LED: 5x LEDs (Power, WiFi1, WiFi2, N/D, SYS)
BTN: 1x RESET
Installation
1. Download initrams kernel image, dtb binary and
This commit removes the target-specific diag.sh script. This way, the
generic one is used for the target, which uses DT-aliases to specify the
LEDs used.
This way, we are also able to use different LEDs to indicate different
states. We use green status LEDs for indicating boot and a running
Also update the U-Boot BSP patch for I2SE Duckbill devices.
Signed-off-by: Michael Heimpold
---
package/boot/uboot-mxs/Makefile | 4 +-
.../patches/001-add-i2se-duckbill.patch | 40 +++
2 files changed, 35 insertions(+), 9 deletions(-)
diff --git
W dniu 16.01.2019 o 02:25, Philip Prindeville pisze:
> Inline
>
>> On Jan 15, 2019, at 12:40 AM, Tomasz Maciej Nowak wrote:
>>
>> Hi Philip
>>
>> W dniu 14.01.2019 o 21:10, Philip Prindeville pisze:
>>
>>> Why is the hwclock being dropped everywhere?
>>
>> It's provided by busybox and installed
