[LEDE-DEV] OpenWRT/LEDE IOT Starter Kit

So I've just open sourced something I've been working on at my company. This is an IOT Starter kit, a concept very popular in the web and app development world. The idea is for beginners like myself you have a repository you can use as a template for your new IOT project. It serves as a living

Re: [LEDE-DEV] [PATCH v2] merge: add OpenWrt branding

On 10/27/2017 02:34 AM, p...@oranjevos.nl wrote: > Dear Imre, > > On the info for the version of the patch: my error, must have overlooked the > included version info, it is indeed included. > > About the use of openwrt email addresses in the SOB: > This has been discussed before, and the

Re: [LEDE-DEV] Lede/Openwrt documentation

Hi, On 27-10-17, Javier Domingo Cansino wrote: > > This problem is well-known [1,2] and can be solved by having access to a > > common ancestor between the two versions. A possible way to do this would > > be to convert each wiki to a git repository [3], merge the two histories > > using git,

Re: [LEDE-DEV] Lede/Openwrt documentation

Hi Alberto, On 27-10-17, John Norton wrote: > On 27/10/2017 10:46, Baptiste Jonglez wrote: > >On 24-10-17, John Norton wrote: > >>On 24/10/2017 18:02, Javier Domingo Cansino wrote: > >>Imho (what I would do) is just migrate current LEDE wiki content in OpenWRT > >>wiki, > >>while current OpenWRT

Re: [LEDE-DEV] Lede/Openwrt documentation

> It seems that there was a bit of confusion. What you quote here is > from me, not from Javier. Also, it's from a different thread [1], in > which I indeed proposed a new system from the developer documentation > (only). > > The current thread is about how to merge the LEDE wiki and the

Re: [LEDE-DEV] Lede/Openwrt documentation

Hi Thomas, On 27-10-17, Thomas Endt wrote: > That's contrary to your statements in the start posting: > > > [...] documentation targeted at hackers, contributors, and would-be > > developers. > > [...] RFC proposal of a new developer documentation > > Links [1] [2] [3] > > [...] more focused

Re: [LEDE-DEV] Lede/Openwrt documentation

> > - We are talking about the developer pages only, or about the > complete > > content? > > Everything That's contrary to your statements in the start posting: > [...] documentation targeted at hackers, contributors, and would-be > developers. > [...] RFC proposal of a new developer

Re: [LEDE-DEV] busybox ntpd not syncing if any server is bad (update, if _first_ server is bad)

Magnus Kroken wrote: > On 21.08.2017 16:34, Karl Palsson wrote: > > on master, even with the ntpd patch for busybox applied. > > # ntpdate -q localhost > > server ::1, stratum 0, offset 0.00, delay 0.0 > > server 127.0.0.1, stratum 0, offset 0.00, delay 0.0 21 >

Re: [LEDE-DEV] Lede/Openwrt documentation

> > The wiki currently hosts and renders tables on the basis of data > > acquired and stored in a database. > > The table of packages and table of hardware. They are searchable and > > can be filtered. > > The table of hardware has a template system to let people add new > > devices to the

Re: [LEDE-DEV] Lede/Openwrt documentation

> Just to get a clear picture: > - We are talking about the LEDE wiki pages or the OpenWrt wiki pages, or > both? http://lists.infradead.org/pipermail/lede-dev/2017-October/009564.html > - We are talking about the developer pages only, or about the complete > content? Everything -- Javier

Re: [LEDE-DEV] Lede/Openwrt documentation

> If you want to use the GH editor, I'd go with markdown. For markdown, > the GH web editor has syntax highlighting and and (more important) a > usable preview mode, for RST all you get is a very simple plain text editor. I think you are right, we can do markdown for now and later change some

Re: [LEDE-DEV] Lede/Openwrt documentation

> > What exactly do you need? All wiki pages? Including history? > > Will look into this this evening. We will find an easy way. > > Someone mentioned there were private pages, but if possible, I would > create a git repo, commit all the content and upload it to github. I > can work on a proper

Re: [LEDE-DEV] Lede/Openwrt documentation

Hello everybody, here my 2 cents: > This system would work through PRs in github, and the user could link > "Edit this file in github", which would direct him to the file, and > there he would be able to click on "Fork and edit", and then submit a > pull request. From my experience, this works

Re: [LEDE-DEV] Lede/Openwrt documentation

I will suppose all the proposals are accepted when answering > I see this can be a good way forward, but I have some questions. > > I still think user-level documentation must have a decent wiki-like editor > in the browser, because github's editor > sucks big way, and isn't suited for proper

Re: [LEDE-DEV] Lede/Openwrt documentation

Am 27. Oktober 2017 15:14:19 MESZ schrieb Javier Domingo Cansino : >> And yes, I'm talking of things I can/will do personally. > >Is there any way to access all the wiki files? I am doing it manually >and its turning out to be quite tedious... =) What exactly do you need?

Re: [LEDE-DEV] Lede/Openwrt documentation

On 27/10/2017 15:14, Javier Domingo Cansino wrote: And yes, I'm talking of things I can/will do personally. Is there any way to access all the wiki files? I am doing it manually and its turning out to be quite tedious... =) afaik the only way is accessing the server itself over ssh. There

Re: [LEDE-DEV] Lede/Openwrt documentation

On 27/10/2017 13:58, Javier Domingo Cansino wrote: This problem is well-known [1,2] and can be solved by having access to a common ancestor between the two versions. A possible way to do this would be to convert each wiki to a git repository [3], merge the two histories using git, and then

Re: [LEDE-DEV] Lede/Openwrt documentation

> And yes, I'm talking of things I can/will do personally. Is there any way to access all the wiki files? I am doing it manually and its turning out to be quite tedious... =) -- Javier Domingo Cansino ___ Lede-dev mailing list

Re: [LEDE-DEV] Lede/Openwrt documentation

On 27/10/2017 10:46, Baptiste Jonglez wrote: Hi, On 24-10-17, John Norton wrote: On 24/10/2017 18:02, Javier Domingo Cansino wrote: Imho (what I would do) is just migrate current LEDE wiki content in OpenWRT wiki, while current OpenWRT stuff is either obsoleted (where it is replaced by the

Re: [LEDE-DEV] Lede/Openwrt documentation

> This problem is well-known [1,2] and can be solved by having access to a > common ancestor between the two versions. A possible way to do this would > be to convert each wiki to a git repository [3], merge the two histories > using git, and then convert back the git repository to a dokuwiki >

Re: [LEDE-DEV] [PATCH v2] merge: add OpenWrt branding

Dear Imre, On the info for the version of the patch: my error, must have overlooked the included version info, it is indeed included. About the use of openwrt email addresses in the SOB: This has been discussed before, and the arguments against using an openwrt mail address as a personal

Re: [LEDE-DEV] Lede/Openwrt documentation

Hi, On 24-10-17, John Norton wrote: > On 24/10/2017 18:02, Javier Domingo Cansino wrote: > Imho (what I would do) is just migrate current LEDE wiki content in OpenWRT > wiki, > while current OpenWRT stuff is either obsoleted (where it is replaced by the > LEDE wiki articles) or moved to suit the

Re: [LEDE-DEV] [PATCH 2/2] download.mk: introduce a new variable SKIPHASH

On 27-10-17, Yousong Zhou wrote: > On 26 October 2017 at 17:50, Baptiste Jonglez wrote: > > When calling a download target, hash verification is now completely > > skipped if the SKIPHASH variable is set. > > > > This allows to easily bump package version: > > > > #

Re: [LEDE-DEV] Transmit timeouts with mtk_eth_soc and MT7621

Hi John, On Sat, Aug 19, 2017 at 8:16 PM, John Crispin wrote: > Hi All, > > i have a staged commit on my laptop that makes all the (upstream) ethernet > fixes that i pushed to mt7623 work on mt7621. please hang on for a few more > days till i finished testing the support. this

Re: [LEDE-DEV] Serial data getting lost - bug or a feature?

Thanks Jay for very detailed answer. You reminded me about Ymodem and Zmodem that I used when I was a studetn to tranfer apps to my HP48+ calculator, but which I still own! :) We do have our own protocol that does block transfers of 30 lines at a time, and it has crc check for each line so it is

Re: [LEDE-DEV] [PATCH 2/2] download.mk: introduce a new variable SKIPHASH

On 26-10-17, Karl Palsson wrote: > Until/if your new documentation project takes off, please > consider adding this to the "how to package" doc pages. none of > these extra magical parameters are discoverable in any way right > now. Fully agreed, all this is magical enough :) While writing this