Add reference information for the ed25519 algorithm.
Add build instructions.
Signed-off-by: Heinrich Schuchardt
---
v2:
Indicate this patch is for usign
README | 18 ++
1 file changed, 18 insertions(+)
diff --git a/README b/README
index e69de29..497be08 100644
--- a/README
Add reference information for the ed25519 algorithm.
Add build instructions.
Signed-off-by: Heinrich Schuchardt
---
README | 18 ++
1 file changed, 18 insertions(+)
diff --git a/README b/README
index e69de29..497be08 100644
--- a/README
+++ b/README
@@ -0,0 +1,18 @@
+Usign provi
There is very little practical use to limit the number of available inodes on
an ext4 filesystem and the make_ext4fs utility is able to calculate useful
defaults by itself.
Keep the option but make it empty by default to allow make_ext4fs to calculate
the optimal number of inodes when generating a
Commit fe20272ab16068765a191f3a846f30f977bc7669 (SVN r40924) introduced
support for specifying ext4 blocksizes but silently switched the implicit
1K value to 4K by default without also adjusting the default partition size.
The current default size of 256MB in conjunction with 4K blocks produces an
Allow CONFIG_TARGET_EXT4_MAXINODE and CONFIG_TARGET_EXT4_RESERVED_PCT to be
empty as make_ext4fs is usually be able to figure out proper defaults.
Signed-off-by: Jo-Philipp Wich
---
include/image.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/image.mk b/includ
This is a patch series which attempts to change uci-defaults to always generate
switch configurations with tagged CPU ports, even if only one VLAN is present
on the switch.
When facing a default untagged configuration, a user has to do the following
steps in order to add an additional port based V
Instead of only using tagged CPU port configurations when more than one VLAN
is present on the switch, always emit tagged configurations unless a board
explicitely opts out of this behaviour by using the previously introduced
[0-9]u@netdev syntax.
Emitting default tagged configurations has the fol
Introduce support for a new [0-9]u@netdev syntax to ucidev_add_switch() to let
board.d network files request default network switch configurations which do
not use tagged CPU ports.
This commit itself has no effect on generated configurations at the moment
since we still emit untagged configuratio
In order to prepare support for generating tagged switch configurations by
default, explicitely request untagged configs for boards which do not already
request tagging to retain default behaviour.
Signed-off-by: Jo-Philipp Wich
---
target/linux/brcm63xx/base-files/etc/board.d/02_network | 4 ++-
Might it be possible to update the lua package in LEDE? There seems to
be an emerging problem with luasec and prosody and the current version
of lua. Luasec-0.6 requires lua-5.2 or lua-5.3, but LEDE and OpenWrt
provide only lua-5.1.
See also:
https://github.com/voidlinux/void-packages/is
Hi Karl,
let me introduce a not strictly new way but another heavily under
documented buildroot feature which you can use to implement custom
modifications to packages which do not require source code edits.
For every processed package Makefile, the buildroot tries to include a a
Makefile fragmen
Hi all,
I'm proceeding to finalize the support:
Now the wifi is enabled, the LEDs and the buttons are supported.
To complete the device support I need to:
1. enable the 3G modem
2. crack the header file to generate the factory image
Will take some time.
In the meantime, here the
Hi Sven,
pushed to iwinfo.git - thanks!
Will update it in LEDE master soon.
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Luiz Angelo Daros de Luca has submitted a patch to update libs/elflibs,
https://github.com/lede-project/source/pull/416
Current status:
tools/libtool - Move to 2.4.6
tools/lzma-old - Move to 4.32.7 (http://tukaani.org/lzma/)? Newer
versions available at link below
tools/lzma - Move to 16.03
(
When emitting .packagedeps, build separate srcpkg/variants lists for build
variants in <*> and states - this is needed to restrict opkg package
installation to only <*> variants in a later change.
Right now the package install code considers the entire variants list
which will include both <*> an
Amend the build variant declarations to let both "ip" and "ip-full" provide a
virtual "ip-command" package which other packages can depend on if they do not
care about the specific implementation of "ip".
Note that this commit does not add busybox as "ip-command" provider due to
the following reas
Instead of forcibly depending on "ip" (the tiny variant), depend on the new
virtual "ip-command" to allow users to pick their desired flavor in menuconfig
instead.
Signed-off-by: Jo-Philipp Wich
---
package/network/services/openvpn/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Various packages in the feeds and within the base repository provide multiple
build variants with slightly varying feature sets and in some cases packages
rely on functionality that can be supported by entirely different packages,
like using either openssl-util or px5g to generate an RSA certificat
Currently the code emitting dependencies for provide candidates is overwriting
the specification calculated by the previous conditional dependency handling
code, rendering dependencies on virtual PROVIDES packages in conjunction with
conditional dependencies unusable.
Instead of overwriting, appen
Previously the opkg package install code installed any package build variant
that was either set to <*> (builtin) or (package only) which leads to
file clashes with most candidates, e.g. between "ip" and "ip-full".
In order to fix those clashes, only install build variants which are
explicitely s
added the code to recognize the filesystem checkers for xfs and f2fs
added xfs and f2fs to the filesystem whitelist of block.
Signed-off-by: Alberto Bursi
-
--- fstools/block.c 2016-10-15 19:15:31.916714011 +0200
+++ fstools/block.c 2016-10-15 19:22:44.164702448 +0200
@@ -702,6 +702,
On 10/15/2016 06:30 PM, Torbjorn Jansson wrote:
> On 2016-10-15 17:39, Matthias Schiffer wrote:
>> On 10/15/2016 05:19 PM, Matthias Schiffer wrote:
>>> On 10/15/2016 05:04 PM, Torbjorn Jansson wrote:
Hello
i decided to give lede a try on one of my rasberry pi computers and i
alm
as it is, block utility of block-mount does a check for filesystem name,
and if the filesystem isn't ext or ubifs it fails.
It seems an artificial restriction as I can mount f2fs and xfs
partitions just fine with mount.
___
Lede-dev mailing list
Lede-d
On 2016-10-15 17:39, Matthias Schiffer wrote:
On 10/15/2016 05:19 PM, Matthias Schiffer wrote:
On 10/15/2016 05:04 PM, Torbjorn Jansson wrote:
Hello
i decided to give lede a try on one of my rasberry pi computers and i
almost immediately ran into problems.
opkg update works fine, but when i d
Generation of keys requires -p and -s.
The usage help should indicate this.
Signed-off-by: Heinrich Schuchardt
---
main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/main.c b/main.c
index 2203d01..3536443 100644
--- a/main.c
+++ b/main.c
@@ -333,7 +333,7 @@ static int usa
id read from unit and txoffset from datasheet
Signed-off-by: Sven Roederer
---
This patch directly applies to the git-repo of iwinfo
hardware.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/hardware.txt b/hardware.txt
index 4cac0a1..81b31cf 100644
--- a/hardware.txt
+++ b/hardware.txt
On 10/15/2016 05:19 PM, Matthias Schiffer wrote:
> On 10/15/2016 05:04 PM, Torbjorn Jansson wrote:
>> Hello
>>
>> i decided to give lede a try on one of my rasberry pi computers and i
>> almost immediately ran into problems.
>>
>> opkg update works fine, but when i do:
>> opkg install luci-ssl
>>
>
Hi,
After Holger & Alexander talk at OpenWrt Summit I started thinking
about handling feeds in LEDE. Right now we simply point to external
repositories within feeds.conf(.default):
src-git packages https://git.lede-project.org/feed/packages.git
src-git luci https://git.lede-project.org/project/luc
On 10/15/2016 05:04 PM, Torbjorn Jansson wrote:
> Hello
>
> i decided to give lede a try on one of my rasberry pi computers and i
> almost immediately ran into problems.
>
> opkg update works fine, but when i do:
> opkg install luci-ssl
>
> i get:
>
> root@lede:~# opkg install luci-ssl
> Instal
Hello
i decided to give lede a try on one of my rasberry pi computers and i
almost immediately ran into problems.
opkg update works fine, but when i do:
opkg install luci-ssl
i get:
root@lede:~# opkg install luci-ssl
Installing luci-ssl (git-16.288.36935-1e1a706-1) to root...
Downloading
ht
On 14-10-16 20:19, Chris Blake wrote:
> The following patch adds support for the PC Engines APU2 Embedded Board
> as a profile under the X86_64 target. More information on this board can
> be found at www.pcengines.ch/apu2c4.htm
>
> Note that this patch is a part of an RFC, and should not be merged
Hi,
did not see the cover letter until just now.
regarding the new image building code ... just ignore that comment,
looks like x86 was not converted yet to the new code pattern
John
On 15/10/2016 10:16, Chris Blake wrote:
> Hello Jon,
>
> My comments can be found below:
>
> On Sat, O
Hello Jon,
My comments can be found below:
On Sat, Oct 15, 2016 at 2:27 AM, John Crispin wrote:
> Hi Chris,
>
> i had quick read of the patch and it looks good at first glance. i
> would suggest you split he patch up as follows.
>
> 1) add the 2 new drivers
> 2) add the support for the new boar
Hi Chris,
i had quick read of the patch and it looks good at first glance. i
would suggest you split he patch up as follows.
1) add the 2 new drivers
2) add the support for the new board
3) the patches that add board.d, led, diag ... and all the other parts
adding the rootfs board support to x86
On 14/10/2016 18:03, Ben Greear wrote:
> On 10/14/2016 08:58 AM, Jan-Tarek Butt wrote:
>> Double quote to prevent globbing and word splitting.
>> Use short syntax to enhance reading quallity.
>
> I disagree that the short syntax helps reading quality,
> but if others like it then I guess that ch
35 matches
Mail list logo
