> *) branding
> - the owrt side sees no option of using the lede brand
>
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
>
> - as the last vote had a 100% ACK for a remerge using the owrt brand is
the
> only feasible option
Passionate: I s
I like the idea and I like the proposed logo.
And I really want a sticker applied on my openwrt router.
Therefore I supported the request on the https://www.unixstickers.com/
roadmap:
https://trello.com/c/QHSfmIQ2/560-openwrt%2Flede-hexagon-sticker
If there are enough vote they will produce the s
Dear All,
I have a problem with the pkg ddns-scripts_2.7.6-14_all.
I'm using the option service_name 'dyndns.org'.
After running the script I get in logread:
Mon Jun 5 15:27:27 2017 user.err ddns-scripts[2591]: myddns_ipv4: No or
private or invalid IP '100.67.31.70' given! Please check your conf
> 100.64.0.0/10 is shared address space under RFC6598. IETF seems to point
> to significant restrictions on its use. Customer connectivity issues are
> clear in the RFC. Chasing mobile load and avoiding rerouting global IP
> space is likely fair. Enumerating users fixed wire line end points is
> li
Dear community,
I'm trying to port openwrt/lede on the dlink dwr921 (mt7620n arch).
Currently I get a kernel panic after the OS fail to find the wmac eeprom
location.
At the moment I use in the dts something clearly wrong:
ðernet {
mtd-mac-address = <&config 0xe2ac>;
mediatek,portm
> Look for the word 0x7620 at an even offset, that's the start of the
EEPROM.
>
> > Here the complete bootlog:
> > ...
>
> You are on the right spot, the log confirms that the eeprom partition or
offset
> is certainly wrong.
Daniel, thanks for your help.
Now I'm able to complete the boot.
But I
Hi all,
I'm working to port owrt/lede on the dwr-921 (mt7620n based).
Currently I'm able to complete the boot but the wan port (port 4) doesn't
work.
All the other lan port (port 0-3) are working properly.
Yesterday with blogic we though the problem was related to the assignment of
the port-4 to
Hi,
Here an update.
I collected the switch configuration from the oem and lede systems (base
registers: 0x1011).
Here are the differences.
In case you find something suspect please ask me to double check the
registers because I get the data using some manual processing (error prone).
o
Dear All,
I'm working to port the Dlink DWR-512 in openwrt.
Currently I'm able to complete the boot and control properly a big part of
the system.
Nevertheless there is an issue with the oem bootloader.
The oem bootloader need to get the firmware in a propietary format.
If the format is not recogni
If someone is interested in testing the binboy, it can be found here:
http://tsd.dlink.com.tw/downloads2008detail.asp
download the file: DWR-512_GPL_V2.00b01_20131231_v1.tar.bz2
The "binboy" is stored in the following directory
DWR-512_GPL_V2.00b01_20131231_v1\CIG531AM_U11_GPL_03QS0.1006_2013123
Hallo,
I'm completing the support for the dlink dwr-512 adding the support for 3G.
In order to enable the 3G modem the following step need to be performed:
1) write '1' to the gpio18 (it should switch on the modem)
2) echo '2001 7d04 ff' > /sys/bus/usb-serial/drivers/option1/new_id
3) enable the f
Hi All,
In ordert o be able to flash properly lede on the DWR-512 most likly I need
to change the bootloader with u-boot (see
http://lists.infradead.org/pipermail/lede-dev/2016-October/003435.html).
Before to proceed I wold be sure that I'm able to control the target using
the jtag.
On internet I
like if the RT5350 doesn't execute the code from flash, but the
internal ROM code copy it in RAM and then execute.
My question then is:
How the ROM code can copy the image in ram if the ram is still not
initialized?
Have someone some tips?
Thanks,
Bye.
> -Ursprüngliche Nachricht--
Dear all,
Im sending to the community the following patch to support the dlink
dwr-512.
diff --git a/target/linux/ramips/base-files/etc/board.d/02_network
b/target/linux/ramips/base-files/etc/board.d/02_network
index c8b57ca..719078c 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_netw
This patch add LEDE support for the board DLINK DWR-512-B
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Álvaro Fernández Rojas
Refresh patches for all targets that support kernel 4.4.
compile/run-tested on brcm2708/bcm2710 only.
Signed-off-by: Álvaro Fernández Rojas
---
include/kernel-version.mk | 4 +--
.../ar71xx/patches-4.4/500-MIPS-fw-myloader.patch | 2 +-
I try to follow the notes of Alberto,
https://www.freedesktop.org/wiki/Software/PulseAudio/HowToUseGitSendEmail/
but clearly something has gone wrong!!!
Can someone help me to commit?
Thanks.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
ht
I add it in:
https://github.com/lede-project/source/pulls
"ramips: Add device DLINK DWR-512-B "
bye.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Dear All,
my preliminary board porting for the dwr-512 has been accepted in the
mainstream.
The dwr-512 have an embedded pcie 3G modem (see
https://wiki.openwrt.org/inbox/d-link/d-link_dwr-512_b )
Currently all the kernel module and package needed to enable the connection
are embedded in the image
Dear All,
I currently add supprt for the dwr-512 device on LEDE.
This device have a 3G modem embedded.
The current available configuration uses the usb-option to establish the 3G
connection over ppp.
Nevertheless the modem offer one cdc-ether interface with better
performance.
T: Bus=01 Lev=01 Pr
Dear Bjørn,
> Nice. The "M-MBIM" is a bit confusing, though. This doesn't seem to have
> anything to do with MBIM?
>
I'm just recompiled an image with mbim, ncm support.
But I don't know if it is the right driver.
If I send the cmd
echo '2001 7d04'> /sys/bus/usb/drivers/cdc_ncm/new_id
I
Hi Bjørn,
> No, no, the cdc_ether driver is definitely the correct one. NCM or MBIM
> won't work unless you can make the device morph into another mode. But
> since you know how to manage it in cdc_ether mode, and that is the native
> mode, I see no reason to mess with it.
You are right. The onl
Dear Bjørn, Matti,
> I don't think it is relevant for you, though. You should continue your
> initial
> idea, creating a "proto" supporting the AT managed cdc_ether based
> modem.
I add a pull request here:
https://github.com/lede-project/source/pull/585
Please help me to fix some issue and r
Dear Bjørn,
please join the discussion directly on the github code:
https://github.com/lede-project/source/pull/585
Bye.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
> --- a/package/network/utils/comgt/files/getcardinfo.gcom
> +++ b/package/network/utils/comgt/files/getcardinfo.gcom
> @@ -6,7 +6,7 @@ opengt
> flash 0.1
>
> :start
> - send "ATI^m"
> + send "AT+CGMI^m"
> diff --git a/package/network/utils/comgt/files/ncm.json
> diff --git a/package/network
> Ah, that's the echo from the command messing up things. I was using the
> cdc-wdm0 node, which doesn't echo, so I didn't notice this. Will send a
fix
> later today. However, it still wouldn't work with your modem as the
> manufacturer would be "+cgmi:". This is a bug in the modem firmware, since
Dear All,
I'd like to enable all the function available to my DWR-512.
Currently on the board is mounted the SLIC device Si3210.
This device is controlled by the spi interface.
I checked that its spi interface is connected to the spi master of the
rt5350 on the cs1.
Running the following cmd in th
I have an update.
Using the following add to the DWR-512-B.dts
&spi1 {
status = "okay";
spidev@1 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "spidev";
reg = <0>;
spi-max-frequency = <30
bind a generic spi driver?
> -Ursprüngliche Nachricht-
> Von: Giuseppe Lippolis [mailto:giu.lippo...@gmail.com]
> Gesendet: Samstag, 10. Dezember 2016 23:21
> An: lede-dev@lists.infradead.org
> Betreff: rt5350-spi rt2880-spi question
>
> I have an update.
> Using
Dear All,
I started to contribute to LEDE recently and after the spin-off.
When I decided where to port my contribution I considered the "focus on
stability and functionality" more interesting than the "bleeding edge
functionality", therefore I selected LEDE.
Now I understand that a merge is ongoin
> > When I decided where to port my contribution I considered the "focus
> > on stability and functionality" more interesting than the "bleeding
> > edge functionality", therefore I selected LEDE.
> > Now I understand that a merge is ongoing.
> > Can I ask to the people taking care about the merg
> >> we did propose this as an idea, keep lede as the bleeding edge tree
> >> and
> > use
> >> openwrt as the stable release tree with long term support. the
> >> openwrt
> > folks
> >> made it a condition for the merger that this may not be the case. i
> >> think
> > the
> >> sentence used by the
I'm trying to use spi-tools on the current LEDE snapshot, but it fails at
runtime:
root@lede:~# echo -n -e '\x80' | spi-pipe -d /dev/spidev1.0 | hexdump
SPI_IOC_MESSAGE: Invalid argument
root@lede:/tmp# strace echo -n -e '\x80' | spi-pipe -d /dev/spidev1.0 |
hexdump
execve("/bin/echo", ["echo", "
Here the report using a different command:
root@lede:/tmp# spi-pipe -d /dev/spidev1.0 -b 4 -n 40 < /dev/zero
SPI_IOC_MESSAGE: Invalid argument
root@lede:/tmp# strace spi-pipe -d /dev/spidev1.0 -b 4 -n 40 < /dev/zero
execve("/usr/bin/spi-pipe", ["spi-pipe", "-d", "/dev/spidev1.0", "-b", "4",
"-n",
Same error using the spidev_test tool:
root@lede:/tmp# spidev_test -D /dev/spidev1.0 -s 100
spi mode: 0x3
bits per word: 8
max speed: 100 Hz (1000 KHz)
can't send spi message: Invalid argument
Aborted
The error occurs on this system call:
ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tr);
Hi All,
I would like to switch on the 3g LED on the front panel of the dwr-512 when
the 3g modem connection is established.
One way (successfully tested) is to add the following section in the
/etc/conf/system:
config 'led'
option 'name' '3G'
option 'sysfs' 'dwr-51
Hi,
Im experimenting the spi interface on a RT5350 target.
Its spi driver set the interface as half duplex
master->dev.of_node = pdev->dev.of_node;
master->mode_bits = RT2880_SPI_MODE_BITS;
master->bits_per_word_mask = SPI_BPW_MASK(8);
master->min_speed_hz = clk_ge
Hi,
I would like to verify if something is connected on the second gpio bank of
my rt5350.
Therefore I enabled the bank in the dts and now I'm able to see it in /sys:
root@lede:~# ls /sys/class/gpio/
export gpio7 gpiochip0 gpiochip22
modem3g_enable unexport
root@lede:~# c
Dear All,
after some investigation on my DWR-512 board I discovered the hw
architecture of the telephone voice channel embedded in the router.
The board embeds one 3g modem plugged on the mini pcie slot and one proslic
device (si3210 - subscriber line interface circuit).
The hw architecture is show
>Dear All,
>after some investigation on my DWR-512 board I discovered the hw
architecture of the telephone voice channel embedded in the router.
>The board embeds one 3g modem plugged on the mini pcie slot and one proslic
device (si3210 - subscriber line interface circuit).
>The hw architecture is
Hi all,
I need to describe the following hw layout in the DT for the DWR-512:
+---+
|si3210 |
| |
|---+---|
| Audio |CTRL |
+---+
| PCM | SPI |---
I replace the layout without TABs
+---+
|si3210 |
| |
|---+---|
| Audio |CTRL |
+---+
| PCM | SPI |---+
+---+ |
^ ^ |
| |
> there was an idea, to do sort of anonymous datacollection by executing
> e.g. 'nslookup sysupgraded.$boardname.lede-project.org'
> after each hotplug.wan - so we can get a feeling for problems...
I like the idea. We can also have a feeling of the most popular board in
LEDE.
Bye.
___
My proposal for the anonymous datacollection is to send
1) an UDP telegram with sysupgraded.$boardname at the end of the sysupgrade
2) an UDP telegram with firstboot.$boardname at the end of the firstboot
Clearly only for the release to avoid flooding data from the developer.
Bye.
> This combines the usage of external kernel tree with the cloning of the
> kernel tree form git. The new kernel will be cloned into an external
> directory and then used from there.
I find it very useful if someone need to develop a kernel patch.
If the problem is the download time my suggestion
> > On 3 March 2017 at 16:55, Mauro Mozzarelli wrote:
> >> I have been trying to make a very simple contribution to LEDE, but it
> >> has been a frustrating process because my contribution got stuck due
> >> to form rather than substance.
I'm also thinking that the process should be in some way i
Hi all,
I'm trying to port lede to the dwr-512.
I'm using the latest trunk downloaded with
git clone https://git.lede-project.org/source.git
The dwr-512 oem bootloader accept a firmware image that shall be processed
with a dlink tool called binboy and need the binary_kernel_image (lzma
compressed
Dear Mathias,
thanks for your info.
Just a couple of question before to proceed.
1) From my understanding the append-dtb seems to append the dtb after the
kernel. But in this way in my opinion the kernel cannot point to the dbt
(remember that currently It seems that the oem bootloader cannot pass
Hi Mathias,
> > use the "KERNEL := kernel-bin | patch-dtb | lzma" config instead?
>
> Well, that is exactly the KERNEL line I've send in my last mail. Not
> sure
if I get
> what you are asking here. But such a kernel works for most of the
> rt305x devices.
In your previous email your advice w
> Von: Mathias Kresin [mailto:d...@kresin.me]
> Gesendet: Montag, 3. Oktober 2016 10:38
> > With the current change in the target/linux/ramips/image/rt305x.mk :
> > + KERNEL := kernel-bin | patch-dtb | lzma IMAGES := factory.bin
> > + IMAGE/factory.bin := \
> > + append-kernel
>
> Am I r
Dear All,
Today I reach an important milestone in " Adding support for dlink dwr-512":
BusyBox v1.25.0 () built-in shell (ash)
_
//\ ____ ___ ___
/ LE/ \| | | __| \| __|
/DE /\ | |__| _|| |) | _|
// LE \ ||___|___/|__
Hi john,
thanks for your encouragement.
> congrats, please make sure to add a proper SoB line when you submit this.
Can you please clarify me how to create and submit the patch? What means
SoB?
> also the changes to the kernel config look out of place, please remove
them
> when submitting the pat
Hi,
currently I have some problem in enabling the wifi.
During the boot I get the following messages:
rt2800_wmac 1018.wmac: failed to load eeprom property
ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data
from 'soc_wmac.eeprom'.
rt2800_wmac 1018.wmac: Direct firmwa
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
Mathias,
Thanks for the tips.
I'm going to work on it.
Bye.
> -Ursprüngliche Nachricht-
> Von: Mathias Kresin [mailto:d...@kresin.me]
> Gesendet: Sonntag, 16. Oktober 2016 09:54
> An: Giuseppe Lippolis ; lede-
> d...@lists.infradead.org
> Betreff: Re: [LEDE-DEV] A
55 matches
Mail list logo
