Re: [LEDE-DEV] Supporting crashdumps w/ kexec

2017-03-08 Thread David Woodhouse
On Tue, 2017-03-07 at 17:40 -0700, Philip Prindeville wrote: > > First, obviously, is that kexec needs access to the boot partition to > reuse the kernel (since most of our architectures support relocatable > images, there’s no reason that the system kernel and the crash dump > kernel can’t be one

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 4/8] caldata-utils: new package to manipulate ath10k

2017-03-08 Thread Sven Eckelmann
On Donnerstag, 31. März 2016 19:48:20 CET Adrian Panella wrote: > >From df9a676bb3ba225f0fd6621dbaeec945baf3153d Mon Sep 17 00:00:00 2001 > From: Adrian Panella > Date: Wed, 30 Mar 2016 23:31:06 -0600 > Subject: [PATCH 12/15] caldata-utils: new package to manipulate ath10k > calibration data >

[LEDE-DEV] QCA Dakota support

2017-03-08 Thread K.Mani
I have a target board based on IPQ40xx, I want to port LEDE on it. Does LEDE has support for the following type: Model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK04.1-C2 Compatible: qcom,ipq40xx-apdk04.1qcom,ipq40xx SF: MX25L25635E Thanks Mani ___ Lede-

Re: [LEDE-DEV] [RFC] sysntpd: restore support for peer-less (standalone) mode

2017-03-08 Thread Jo-Philipp Wich
On 03/06/2017 11:20 PM, Piotr Dymacz wrote: > ntpd from Busybox supports peer-less (standalone) mode when it's started > with option -l and without any peer provided with option -p. In this > mode ntpd uses local time as reference and acts as stratum 1 server. > > This mode can be used in isolated

Re: [LEDE-DEV] [RFC] au1000: drop support

2017-03-08 Thread Bastian Bittorf
* John Crispin [26.02.2017 20:20]: > ok, send your v4.9 series when it is ready. after some trial and error: the (ram-)kernel boots without issues, but flashing is not possible, because we have only 0x2c kernel partition size, which is 44 blocks and ~2816 kilobytes. Our kernel is around 3,3mb

Re: [LEDE-DEV] QCA Dakota support

2017-03-08 Thread Matthew McClintock
Most of the support for the SoC should be in place, the various Dakota boards dk0{1,4,7}-c{1,2,3,4} are very similar. You could look at the device tree's on codeaurora.org to compare the differences from a supported platform and this variant. -M On Wed, Mar 8, 2017 at 2:47 AM, K.Mani wrote: > I

[LEDE-DEV] phy distance error (ath5k atleast)

2017-03-08 Thread Denis Periša
Hi all, I seem to have all weird problems, sorry for that. If I do `iw phy phy0 set distance 300` or anything less than 500 it seems that it's ok, hostapd runs, I have dev in the air as access point.. only.. association is denied.. it's just like rejected.. Lost whole day until I dissected this.

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

2017-03-08 Thread Philip Prindeville
> On Mar 8, 2017, at 1:12 AM, David Woodhouse wrote: > > On Tue, 2017-03-07 at 17:40 -0700, Philip Prindeville wrote: >> >> First, obviously, is that kexec needs access to the boot partition to >> reuse the kernel (since most of our architectures support relocatable >> images, there’s no reason

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

2017-03-08 Thread David Woodhouse
On Wed, 2017-03-08 at 10:20 -0700, Philip Prindeville wrote: > > Then…  grub reads the raw file system?  Well, grub has to load the kernel before the kernel is running smime.p7s Description: S/MIME cryptographic signature ___ Lede-dev mailing list

Re: [LEDE-DEV] [RFC] au1000: drop support

2017-03-08 Thread Florian Fainelli
On 03/08/2017 03:19 AM, Bastian Bittorf wrote: > * John Crispin [26.02.2017 20:20]: >> ok, send your v4.9 series when it is ready. > > after some trial and error: the (ram-)kernel boots without issues, > but flashing is not possible, because we have only 0x2c kernel > partition size, which is

[LEDE-DEV] using sata-port-specific led triggers

2017-03-08 Thread Alberto Bursi
Hi, I'm trying to use the functionality added by this patch [1] (it should generate different led triggers for each Sata port) for a few kirkwood device that have multiple Sata Leds. This patch is currently used only by some oxnas NAS devices, that seem to have not been fully ported to device t

[LEDE-DEV] NAND JFFS2 question

2017-03-08 Thread hamsi2k
Hi! I currently work to assembly a fullimage.img for the Easybox 904xdsl. Actually there are some differences to upstream made by the vendor. I take over some code and now I'm able to update the firmware, or at least the kernel via the recovery method within the uboot. As I wrote, the kernel and

Re: [LEDE-DEV] using sata-port-specific led triggers

2017-03-08 Thread Daniel Golle
Hi Alberto, On Wed, Mar 08, 2017 at 09:59:10PM +, Alberto Bursi wrote: > Hi, I'm trying to use the functionality added by this patch [1] (it > should generate different led triggers for each Sata port) for a few > kirkwood device that have multiple Sata Leds. > > This patch is currently use

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

2017-03-08 Thread Philip Prindeville
> On Mar 8, 2017, at 10:23 AM, David Woodhouse wrote: > > On Wed, 2017-03-08 at 10:20 -0700, Philip Prindeville wrote: >> >> Then… grub reads the raw file system? > > Well, grub has to load the kernel before the kernel is running…. So, what would be involved in mashing /dev/sda1 into the r

Re: [LEDE-DEV] [RFC] sysntpd: restore support for peer-less (standalone) mode

2017-03-08 Thread Philip Prindeville
> On Mar 6, 2017, at 3:20 PM, Piotr Dymacz wrote: > > ntpd from Busybox supports peer-less (standalone) mode when it's started > with option -l and without any peer provided with option -p. In this > mode ntpd uses local time as reference and acts as stratum 1 server. > > This mode can be used

Re: [LEDE-DEV] [RFC] sysntpd: restore support for peer-less (standalone) mode

2017-03-08 Thread Piotr Dymacz
Hello Philip, On 09.03.2017 00:40, Philip Prindeville wrote: On Mar 6, 2017, at 3:20 PM, Piotr Dymacz wrote: ntpd from Busybox supports peer-less (standalone) mode when it's started with option -l and without any peer provided with option -p. In this mode ntpd uses local time as reference an

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

2017-03-08 Thread Luiz Angelo Daros de Luca
1st: Is where does /boot get unmounted, and is there an easy way to keep it around a bit longer, at least until the init.d scripts have finished running? A: /boot (aka sda1) is never mounted on x86/x86_64. It could but it is simply unnecessary. grub is the only one that reads it (for loading grub c

Re: [LEDE-DEV] Support for more than a single overlay, which is selected at boot time

2017-03-08 Thread Philip Prindeville
> On Mar 7, 2017, at 6:15 AM, Jurgen Van Ham wrote: > > Hi all, > > I want to support multiple (currently just two) configurations on a > single device. One of these configurations is chosen at boot time. > Instead of saving and restoring the configuration each time, I came up > with a solution

[LEDE-DEV] Using Conflicts:

2017-03-08 Thread Philip Prindeville
Is there a reason we don’t use Conflicts: information from the packaging to stop overlapping installs from being selected when doing a build? I understand that the buildbots build everything… but it should be possible to differentiate between ’y’ and ‘m’ and detect to packages providing the sam

Re: [LEDE-DEV] using sata-port-specific led triggers

2017-03-08 Thread Mathias Kresin
08.03.2017 22:59, Alberto Bursi: Hi, I'm trying to use the functionality added by this patch [1] (it should generate different led triggers for each Sata port) for a few kirkwood device that have multiple Sata Leds. This patch is currently used only by some oxnas NAS devices, that seem to have n

Re: [LEDE-DEV] QCA Dakota support

2017-03-08 Thread John Crispin
Hi Matthew, can you point me at the tree to use on codeaurora ? i am also looking for the AP145 dts file. this is ipq8062 based John On 08/03/17 15:49, Matthew McClintock wrote: Most of the support for the SoC should be in place, the various Dakota boards dk0{1,4,7}-c{1,2,3,4} are very

Re: [LEDE-DEV] NAND JFFS2 question

2017-03-08 Thread Mathias Kresin
08.03.2017 23:01, hams...@freenet.de: Hi! I currently work to assembly a fullimage.img for the Easybox 904xdsl. Actually there are some differences to upstream made by the vendor. I take over some code and now I'm able to update the firmware, or at least the kernel via the recovery method within