On 2018-03-01 03:48, Yousong Zhou wrote:
> On 28 February 2018 at 18:58, Felix Fietkau wrote:
>> On 2018-02-28 11:48, Yousong Zhou wrote:
>>> On 28 February 2018 at 16:13, Felix Fietkau wrote:
On 2018-02-28 06:07, Yousong Zhou wrote:
> This is intended to reduce build time for situations
On Wed, Feb 28, 2018 at 9:21 AM, Felix Fietkau wrote:
> In OpenWrt, we don't keep full kernel configurations in our target
> config-* files. We have a generic config template, and the target config
> file is supposed to contain only changes to the generic config template.
> Merging and splitting
On Wed, Feb 28, 2018 at 2:58 PM, Hauke Mehrtens wrote:
> On 02/27/2018 10:45 PM, Linus Walleij wrote:
>> On Tue, Feb 27, 2018 at 4:46 PM, Hauke Mehrtens wrote:
>>> And the also "make target/linux/{clean,refresh} V=99" to make the
>>> patches cleanly apply.
>>
>> I tested this and it looks clean.
Hi list!
I'm new by building packages on OpenWRT, but I try to create a package
(I know how it works on Debian).
My package depends on BASH, so I wrote:
define Package/blah
SECTION:=admin
CATEGORY:=Administration
DEPENDS:=$(CXX_DEPENDS) +libpq +libopenssl +libopenldap +bash
TITLE:=Bla
If you really need dependency on bash package, it is in packages repository.
Did you try "./scripts/feeds update && ./scripts/feeds install bash" ?
--
S pozdravom Jakub Janco
On Thu, Mar 1, 2018 at 1:57 PM, Luca Bertoncello wrote:
> Hi list!
>
> I'm new by building packages on OpenWRT, but I t
Zitat von Jakub Jančo :
If you really need dependency on bash package, it is in packages repository.
Did you try "./scripts/feeds update && ./scripts/feeds install bash" ?
Hi Jakub,
It works!
Thanks a lot, that was the right tip!
Regards
Luca Bertoncello
(lucab...@lucabert.de)
___
Bump the 4.4 kernel for the 17.01 release to 4.4.119. Refresh patches.
Compile-tested: ar71xx, ramips/mt7621, x86/64
Run-tested: ar71xx, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +--
.../patches-4.4/910-unaligned_access_hacks.patch | 2 +-
Split the oem firmware upgrade images into seperate files.
Useful when analysing oem firmware files.
Signed-off-by: Alexander Couzens
---
tools/firmware-utils/src/tplink-safeloader.c | 280 +--
1 file changed, 263 insertions(+), 17 deletions(-)
diff --git a/tools/firmwar
Those converted factory images can be used to regain the original
tp-link firmware.
Be aware of firmware upgrade which additional require changes of
other partition than os-image (kernel) & file-system (rootfs).
OEM factory images from tplink can change nearly all partitions.
However using those im
Specification:
- SoC: Atheros AR9342
- Flash: 8 MiB
- RAM: 64 MiB
- UART: 1x UART on PCB - 115200 8N1
- Ethernet: 1 x 100 Mbit with passive PoE (24V/0.2A)
Doesn't work:
* Flash via TFTP with Uiquiti Uboot
Installation via vendor firmware:
- upload factory image via webinterface
Signed-off-by: Ar
This bumps the 4.4. kernel in master to 4.4.119.
Includes more Meltdown & Spectre mitigation.
* Refresh patches.
* Refresh x86/config for RETPOLINE.
* Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
(accepted upstream)
* Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.pa
11 matches
Mail list logo
