From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (lang.hm [66.167.227.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9EE403B2A4 for ; Mon, 20 Feb 2017 15:21:35 -0500 (EST) Received: from dlang-laptop ([10.2.0.162]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id v1KKLL7W028682; Mon, 20 Feb 2017 12:21:21 -0800 Date: Mon, 20 Feb 2017 12:21:21 -0800 (PST) From: David Lang X-X-Sender: dlang@dlang-laptop To: Marty cc: make-wifi-fast@lists.bufferbloat.net In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20.17 (DEB 179 2016-10-28) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: [Make-wifi-fast] How to integrate LEDE into OpenWRT build env X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 20:21:35 -0000 On Mon, 20 Feb 2017, Marty wrote: > How does LEDE relate to the OpenWRT build environment? > Does it replace it? Does it just replace the kernel portion of the build > env? > > I might be asking more specific questions later, heads up, haha. LEDE is a fork of OpenWRT, most things in the build environment are virtually identical (it's been less than a year since the fork and neighter one has made a full release since), but since it is a fork, you may trip over differences. David Lang