Re: [LEDE-DEV] [PATCH 2/7] firmware-tools/ptgen: do not truncate the output file

2018-01-01 Thread John Crispin
On 01/01/18 17:33, Michael Heimpold wrote: Hi John, Am Montag, 1. Januar 2018, 12:12:35 CET schrieb John Crispin: On 21/12/17 23:59, Michael Heimpold wrote: At the moment, the image file operated on is always truncated to 512 bytes. This limits the usage of ptgen somewhat. O_TRUNC

Re: [LEDE-DEV] [PATCH] layerscape: activate fpu feature

2018-01-01 Thread Mathew McBride
On 2/1/18 2:58 am, Hauke Mehrtens wrote: The CPU sub type was set to a CPU version with FPU, but the FPU feature was not activated before, so a soft float toolchain was created. Activate also the FPU feature to create the correct toolchain. Signed-off-by: Hauke Mehrtens ---

Re: [LEDE-DEV] LEDE Intel Galileo Gen 2 port

2018-01-01 Thread Hauke Mehrtens
On 01/01/2018 08:04 PM, perillamint wrote: > BTW, it seems Intel Quark X1000 SoC may affected by Pentium F00F bug or > its variant (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738575) > > I wonder LEDE build system can workaround this kind of bug. It seems > appending NOP before every LOCK

Re: [LEDE-DEV] LEDE Intel Galileo Gen 2 port

2018-01-01 Thread perillamint
BTW, it seems Intel Quark X1000 SoC may affected by Pentium F00F bug or its variant (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738575) I wonder LEDE build system can workaround this kind of bug. It seems appending NOP before every LOCK instruction is required for Quark X1000 SoC

Re: [LEDE-DEV] LEDE/OpenWrt firmware wizard

2018-01-01 Thread Moritz Warning
Hi Alberto, I would parse this site https://lede-project.org/toh/views/toh_fwdownload once using node and generate the data needed. This should be no issue in JavaScript, so there is no need to have a better formatted data. Thanks, Moritz On 01/01/2018 07:35 PM, Alberto Bursi wrote: > Would

Re: [LEDE-DEV] LEDE Intel Galileo Gen 2 port

2018-01-01 Thread perillamint
Now, my current "patch" just contains some try-and-error result from make kernel_menuconfig. I'm currently organizing my journey on my blog how I successfully booted LEDE on Intel Galileo Gen 2. I estimate my "write-up" post will be done within this week however, if you want that patch right now,

Re: [LEDE-DEV] LEDE/OpenWrt firmware wizard

2018-01-01 Thread Alberto Bursi
Would providing the text files which are the actual source of the wiki pages help making this fully automated? The source text file is already structured to be parsed by the wiki PHP engine that generates the webpage. This is an example (same page as linked): = Dataentry =

Re: [LEDE-DEV] LEDE/OpenWrt firmware wizard

2018-01-01 Thread Moritz Warning
hi Hauke, somebody on the forum already pointed me there: https://forum.lede-project.org/t/firmware-wizard/9039/19 (example was also the same - coincidence? ;-)) That particular site is easy to parse, but most are not (I click random entries). Iirc, I already parsed the TOH table and added

Re: [LEDE-DEV] dnsmasq dnssec problem

2018-01-01 Thread Kevin Darbyshire-Bryant
> On 1 Jan 2018, at 15:31, e9hack wrote: > > Hi, > > dnsmasq with dnssec enabled doesn't work properly. If dnssec is enabled, the > parameter dnssec-no-timecheck is add too, > depend on some conditions related to sysntpd. If this parameter is added and > dnsmasq receives a

Re: [LEDE-DEV] [PATCH 2/7] firmware-tools/ptgen: do not truncate the output file

2018-01-01 Thread Michael Heimpold
Hi John, Am Montag, 1. Januar 2018, 12:12:35 CET schrieb John Crispin: > > On 21/12/17 23:59, Michael Heimpold wrote: > > At the moment, the image file operated on is always truncated > > to 512 bytes. This limits the usage of ptgen somewhat. > > O_TRUNC truncates to 0 and not 512 ?! when the

Re: [LEDE-DEV] [PATCH] layerscape: activate fpu feature

2018-01-01 Thread Hauke Mehrtens
Hi Yangbo Lu, Can you please test this patch on your hardware. I send a mail to yangbo...@nxp.com who is listed as the current layerscape maintainer, but it was rejected by your mail server: : host nxp-com.mail.protection.outlook.com[213.199.154.170] said: 550 5.4.1

[LEDE-DEV] [PATCH] layerscape: activate fpu feature

2018-01-01 Thread Hauke Mehrtens
The CPU sub type was set to a CPU version with FPU, but the FPU feature was not activated before, so a soft float toolchain was created. Activate also the FPU feature to create the correct toolchain. Signed-off-by: Hauke Mehrtens --- This probably fixes a problem, but I do not

[LEDE-DEV] dnsmasq dnssec problem

2018-01-01 Thread e9hack
Hi, dnsmasq with dnssec enabled doesn't work properly. If dnssec is enabled, the parameter dnssec-no-timecheck is add too, depend on some conditions related to sysntpd. If this parameter is added and dnsmasq receives a SIGHUP before ntpd was able to set the time, name resolution isn't possible,

Re: [LEDE-DEV] [PATCH] kexec-tools: fix non-device tree devices on mips

2018-01-01 Thread John Crispin
On 26/12/17 12:47, Konstantin Kuzov wrote: Add additional argument '--no-dtb' which disables device tree search in currently loaded kernel. Signed-off-by: Konstantin Kuzov Hi, could you please rework this patch such that

Re: [LEDE-DEV] [PATCH 2/7] firmware-tools/ptgen: do not truncate the output file

2018-01-01 Thread John Crispin
On 21/12/17 23:59, Michael Heimpold wrote: At the moment, the image file operated on is always truncated to 512 bytes. This limits the usage of ptgen somewhat. O_TRUNC truncates to 0 and not 512 ?!     John This change allows to use ptgen on existing, larger image files. In this case,

Re: [LEDE-DEV] LEDE Intel Galileo Gen 2 port

2018-01-01 Thread Alberto Bursi
On 01/01/2018 10:33 AM, p.wa...@gmx.at wrote: Hi perillamint, thanks for your effort on getting LEDE run on Galileo. Recently I got few Galileo Gen 2 boards from Seeed studio clearance. I tried to boot OpenWRT on them and successfully booted it with some hacks. (...) Intel discontinues

Re: [LEDE-DEV] LEDE Intel Galileo Gen 2 port

2018-01-01 Thread p . wassi
Hi perillamint, thanks for your effort on getting LEDE run on Galileo. > Recently I got few Galileo Gen 2 boards from Seeed studio clearance. I > tried to boot OpenWRT on them and successfully booted it with some hacks. > (...) > Intel discontinues Galileo and other boards. No one will be able