On 13/06/2018 22:08, Philip Prindeville wrote:
Hi all,
Does anyone have a baseline KVM machine description (i.e. an domain.xml file)
for testing x86_64 images?
I’ve spotted a bug in Busybox that requires some debugging to root-cause it,
but I don’t want to do this on an actual production
Hi all,
Does anyone have a baseline KVM machine description (i.e. an domain.xml file)
for testing x86_64 images?
I’ve spotted a bug in Busybox that requires some debugging to root-cause it,
but I don’t want to do this on an actual production router for obvious reasons
and I’m a little short
The original work is about a year old now, I think.
What do we still need to make it into master?
Also, how did the target/host Makefile issue for sfdisk end up being resolved?
Thanks,
-Philip
> On Mar 14, 2018, at 12:18 PM, Jo-Philipp Wich wrote:
>
> Merged into my staging tree at
>
13.06.2018 10:51, Zoltan HERPAI:
Certain Netgear devices use BE squashfs for the kernel image. As
squashfs4 only supports creating LE images, add squashfs (v3) into
the tools to be built for ath79.
Trying to use an LE squashfs (thus trying to use squashfs4 only for
building the image) for the
The D-Link DIR-685 has a RealTek RT2880 mini-PCI card in a
slot. Activate the appropriate kernel module.
The Square One SQ201 has a Ralink RT61-based mini-PCI card.
Activate the appropriate kernel modules. This fixes the
previous error just activating the firmware: the kernel
module will bring in
This makes the Gemini build a WRGG-type firmware update
image for the DIR-685. This should hopefully install the
kernel from the web firmware upgrade API on the product
switching it permanently to use OpenWRT.
Signed-off-by: Linus Walleij
---
target/linux/gemini/image/Makefile | 12 ++--
While support for the FLOWOFFLOAD target is available in the firmware
images, it is still missing in some of the binary packages on
downloads.openwrt.org, e.g. for the mipsel_mips32 architecture.
Increment PKG_RELEASE to force an update of these packages.
Also adjust the package description to
Signed-off-by: Zoltan HERPAI
---
target/linux/ath79/image/common-netgear.mk | 22 ++
target/linux/ath79/image/generic.mk| 24 +---
2 files changed, 23 insertions(+), 23 deletions(-)
create mode 100644 target/linux/ath79/image/common-netgear.mk
Netgear WNR612 v2:
- cpu Atheros AR7240 (Python) @400MHz
- flash 4MB
- ram 32MB
- ethernet 10/100: 1xwan + 2xlan (only two)
- radio AR9285
As there is a rebranded WNR612v2 called ON Networks N150R, add
a dtsi which includes all device support, and add a separate dts
for the board only
Signed-off-by: Zoltan HERPAI
---
target/linux/ath79/base-files/etc/board.d/01_leds | 3 ++-
target/linux/ath79/base-files/etc/board.d/02_network| 3 ++-
.../base-files/etc/hotplug.d/firmware/10-ath9k-eeprom | 1 +
target/linux/ath79/dts/ar7240_on_n150r.dts | 10
Certain Netgear devices use BE squashfs for the kernel image. As
squashfs4 only supports creating LE images, add squashfs (v3) into
the tools to be built for ath79.
Trying to use an LE squashfs (thus trying to use squashfs4 only for
building the image) for the kernel image results in the
On 13/06/2018 09:00, Russell Senior wrote:
Hans Dedecker writes:
Hi, On Sun, Jun 10, 2018 at 11:54 PM Russell Senior
wrote:
Signed-off-by: Russell Senior ---
I get the following compile issues if the rdma utility is enabled :
I wonder if rdma is actually useful in openwrt. As far as
> Hans Dedecker writes:
> Hi, On Sun, Jun 10, 2018 at 11:54 PM Russell Senior
> wrote:
>>
>>
>> Signed-off-by: Russell Senior ---
> I get the following compile issues if the rdma utility is enabled :
I wonder if rdma is actually useful in openwrt. As far as I can tell
it's related to
13 matches
Mail list logo
