On Fri, May 12, 2017 at 5:29 PM, Mathias Kresin wrote:
> 12.05.2017 03:37, kyson lok:
>>
>> On Fri, May 12, 2017 at 6:18 AM, L. D. Pinney wrote:
>>>>
>>>> +&spi0 {
>>>> + status = "okay";
>>>> +
>>>>
Hi Kyson :
v2 looks much better ...
Not a LEDE dev...comments inline.
Thanks for your contribution efforts!
Larry
On Thu, May 11, 2017 at 3:48 AM, kysonlok wrote:
> This patch adds supports for the GL-inet GL-MT300N-V2.
>
> Specification:
> - SoC: MediaTek MT7628AN
> - Flash: 16 MiB (W25Q128FV
the review easier.
>
> Find some comments inline.
>
> 07.05.2017 03:41, L. D. Pinney:
>
>> The VoCore2 Lite uses the same PCB as the Vocore2 with a MT7688A and 8M
>> Flash/64M RAM
>>
>> https://www.indiegogo.com/projects/vocore2-4-coin-sized-linux-computer-with-
firmware one may need to edit the same files or use
the bootloader.
Signed-off-by: L. D. Pinney
Tested-by: Noble Pepper
---
target/linux/ramips/base-files/etc/board.d/01_leds | 5 -
target/linux/ramips/base-files/etc/board.d/02_network | 3 ++-
target/linux/ramips/base-files/etc
On Thu, Feb 16, 2017 at 5:27 AM, Felix Fietkau wrote:
> On 2017-02-16 12:21, L. D. Pinney wrote:
>> Without the updated Makefile I have this error :
>>
>> make[3]: Entering directory '/data/LEDE-17.01/package/kernel/mt76'
>> . /data/LEDE-17.01/include/shell.
Thu, Feb 16, 2017 at 5:11 AM, Felix Fietkau wrote:
> On 2017-02-16 12:04, L. D. Pinney wrote:
>> Update mt76 Makefile to latest github revision.
>>
>> Signed-off-by: L. D. Pinney
> NACK. 17.01 doesn't have the necessary changes to ramips .dts files, and
> I see no
Update mt76 Makefile to latest github revision.
Signed-off-by: L. D. Pinney
---
package/kernel/mt76/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/kernel/mt76/Makefile b/package/kernel/mt76/Makefile
index 5e7761093c..658a3191b1 100644
--- a/package
This patch resets the spi to 3 byte mode needed for devices with more than 16M
Flash.
Tested on the Onion Omega2+ (MT7688)
Signed-off-by: L. D. Pinney
Tested-by: Nita Vesa
---
diff --git a/target/linux/ramips/patches-4.4/101-spi-reset-to-3-byte-mode.patch
b/target/linux/ramips/patches-4.4
This patch updates the MIWIFI-NANO.dts using dt-bindings, sets the MAC from
eeprom, and sets the LEDs
Signed-off-by: L. D. Pinney
---
target/linux/ramips/base-files/etc/board.d/01_leds | 6 +++---
target/linux/ramips/dts/MIWIFI-NANO.dts| 34
++
2
This patch defines the reset button in the MIWIFI-NANO.dts
Signed-off-by: L. D. Pinney
---
diff --git a/target/linux/ramips/dts/MIWIFI-NANO.dts
b/target/linux/ramips/dts/MIWIFI-NANO.dts
index 6906ef3..9b1ca42 100644
--- a/target/linux/ramips/dts/MIWIFI-NANO.dts
+++ b/target/linux/ramips/dts
Fix the mtd partition layout and enable both radios in the dts
Signed-off-by: L. D. Pinney
Tested-by Andrius ??tikonas
---
diff --git a/target/linux/ramips/dts/WNDR3700V5.dts
b/target/linux/ramips/dts/WNDR3700V5.dts
index b9ca613..bb879a1 100644
--- a/target/linux/ramips/dts/WNDR3700V5.dts
Add Support for the ESMT_F25L32QA and ESMT_F25L64QA
These are 4MB and 8MB Flash Chips from Elite Semiconductor Memory Technology
Signed-off-by: L. D. Pinney
---
target/linux/generic/patches-4.4/477-mtd-spi-nor-add-support-ESMT_f25l32qa_and_f25l64qa
| 14 ++
1 file changed, 14
The NixCore X1 is a Ralink/MediaTek rt5350 WiFi Module.
http://nixcores.com/
Signed-off-by: L. D. Pinney
Acked-by: Drew Gaylo
---
V2 uses a combined .dtsi
target/linux/ramips/base-files/etc/board.d/02_network | 1 +
target/linux/ramips/base-files/lib/ramips.sh | 3 ++
target
The NixCore X1 is a Ralink/MediaTek rt5350 WiFi Module.
http://nixcores.com/
Signed-off-by: L. D. Pinney
Acked-by: Drew Gaylo
---
target/linux/ramips/base-files/etc/board.d/02_network | 1 +
target/linux/ramips/base-files/lib/ramips.sh | 3 +++
target/linux/ramips/base-files/lib
While I think adding luci will be convenient for many users.
I feel that the initial release is the paramount issue and that builds
containing luci could be added later.
A nice solution would be to offer downloads built w/wo lucias well
as adding 'luci' to the filename if built with luci.
On
>From the OP
I wanted to ask folks whether they want me to continue to cross post to these
On Thu, Jun 16, 2016 at 2:49 AM, John Crispin wrote:
>
>
> On 16/06/2016 09:18, L. D. Pinney wrote:
>> OP wants to know if it's OK to cross post about old subjects.
>
> no he
OP wants to know if it's OK to cross post about old subjects.
Particularly TR-069 already available as packages for LEDE.
Notably freecwmp and easycwmp
NAK... use reasonable mailing list etiquette.
On Thu, Jun 16, 2016 at 2:17 AM, L. D. Pinney wrote:
> OP wants to know if it'
ed, Jun 15, 2016 at 6:05 PM, David Lang wrote:
> On Wed, 15 Jun 2016, L. D. Pinney wrote:
>
>> It's a Development List ... no place for corporate agendas.
>
>
> if adding a feature is a corporate agenda because a company is interested in
> it working correctly, y
ce software development is done by people who benefit from the results.
> If benefiting from the results makes it that the LEDE project doesn't want
> to hear from you, the project will die _really_ fast.
>
> I hope your hostile attitude doesn't spread.
>
> David Lang
>
port remote management protocols?
>
> Just because a company works on something doesn't make it evil.
>
> David Lang
>
> On Wed, 15 Jun 2016, L. D. Pinney wrote:
>
>> Date: Wed, 15 Jun 2016 16:29:08 -0500
>> From: L. D. Pinney
>> To: LEDE Development List
>
Postings to the LEDE Development List should be devoted to technical
development issues.
Persons from prplfoundation et.al should respect conventional mail list
etiquette such as found here :
http://www.arm.linux.org.uk/mailinglists/etiquette.php
Pay particular attention to 4, 7, and 10 on the a
Yet another example of cross-posted DRIVEL
On Tue, Jun 14, 2016 at 3:54 PM, Richard Smith wrote:
> On 05/20/2016 05:16 PM, Dave Taht wrote:
>>
>> We had found some pretty major performance problems on this hardware
>> as of a few months ago. I am curious if they still exist? A whole
>> bunch of b
Much like the convention of prefixing your subject line with [PATCH]
messages like this should be required to have a prefix such as
[DRIVEL] for effective filtering
lede integration issues ??
I don't see why there IS an issue CeroWrt died for good reason(s) ... such as :
Low return on investment
This patch sets the busybox prompt to the default.
It also provides options to colorizes (or not) the command line prompt.
Also optional time display.
Signed-off-by: L. D. Pinney
---
diff --git a/package/base-files/files/etc/profile
b/package/base-files/files/etc/profile
index ad8fe12
This patch provides a new banner for LEDE
Signed-off-by: L. D. Pinney
---
diff --git a/package/base-files/files/etc/banner
b/package/base-files/files/etc/banner
index ae2f16f..7b19941 100644
--- a/package/base-files/files/etc/banner
+++ b/package/base-files/files/etc/banner
@@ -1,10 +1,11
Isn't the 'default' busybox prompt just a #
Although the 'default' prompt on OpenWrt is 'monocolor'
My point here is that the 'default' prompt should be '#'
Not that of the 'OpenWrt team'.
The 'ls' command has been 'colorized' for quite some time.
Personally I find it quite useful...and less
26 matches
Mail list logo
