Re: [OpenWrt-Devel] Monitoring Downlink Queue

That is a linux thing, I mean, you need to know how to do that in standard linux. Openwrt is just a normal linux system. The only difference is that you are provided with a toolchain to generate customized images. On Thu, Jan 28, 2016 at 5:10 PM Nimantha Baranasuriya wrote:

Re: [OpenWrt-Devel] API documentation of ubus

The only documentation you have from ubus is https://wiki.openwrt.org/doc/techref/ubus Apart from that, you can read procd, rpcd, uhttpd, netifd and ubus itself to see how to use it. I had plans on further documenting it but still didn't have time. You are welcome to further document it. On Sat,

[OpenWrt-Devel] [PATCH][RPCD] paths: substitute literal with macro

Signed-off-by: Javier Domingo Cansino <javier...@gmail.com> --- main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/main.c b/main.c index 3b6841b..7c161b5 100644 --- a/main.c +++ b/main.c @@ -74,8 +74,8 @@ int main(int argc, char

Re: [OpenWrt-Devel] How to start

Hi, If you are willing to implement a simple mac protocol, you could start exploring the Linux kernel code, the network part. There are several manuals and books around linux networking that could be useful. After that, you could try to compile an image for any board you are willing to use. I

Re: [OpenWrt-Devel] [PATCH libubox v2] Support broadcast sockets in usock

On Mon, Oct 26, 2015 at 2:16 PM John Crispin <blo...@openwrt.org> wrote: > Hi, > > was about to merge this but then ... see inline > > On 02/10/2015 15:53, Javier Domingo Cansino wrote: > > Signed-off-by: Javier Domingo Cansino <javier...@gmail.com> > > ---

Re: [OpenWrt-Devel] SVN to GIT transition

> > People report bugs all the time, and if I'm lucky enough to have a bug > report containing revision information, I want to maximize the > likelihood of that revision information being useful (even if there are > some local commits on top of that). > Any assumptions about users thinking

Re: [OpenWrt-Devel] SVN to GIT transition

> > One way to avoid the ambiguity of the r-number would be to use > "git describe origin/master" then even if the local master branch has > commits, you'd get the "upstream" revision number. But, I think it's > more important to know that there have been local changes. > The git-describe two

Re: [OpenWrt-Devel] SVN to GIT transition

-- Javier Domingo Cansino ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SVN to GIT transition

> > > since kernel.org was compromised. And gitlab/github > > are pretty similar. > Sure, just giving some background on where gitolite was being used and the less-known features it has. While it works fine for packages, I don't think the pull request stuff > is very usable

Re: [OpenWrt-Devel] SVN to GIT transition

> > Right now, the revision number (r) is really useful to figure > out what particular openwrt version is being used, when people report > bugs. The commit hash cannot be used as a replacement, since it might be > one that isn't present in the official repo. > When using tags as a starting point

Re: [OpenWrt-Devel] SVN to GIT transition

> > I haven't seen a single instance of somebody doing this, and in my > opinion it would be kind of stupid anyway :) > We don't even advertise the SVN server URL to users anymore for a reason. > This was a way to demonstrate that the forking point is not actually a problem SVN solves. Not having

Re: [OpenWrt-Devel] SVN to GIT transition

> > We currently don't have any tags for mainline trunk, since we usually > don't directly release from it. > I would like to know how you usually release. Can you map a commit to a release, if you can't, then we may use another simpler method. $parent-$commit$dirty That would give you info

Re: [OpenWrt-Devel] SVN to GIT transition

> > I have yet to see an approach for this that actually works and deals > with all the common scenarios where people fork OpenWrt and make a few > local changes. > I see I have not enough information on what are the common use cases. For me, these are the following: - User clones openwrt master,

Re: [OpenWrt-Devel] SVN to GIT transition

> > Would it be possible to track the revision number in an automated way even > in a git repo? So store the r number, and automatically increment on > commits. Not sure if that's an option, but it seems like it might address > the problem. > In git you wouldn't need such thing, the way would

Re: [OpenWrt-Devel] SVN to GIT transition

So the questions to be answered to provide a build version string are. - Are you planning to use git tags for something? What are you needs for it? - What information would you like to have from the build? Examples: last upstream common commit, current commit, dirtiness, officialness. Also, I

Re: [OpenWrt-Devel] [RFC] libubox/binary.h design proposal

Hello, I have been asked for examples and use cases. Github repo has been updated. I do also have doubts on if it's worth it. If a library like this existed I would be definitely using it, make conversions, does take care of alignment, can manage unaligned data and endianness. etc. But I am not

Re: [OpenWrt-Devel] [RFC] libubox/binary.h design proposal

to deal with it, I rather prefer this other design. On Mon, Oct 5, 2015 at 10:25 AM Javier Domingo Cansino <javier...@gmail.com> wrote: > Hello, > > I have been asked for examples and use cases. Github repo has been updated. > > I do also have doubts on if it's worth

[OpenWrt-Devel] [PATCH] scripts/checkpatch.pl: Fix deprecation warnings

In perl version v5.22, use of unescaped opening braces is deprecated Signed-off-by: Javier Domingo Cansino <javier...@gmail.com> --- scripts/checkpatch.pl | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index 5

[OpenWrt-Devel] [RFC] libubox/binary.h design proposal

Hello, I asked Friday on IRC how to write blobs, I was suggested using blob_raw_put from libubox/blob.h, but as I have to implement a binary protocol that uses different endianess, non aligned data etc., I think the best solution is creating a set of helper functions to write/read blobs. As this

Re: [OpenWrt-Devel] [RFC] libubox/binary.h design proposal

:38 PM Etienne Champetier < champetier.etie...@gmail.com> wrote: > Hi, > > 2015-10-04 22:47 GMT+02:00 Javier Domingo Cansino <javier...@gmail.com>: > >> Hello, >> >> I asked Friday on IRC how to write blobs, I was suggested using >> blob_raw_put

[OpenWrt-Devel] [PATCH libubox v2] Support broadcast sockets in usock

Signed-off-by: Javier Domingo Cansino <javier...@gmail.com> --- usock.c | 4 +++- usock.h | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/usock.c b/usock.c index 6748ef3..3dd9957 100644 --- a/usock.c +++ b/usock.c @@ -42,6 +42,7 @@ static void usock_set_flags(in

Re: [OpenWrt-Devel] UML not working in master

=) On Sat, Sep 26, 2015 at 11:35 PM Martin Tippmann <martin.tippm...@gmail.com> wrote: > 2015-09-26 20:48 GMT+02:00 Javier Domingo Cansino <javier...@gmail.com>: > > Hi Bastian, > > > > I have patched, compiled correctly, and working alright! =) > > > &g

Re: [OpenWrt-Devel] UML not working in master

Hi Bastian, I have patched, compiled correctly, and working alright! =) You should really send that patch upstream! On Sat, Sep 26, 2015 at 5:39 PM Bastian Bittorf <bitt...@bluebottle.com> wrote: > * Javier Domingo Cansino <javier...@gmail.com> [26.09.2015 13:26]: > >

[OpenWrt-Devel] UML not working in master

Hi, I wanted to setup for some tests an environment running uml, and I found it's not compiling on master with default config. The error seems similar to a previous one I found in the bug tracker. https://dev.openwrt.org/ticket/870 Is anyone actually maintaining UML or managed to make it work?

Re: [OpenWrt-Devel] [PATCH] [SIGNED-OFF] Add initial support for WeIO board

They will eventually do it, I suppose they where mainly focused on the release until now =) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Presentation on Linux Containers (LXC)

Thanks for sharing!! On Thu, Jun 25, 2015 at 8:31 PM Eric Schultz eschu...@prplfoundation.org wrote: I wanted to let folks know about an interesting presentation from yesterday's global OpenWrt/prpl ecosystem meeting. Luka Perkov presented on his work in adding support for Linux Containers

Re: [OpenWrt-Devel] wrong configured spam-filter for openwrt-dev

address in the FROM: field. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Javier Domingo Cansino ___ openwrt-devel

Re: [OpenWrt-Devel] OpenWrt documentation team

As far as I know, regarding documentation, there is no a specific group of people. I just edit the wiki whenever I see something is not contained and I can explain it correctly. On Tue, Apr 14, 2015 at 10:20 PM Eric Schultz eschu...@prplfoundation.org wrote: All, I'm looking to improve some

[OpenWrt-Devel] [PATCH] Simple http server to expose opkg packages and images from bin/

I have created a python script to make easily available packages under bin/ easier. I got sick of installing a web server, or move the packages, or configure it. So I just thought that a python based solution based on the scripts/ folder would be the best solution. Hope you like it! ---

[OpenWrt-Devel] [PATCH V2] scripts: python based server for opkg packages and .bin

This patch adds a small script that will expose the built packages and the images to ease opkg and sysupgrade use during development. Compatible with Python2 and Python3. --- scripts/package-server.py | 50 +++ 1 file changed, 50 insertions(+) create

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

. Regards, Roman On 22 January 2015 at 02:55, Javier Domingo Cansino javier...@gmail.com wrote: Ok, I have narrowed the problem to something with the compilation of the kernel. I think it's more an incompatibility between xilinx and linux patches, because the kernel fails to boot even

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

/zynq-zed.dts $(BIN_DIR)/zedboard.dtb endef $(eval $(call BuildImage)) === [1] Bug I should have found a lot of time ago: https://github.com/txomon/openwrt/commit/5e882bc2f14580f62a6ad78ddc57033d207261f9 ​ Cheers On Sun, Jun 29, 2014 at 1:35 PM, Javier Domingo Cansino javier...@gmail.com wrote

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

I am still stuck on this. I think that the failing point here is the kernel image load, but the loading in the part of uboot. Javier Domingo Cansino ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

​I have manually executed the boot sequence in the uboot, and the result is that it fails on the command bootm loados. Any idea on how to debug what can be wrong? Cheers and I will keep searching, Javier Domingo Cansino zynq-uboot fatload mmc 0 0x300 uImage reading uImage 4582152 bytes read

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

, ​and all those things I have been said to. May it be due to the kernel not printing to the right device? Is there any way to check that? Javier Domingo Cansino ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin

Re: [OpenWrt-Devel] Xilinx Zynq zedboard integration

- 0xc0c2c1b0 (5346 kB) Javier Domingo Cansino ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel