On 17 August 2016 at 12:28, Jonas Gorski wrote:
> On 16 August 2016 at 16:47, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> On all devices suppored so far BCM53125 got port 8 connected to the SoC
>> interface and ports 0-4 to physical ports. On BCM53573 there is slightly
>> more comlex setup
i would guess a regression inside the atm subsystem of he kernel or some
other part of the network stack. assuming that this issue is only
observed inside the atm part, i'll start looking there.
John
On 18/08/2016 06:22, Daniel Niasoff wrote:
> Hi Mathias,
>
>
> Looks like it's this com
Commit 83175687c81bee594885d0738cfd488673f5a3fb "build: remove image
specific checksum code" dropped the generation of md5 checksums in
favour of only shipping sha256 ones.
A default Lede installation however doesn't enable busybox' sha256sum
applet, which makes confirming the checksum on the devi
Hi
On 2016-08-18, Karl Palsson wrote:
> Why not just add sha256 sum rather than going back to md5?
[...]
Generating md5sums in addition to sha256sums files only affects build
time slightly, but doesn't increase the firmware size itself. Given
that apparently nothing currently requires a sha256su
Why not just add sha256 sum rather than going back to md5?
Cheers,
Karl P
Stefan Lippers-Hollmann wrote:
> Commit 83175687c81bee594885d0738cfd488673f5a3fb "build: remove
> image specific checksum code" dropped the generation of md5
> checksums in favour of only shipping sha256 ones.
>
> A defa
Hello Josua, pat,
I haven't tested this yet. Thanks for your effort.
Are you sure this is the root cause? Everything works well in the past
without this config being enabled.
If you say yes, please send a PR or send a patch to mailing list.
Best Regards,
Syrone Wong
On Thu, Aug 18, 2016 at
Commit 83175687c81bee594885d0738cfd488673f5a3fb "build: remove image
specific checksum code" dropped the generation of md5 checksums in
favour of only shipping sha256 ones.
A default Lede installation however doesn't enable busybox' sha256sum
applet, which makes confirming the checksum on the devi
Sorry for bothering you.
After "make clean" it seems allright.
On 2016-08-17 22:21, Jochen Demmer wrote:
Hi,
I'm on 7264df388616d2fa21d4cb97336e7e2afe3759ad and when I try to
build with this diffconfig:
CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_DEVICE_a
Hi,
I'm on 7264df388616d2fa21d4cb97336e7e2afe3759ad and when I try to build
with this diffconfig:
CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_DEVICE_archer-c7-v2=y
# CONFIG_PACKAGE_ath10k-firmware-qca988x is not set
# CONFIG_PACKAGE_kmod-ath10k is not set
On Sun, Aug 14, 2016 at 1:20 AM, Daniel Dickinson
wrote:
> Hi,
>
> Just wondering if I missed any questions or comments about the odhcpd
> per-host leasetime patch I sent some time ago? I don't recall seeing
> anything and I wasn't following the list all that closely for a while
> for personal re
Hello Josua,
To my great satisfaction, your suggestion works beautifully !!
Thank you very much for taking time to pass this suggestion along.
Pat
> On Aug 17, 2016, at 9:08 AM, Josua Mayer wrote:
>
> Hi Syrone, Pat,
>
> I ran into the same issue on the Clearfog Pro, and my colleague figur
Hi Syrone, Pat,
I ran into the same issue on the Clearfog Pro, and my colleague figured
out a way to make it disappear.
Please try out this patch and let me know if it helps on your boards:
https://github.com/Artox/lede-project/commit/db724f8ff1ed4c77668f691ed4d066a8e0f2693e
From db724f8ff1ed4c77
Hi Daniel,
On Tue, 2016-08-16 at 17:12 +0200, Daniel Golle wrote:
> Hi Alexey,
>
> On Tue, Aug 16, 2016 at 06:06:20AM +, Alexey Brodkin wrote:
> >
> > Hi Felix,
> >
> > On Wed, 2016-07-27 at 17:19 +0200, Felix Fietkau wrote:
> > >
> > > On 2016-07-27 14:11, Alexey Brodkin wrote:
> > > >
>
Hi John,
On Wed, 2016-08-17 at 16:51 +0200, John Crispin wrote:
>
> On 17/08/2016 16:49, Alexey Brodkin wrote:
> >
> > Hi John,
> >
> > On Wed, 2016-08-17 at 09:20 +0200, John Crispin wrote:
> > >
> > >
> > > On 16/08/2016 12:43, Alexey Brodkin wrote:
> > > >
> > > >
> > > > For some reason
On 17/08/2016 16:49, Alexey Brodkin wrote:
> Hi John,
>
> On Wed, 2016-08-17 at 09:20 +0200, John Crispin wrote:
>>
>> On 16/08/2016 12:43, Alexey Brodkin wrote:
>>>
>>> For some reason CMake's buildsystem searches for openssl libs
>>> on Linux either in /usr/libX, /usr/local/libX or in OPENSSL_
Hi John,
On Wed, 2016-08-17 at 09:20 +0200, John Crispin wrote:
>
> On 16/08/2016 12:43, Alexey Brodkin wrote:
> >
> > For some reason CMake's buildsystem searches for openssl libs
> > on Linux either in /usr/libX, /usr/local/libX or in OPENSSL_ROOT_DIR
> > ignoring standard LD_LIBRARY_PATH env
Hi,
due to a server update the git server is gone for about 1 hour.
sorry for the inconvenience.
John
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
On 16 August 2016 at 16:47, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> On all devices suppored so far BCM53125 got port 8 connected to the SoC
> interface and ports 0-4 to physical ports. On BCM53573 there is slightly
> more comlex setup. We have 2 SoC interfaces: one (eth0) connected to
On 16/08/2016 12:43, Alexey Brodkin wrote:
> For some reason CMake's buildsystem searches for openssl libs
> on Linux either in /usr/libX, /usr/local/libX or in OPENSSL_ROOT_DIR
> ignoring standard LD_LIBRARY_PATH env var.
>
> This behavior breaks CMAke building if openssl libs are in some
> spe
19 matches
Mail list logo
