[LEDE-DEV] MPTCP
I'm now having a highly experimental version of MPTCP (as a package) for 15.05, (and one that builds on my old dirty trunk with the old patches-4.1 still i place) make menuconfig shows it as possible to mark with which I doubt is working as it is a kernel patch, how do I kill that? And where should it be placed in the tree? (Right now it is at KernelPackage/mptcp SUBMENU:=Network Support but that is mostly to get something to work with) signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] OpenWRT tree vs LEDE tree
Den 2016-05-20 kl. 00:09, skrev Oswald Buddenhagen: > On Thu, May 19, 2016 at 04:40:34PM +0200, Jo-Philipp Wich wrote: >> Bjørn wrote: >>> Yes, this is extremely unfair. Just like the I'm sure some >>> developers saw the original LEDE announcement. Good intentions are >>> not enough. It's the result that matters. >> I certainly agree but we should avoid applying double standards here, >> > well, that's kinda the key here, isn't it? i don't know whether the lede > infrastructure and participation was technically open from the start, > but the fact that nobody except "the cabal" knew about it makes the > whole "open" thing a bit of a cynical joke. > > the one thing that will make a big difference is plainly and openly > admitting the screwup ... and rebooting your "reboot". > > that doesn't mean starting from scratch, but instead openly and forcibly > pushing your alternatives within openwrt - as imre pointed out, you have > quite some real power. however controversial such an approach might be, > it cannot possibly do more damage to the community than this hostile > fork does. > > regarding the open decision-making process: *the* channel for any kind > of serious discussion should be the open mailing list. > - as others pointed out, irc plain does not work for such stuff. the > whole concept of meetings (or generally real-time communication about > non-trivial matters) doesn't work for many people, so just scratch it. > - alone the fact that "important stuff" happens "out of band" and needs > to be actively collected by those "passively interested" is a problem. > probably the problem that triggered bjoern's mail in the first place. > > anyway, that's my perspective as an outsider (who has 15 years of > experience in some *big* openly governed communities) ... Isn't the LEDE-adm list used for that? Just a guess, I'm not on that list... signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] MPTCP
I just built LEDE with MPTCP, but in order to get better integration I'm reading https://wiki.openwrt.org/doc/devel/patches#adding_or_editing_kernel_patches MPTCP is however associated with a bunch of lines in the kernel config, is there a way to add some defaults there som that make kernel_config is not necessary? And is there a way to make the patch only be applied if it is chosen in make menuconfig? signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] More OpenWrt -> LEDE renames
Den 2016-05-10 kl. 11:52, skrev Bruno Randolf: >> On 10/05/16 09:33, Hannu Nyman wrote: >> * branch builds after a release: Branch codename designation, last >> > release number known + changes after it, source revision, opkg download >> > from last release repo > Would automatically happen as explained above, e.g. "15.05.1-14-ge1357c0" It would be wonderful for small tinkerers like me to have opkg download from a similarily named snapshot directory as we (or at least I) tend to use or build from trunk (because of something like a new device or feature) and then 6 months later realize that I forgot tcpdump or autossh (or rather something like a kmod i.e. depending on the exact kernel, but I hope you get the picture) and of course that is not so easy to get hold of then (if I synced or used the "official" trunk build). Would of course have costs regarding disk space, so this is merely a question. signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
