AW: OpenWrt 22.0X release plan
> -Ursprüngliche Nachricht- > Von: openwrt-adm Im Auftrag > von Hauke Mehrtens > Gesendet: Sonntag, 20. Februar 2022 23:58 [...] > Paul created a issue to track the remaining tasks: > https://github.com/openwrt/openwrt/issues/9248 > This will be extended with new problems. If this is an issue specifically for 22.0x, then maybe the issue title should state that. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: [PATCH] ramips: Adds support for Comfast CF-E538AC
> Is there already a device wiki page where I can see dmesg output of the > device booting OpenWrt? See https://openwrt.org/inbox/toh/comfast/comfast_cf-e538ac Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: Upcoming 19.07.4 and 18.07.9 stable releases
> Von: openwrt-devel Im > Auftrag von Thomas Endt > Gesendet: Mittwoch, 9. September 2020 17:10 > I will update the dataentries this evening. Dataentry update to 19.07.4 is running right now. Time for the long awaited announcement message! 😊 Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: Upcoming 19.07.4 and 18.07.9 stable releases
> Von: Baptiste Jonglez > Gesendet: Dienstag, 8. September 2020 22:11 > Images for 19.07.4 have been built. Thomas, could you update the ToH > accordingly? When the download page is also updated, I will announce it, > probably tomorrow. > > 18.06.9 will follow soon. I will update the dataentries this evening. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: 'tr' character class support?
> -Ursprüngliche Nachricht- > Von: openwrt-devel Im > Auftrag von Jordan Geoghegan > Gesendet: Samstag, 11. Juli 2020 06:22 > --- Config-defaults.in.orig Fri Jul 10 21:03:57 2020 > +++ Config-defaults.in Fri Jul 10 21:03:22 2020 > @@ -837,7 +837,7 @@ > default y > config BUSYBOX_DEFAULT_FEATURE_TR_CLASSES > bool > - default n > + default y > config BUSYBOX_DEFAULT_FEATURE_TR_EQUIV > bool > default n What impact on busybox package size does this have? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: 'tr' character class support?
> -Ursprüngliche Nachricht- > Von: openwrt-devel Im > Auftrag von Jordan Geoghegan > Gesendet: Samstag, 11. Juli 2020 02:16 > Is a couple kb of space worth such a loss in portability (not to mention > deviating heavily from POSIX)? If you ask the guys with 4/32 devices the answer can only be YES. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] brcm47xx: rename target to bcm47xx
> -Ursprüngliche Nachricht- > Von: openwrt-devel Im > Auftrag von m...@adrianschmutzler.de > Gesendet: Dienstag, 11. Februar 2020 01:23 > An: 'Baptiste Jonglez' ; openwrt- > de...@lists.openwrt.org > Betreff: Re: [OpenWrt-Devel] [PATCH 1/2] brcm47xx: rename target to > bcm47xx > > Hi, > > > -Original Message- > > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > > On Behalf Of Baptiste Jonglez > > Sent: Montag, 10. Februar 2020 23:22 > > To: openwrt-devel@lists.openwrt.org > > Subject: Re: [OpenWrt-Devel] [PATCH 1/2] brcm47xx: rename target to > > bcm47xx [...] > > Won't this break various things such as the wiki, the download > > servers, maybe other infrastructure? [...] > The biggest obstacle might actually be the Wiki. > > > > > For instance: https://openwrt.org/docs/techref/targets/brcm47xx > > > > All techdata URLs would need to be updated, but only for the upcoming > > release: https://openwrt.org/toh/netgear/wndr4000#installation > > I do not know how those URLs are updated, and how much manual > interference is needed there. Dataentry update normally happens manually. If the number of affected devices is too high for manual intervention, changes can be scripted. Don't worry about the wiki when changing target names. It happened in the past and is managable. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt 20.X release plans
> Von: openwrt-devel Im > Auftrag von Hauke Mehrtens > Gesendet: Sonntag, 19. Januar 2020 18:17 > This is just my proposal and I would see the dates relaxed, it also depends if > people have time to do it and so on. We can also do two weeks between the > RCs and do one more like you suggested a month ago. > > The week between the branch and the RC1 is just to setup the build bots for > the branch. > Someone has to take care of the release and this person would then > announce that he wants to tag and build the next RC some days before so > that people can prepare. The person can change in the release process. > From my point of view the delays were not caused by someone saying that > we should wait till something is fixed, but that nobody did the next step and > nothing happened. IMHO we should set up a generic timing with durations and dates behind. https://openwrt.org/docs/guide-developer/releases/release-process is already a good start, but is currently missing the RCs and the weeks behind them. $someone, a timekeeper or release-master or how you want to call him, then regularly checks the (release specific) timing if an action is due and informs the mailing list about the actions to be done. Dates can be flexible, but current timing should always be updated in the wiki accordingly. Having a timing (and someone who regularly checks it) would help to be in time with the releases. Keeping the timing updated and communicating it to the users would make the release process more transparent to them and avoid uncertainty and frustration. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Question: Migration from ar71xx to ath79
> The remaining documentation issues are the following: > > - functionalities that are present in ar71xx but missing in ath79. > If I read https://openwrt.org/docs/techref/targets/ar71xx-ath79 correctly, > missing functionalities in ath79 are supposed to go in the "Unsupported" > field of the hwdata? Yes. > How do we know if it's missing only in ath79 or in both ar71xx & ath79? The "unuspported functions" does not distinguish between targets, but since ath79 is the future, I'd say this datafield should represent ath79. > - update download links for all ar71xx/ath79 devices so that they point to > 19.07.0/ath79 images instead of 18.06.5/ar71xx. This can be done by > changing the hwdata page. Should this be done blindly, or manually > after checking that ath79 works properly on the device? I will update the dataentries via script (possibly today). If there is an ath79 image available in 19.07, download links will be changed as you have written above. If a device does not really work with 19.07.0/ath79, the dataentries should be corrected once details of the malfunction are known. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Question: Migration from ar71xx to ath79
> @Thomas: I saw that there are auto-generated pages listing ath79 devices, > it's very helpful: > > https://openwrt.org/docs/techref/targets/ath79 > https://openwrt.org/docs/techref/targets/ar71xx-ath79 > > What is the source used to generate them? Source = the dataentries of the respective devices > Where could people add > important information about upgrading for a specific device? Would it be > better on the device pages themselves, or in a column of this table? It depends. The dataentries should be used only for very short instructions (like "change imagename to xyz.bin before flashing). Everything that needs more explanation should be put on the devicepages, simply because there is much more space available. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] commit message in YAML format for new devices
> -Ursprüngliche Nachricht- > Von: openwrt-devel Im > Auftrag von Paul Spooren > Gesendet: Sonntag, 12. Januar 2020 22:47 > An: 'OpenWrt Development List' > Betreff: [OpenWrt-Devel] [RFC] commit message in YAML format for new > devices > An illustrative commit therefore: > > soc: Qualcomm IPQ4029 > ram_mb: 512 > flash: If there is manual user input, you need to validate and normalize the input data. Example: - soc: Qualcomm IPQ4029 - soc: IPQ4029 - soc: qUaLcOmMm IPQ4029 We want uniform naming and spelling. If all this is created via script, ok, no problem, the script can handle that. If you want users to deliver acceptable yaml files, you should create a "yaml-generator" where you can easily chose in dropdown lists which SoC, what RAM chip, . The current dataentries do already have dropdowns for several features, however, SoC + Wireless hardware are freetext, no dropdowns. Having that automated would be a gain. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Download link not working for 18.06.5 and 19.07.0rc1
>The OpenWrt front page has a "Download a firmware image for your device" for >each released version. However, the last two links are currently useless. Both >show no devices. >For 18.06.5, it seems that something somewhere must be updated from 18.06.4 to >18.06.5. Fixed. >For 19.07, it could be only a temporary issue while in RC. However, if so, >OpenWrt should not advertise that link for now. Fixed. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Typo: sysupgarde
FYI: There is a typo in 3 files: "upgarde" instead of "upgrade" target/linux/octeon/base-files/lib/upgrade/platform.sh 91 echo "The upgarde image is corrupt." tools/firmware-utils/src/mkdapimg.c 15 // e.g.: mkdapimg -s RT3052-AP-DAP1350-3 -i sysupgarde.bin -o factory.bin tools/firmware-utils/src/mkdapimg2.c 51 // -k 917504 -i sysupgarde.bin -o factory.bin Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches
> -Ursprüngliche Nachricht- > Von: openwrt-devel Im Auftrag > von James Feeney > Gesendet: Donnerstag, 20. Dezember 2018 20:46 [...] > There also seems to be a presumption that a "newbie" is, or should be, > running luci. I believe that that is also an inappropriate assumption. > > Using some web interface is not necessarily any easier than using a > command line interface. I see quite some users in the forum which install a snapshot (w/o LuCI). Their reaction: 1) I can not connect to the web interface! I need web interface! Please help! 2) How can I go back to stock firmware? Some users can perfectly live without LuCI, some others can't. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx Vs ath79 -- sysupgrade
> -Ursprüngliche Nachricht- > Von: Henrique de Moraes Holschuh > Em 05/12/2018 21:20, Thomas Endt escreveu: > >> Auftrag von Henrique de Moraes Holschuh Do we have a wiki table > >> somewhere that has the device name, ar71xx info and ath79 info, which > >> could be expanded with ar71xx->ath79 status (no, yes but unverified, > >> yes verified to be complete)? > >> > >> That would be really useful to direct efforts on adding ath79 support > >> to something that is still ar71xx-only, as well as adding > >> ar71xx->ath79 support to targets of interest (i.e. those one happens > >> to know what changes are required for the migration, really). > >> > >> I suppose one would also add any remarks about ath79 support being > >> incomplete or any regressions for each target one knows about, too. > >> That would help steering the ar71xx deprecation. > > > > There is a table that documents the ath79 status in the OpenWrt forum: > > https://forum.openwrt.org/t/ath79-target-status/18614/9 > > > > The place to put this into the wiki would be: > > https://openwrt.org/docs/techref/targets/ath79 > > > > > > We can define a new target "ar71xx-ath79" for the dataentries, which > would then give us these 3 options: > > > > 1) "ar71xx" # device is ar71xx only > > 2) "ath79" # device is ath79 only > > 3) "ar71xx-ath79"# device is migrated (and working, if nothing in > "Unsupported Functions") > > > > ---> devices will automatically show up on the ath79 and/or ar71xx wikipage > (slight modifications necessary). > > > > For "ath79 WIP" devices, we can set the "Unsupported Functions" datafield > (that's where WIP usually is found) to "ath79 WIP, see forum". > > Any detailed discussion or description of incomplete support should > happen elsewhere, i.e. either in the forum or on the respective devicepages. > > > > Please let me know if this meets your requirements. > > Yes, this would do it nicely, provided that we take care to describe in the > web > pages what ar71xx-ath79 means. > > Note that my answer assumes "migrated" (i.e. ar71xx-ath79) means the glue > to migrate and convert low-level config (LEDs, etc) when updating from > ar71xx -> ath79 is in place on the ath79 port. > > If it just does ar71xx _and_ ath79, BUT one has to manually adjust > configuration when migrating from ar71xx to ath79, it would have to be > flagged as WIP or something like that, even if all of its functions are fully > implemented and working in ath79. I tried to include your comments while creating these two pages: https://openwrt.org/docs/techref/targets/ar71xx-ath79 https://openwrt.org/unsupported/ath79_wip Please crosscheck. > > There is a table that documents the ath79 status in the OpenWrt forum: > > https://forum.openwrt.org/t/ath79-target-status/18614/9 Can I set all devices listed as "working" to "ar71xx-ath79 + no ath79 WIP"? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx Vs ath79 -- sysupgrade
> -Ursprüngliche Nachricht- > Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im > Auftrag von Henrique de Moraes Holschuh > Gesendet: Mittwoch, 5. Dezember 2018 11:03 [...] > Do we have a wiki table somewhere that has the device name, ar71xx info > and ath79 info, which could be expanded with ar71xx->ath79 status (no, > yes but unverified, yes verified to be complete)? > > That would be really useful to direct efforts on adding ath79 support > to something that is still ar71xx-only, as well as adding ar71xx->ath79 > support to targets of interest (i.e. those one happens to know what > changes are required for the migration, really). > > I suppose one would also add any remarks about ath79 support being > incomplete or any regressions for each target one knows about, too. > That would help steering the ar71xx deprecation. There is a table that documents the ath79 status in the OpenWrt forum: https://forum.openwrt.org/t/ath79-target-status/18614/9 The place to put this into the wiki would be: https://openwrt.org/docs/techref/targets/ath79 We can define a new target "ar71xx-ath79" for the dataentries, which would then give us these 3 options: 1) "ar71xx" # device is ar71xx only 2) "ath79" # device is ath79 only 3) "ar71xx-ath79"# device is migrated (and working, if nothing in "Unsupported Functions") ---> devices will automatically show up on the ath79 and/or ar71xx wikipage (slight modifications necessary). For "ath79 WIP" devices, we can set the "Unsupported Functions" datafield (that's where WIP usually is found) to "ath79 WIP, see forum". Any detailed discussion or description of incomplete support should happen elsewhere, i.e. either in the forum or on the respective devicepages. Please let me know if this meets your requirements. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Read-only copy of Wiki?
Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im Auftrag von Nguy?n H?ng Quân Gesendet: Sonntag, 29. Juli 2018 04:30 An: OpenWrt Development List Betreff: [OpenWrt-Devel] Read-only copy of Wiki? >Hi > >The OpenWrt wiki is sometimes too slow to access from my country. Which wiki are you talking about: 1) wiki.openwrt.org (that's the old wiki) 2) openwrt.org (that's the new wiki) > So I would like to host a read-only copy of it, to serve as reference > documentation. >Is this possible? Can you help export the wiki? There are several ways to get the wiki content without any wiki admin action. Have you tried e.g. an offline-reader plugin for your browser already? Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page
> -Ursprüngliche Nachricht- > Von: Vincenzo Romano [mailto:vincenzo.rom...@notorand.it] > Gesendet: Montag, 29. Januar 2018 15:34 > > I think that the merge should be finalized as soon as possible. > > As of now: > > 1. openwrt.org home page is still the old one with just the merge > announcement 2. Development link goes to dev.openwrt.org which gives an > error with no way out (at least with chrome) 3. Documentation link goes > to wiki.openwrt.org/doc/start 4. Downloads link goe to > downloads.openwrt.org which neither looks like Openwrt nor Lede. > 5. Wiki link goes to wiki.openwrt.org > 6. Forum goes to forum.openwrt.org > 7. Trademark policy goes to openwrt.org/trademark.php 8. The "download" > link on the right panel gives a 404 error. > 9. The "Headlines" are still outdatedly pointing to OpenWRT 15.05.1. > > Everything else is more or less the same old OpenWRT stuff. > It looks like the amount of work to be done is huge. > I can volunteer for anything the administrators want. Hey Vincenzo, we're currently discussing how to get things started quickly, please see https://forum.lede-project.org/t/lede-openwrt-wiki-merge/10861/8 Helping hands are welcome! Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page
Hi John, First results on a private demowiki, see: https://lede-project.org/_media/wiki/ledewiki-owrtstyling.jpg 1) red marking: What are we going to do with the sidebar (raw, untouched styling; could be beautified)? Keep or remove? 2) blue marking: I remember there was some discussion about a new, fresh logo. I think now with the move to the LEDE codebase is the right time to refresh the wiki a bit too. Does anybody remember where that discussion happened and what the outcome was? 3) I changed my mind regarding hard cut. The OpenWrt wiki is still rw, and we should keep it that way until we have a plan on how to accomplish the actual merge of the wikis. Thomas > -Ursprüngliche Nachricht- > Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im > Auftrag von Thomas Endt > Gesendet: Samstag, 6. Januar 2018 18:06 > An: 'John Crispin'; 'LEDE Development List'; 'LEDE Project > Administration'; 'OpenWrt Development List' > Betreff: Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page > > Hi John, > > Since the styling is based on CSS, we would need the OpenWrt wiki's CSS > for that. Once we have that, it will be relatively easy. > But instead of doing the merge of the wikis step by step, I would > suggest a hard cut. > > 1.) Make OpenWrt wiki read only -> I can do that or Imre > 2.) Create .tgz of OpenWrt wiki and hand it over to LEDE wiki admins -> > Imre > 3.) Move LEDE wiki to OpenWrt styling (apply OpenWrt theme and CSS to > LEDE > wiki) -> I can do that. Some help of CSS experienced guys could be > necessary for hard cases. > 4.) Move content of old OpenWrt wiki to new OpenWrt wiki (former LEDE) > -> I can take the toh part (devicepages); dataentries will be taken > from LEDE since they are way more up to date and contain more > datafields. > -> Rest of the wiki: A plan needs to be worked out what will be > carried over from old to new OpenWrt wiki -> Community discussion > > I'm in the starting blocks since weeks, waiting only for the GO and the > OpenWrt wiki sources, and I'm sure, we will have some helping heands > ready to start the wiki merge. > > Thomas > > > -Ursprüngliche Nachricht- > > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im > Auftrag > > von John Crispin > > Gesendet: Freitag, 5. Januar 2018 18:54 > > An: LEDE Development List; LEDE Project Administration; OpenWrt > > Development List > > Betreff: [LEDE-DEV] owrt landing page > > > > Hi, > > > > could someone please help us with rebranding the lede landing page to > > an openwrt colour/theme ? i would like to see this swithced over > > within the next 7 days. > > > > John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page
Hi John, Since the styling is based on CSS, we would need the OpenWrt wiki's CSS for that. Once we have that, it will be relatively easy. But instead of doing the merge of the wikis step by step, I would suggest a hard cut. 1.) Make OpenWrt wiki read only -> I can do that or Imre 2.) Create .tgz of OpenWrt wiki and hand it over to LEDE wiki admins -> Imre 3.) Move LEDE wiki to OpenWrt styling (apply OpenWrt theme and CSS to LEDE wiki) -> I can do that. Some help of CSS experienced guys could be necessary for hard cases. 4.) Move content of old OpenWrt wiki to new OpenWrt wiki (former LEDE) -> I can take the toh part (devicepages); dataentries will be taken from LEDE since they are way more up to date and contain more datafields. -> Rest of the wiki: A plan needs to be worked out what will be carried over from old to new OpenWrt wiki -> Community discussion I'm in the starting blocks since weeks, waiting only for the GO and the OpenWrt wiki sources, and I'm sure, we will have some helping heands ready to start the wiki merge. Thomas > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von John Crispin > Gesendet: Freitag, 5. Januar 2018 18:54 > An: LEDE Development List; LEDE Project Administration; OpenWrt > Development List > Betreff: [LEDE-DEV] owrt landing page > > Hi, > > could someone please help us with rebranding the lede landing page to > an openwrt colour/theme ? i would like to see this swithced over within > the next 7 days. > > John > > > ___ > Lede-dev mailing list > lede-...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be merged into Chaos Calmer
disregard that, I didn’t notice that you already had references that.
Von: Thomas Endt [mailto:tm...@gmx.de]
Gesendet: Dienstag, 28. November 2017 21:35
An: 'Ronaldo Afonso'; 'Zoltan HERPAI'
Cc: 'OpenWrt Development List'
Betreff: AW: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be
merged into Chaos Calmer
This might be of interest:
https://git.lede-project.org/?p=source.git;a=commit;h=0b45bec22c59cc6e6b2fa71dc9a88386c5587132
Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im Auftrag
von Ronaldo Afonso
Gesendet: Dienstag, 28. November 2017 20:25
An: Zoltan HERPAI
Cc: OpenWrt Development List
Betreff: Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be
merged into Chaos Calmer
Hi Zoltan,
First of all, thanks for you replay.
Following is what I have tried to to:
1) I tried doing a simple "git merge d42ccc9f28aca96bdd7c83cfac43ae81d24bc5a2"
... but that resulted in a LOT of errors.
2) So, I decided to look more closely at the commit and manually ported what
had being done. Following is the git status and git diff on the CC branch ...
ronaldo@fox:~/Linux/OpenWrt/src/openwrt$ git status
On branch chaos_calmer
Your branch is up-to-date with 'origin/chaos_calmer'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: target/linux/ar71xx/base-files/etc/diag.sh
modified: target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
modified: target/linux/ar71xx/base-files/etc/uci-defaults/02_network
modified: target/linux/ar71xx/base-files/lib/ar71xx.sh
modified: target/linux/ar71xx/base-files/lib/upgrade/platform.sh
modified: target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c
modified: target/linux/ar71xx/image/Makefile
modified:
target/linux/ar71xx/patches-3.18/610-MIPS-ath79-openwrt-machines.patch
no changes added to commit (use "git add" and/or "git commit -a")
ronaldo@fox:~/Linux/OpenWrt/src/openwrt$ git diff
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 623e2a43b5..85f1e3eab6 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -280,6 +280,7 @@ get_status_led() {
tl-wr841n-v11 | \
tl-wa830re-v2 | \
tl-wr842n-v2 | \
+tl-wr841n-v3 | \
tl-wr941nd | \
tl-wr941nd-v5)
status_led="tp-link:green:system"
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index 91f5875c2f..03f01c4050 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -519,6 +519,16 @@ tl-wr842n-v2)
ucidef_set_led_usbdev "usb" "USB" "tp-link:green:3g" "1-1"
;;
+tl-wr842n-v3)
+ ucidef_set_led_netdev "wan" "WAN" "tp-link:green:wan" "eth1"
+ ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0"
"0x10"
+ ucidef_set_led_switch "lan2" "LAN2" "tp-link:green:lan2" "switch0"
"0x08"
+ ucidef_set_led_switch "lan3" "LAN3" "tp-link:green:lan3" "switch0"
"0x04"
+ ucidef_set_led_switch "lan4" "LAN4" "tp-link:green:lan4" "switch0"
"0x02"
+ ucidef_set_led_wlan "wlan" "WLAN" "tp-link:green:wlan" "phy0tpt"
+ ucidef_set_led_usbdev "usb" "USB" "tp-link:green:3g" "1-1"
+ ;;
+
tl-wa801nd-v2 | \
tl-wa901nd-v3)
ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0"
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index 032c671341..0558c0f33d 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -439,6 +439,7 @@ tl-wr741nd |\
tl-wr741nd-v4 |\
tl-wr841n-v7 |\
tl-wr841n-v9 |\
+tl-wr842n-v3 |\
tl-wr841n-v11 |\
whr-g301n |\
whr-hp-g300n |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 1eb608..904ff4b10f 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -821,6 +821,9 @@ ar71xx_board_detect() {
*"TL-WR842N/ND v2")
name="tl-wr842n-v2"
;;
+ *&qu
Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be merged into Chaos Calmer
This might be of interest:
https://git.lede-project.org/?p=source.git;a=commit;h=0b45bec22c59cc6e6b2fa71dc9a88386c5587132
Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im Auftrag
von Ronaldo Afonso
Gesendet: Dienstag, 28. November 2017 20:25
An: Zoltan HERPAI
Cc: OpenWrt Development List
Betreff: Re: [OpenWrt-Devel] How can I help TL-WR842N Hardware version 3 be
merged into Chaos Calmer
Hi Zoltan,
First of all, thanks for you replay.
Following is what I have tried to to:
1) I tried doing a simple "git merge d42ccc9f28aca96bdd7c83cfac43ae81d24bc5a2"
... but that resulted in a LOT of errors.
2) So, I decided to look more closely at the commit and manually ported what
had being done. Following is the git status and git diff on the CC branch ...
ronaldo@fox:~/Linux/OpenWrt/src/openwrt$ git status
On branch chaos_calmer
Your branch is up-to-date with 'origin/chaos_calmer'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: target/linux/ar71xx/base-files/etc/diag.sh
modified: target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
modified: target/linux/ar71xx/base-files/etc/uci-defaults/02_network
modified: target/linux/ar71xx/base-files/lib/ar71xx.sh
modified: target/linux/ar71xx/base-files/lib/upgrade/platform.sh
modified: target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c
modified: target/linux/ar71xx/image/Makefile
modified:
target/linux/ar71xx/patches-3.18/610-MIPS-ath79-openwrt-machines.patch
no changes added to commit (use "git add" and/or "git commit -a")
ronaldo@fox:~/Linux/OpenWrt/src/openwrt$ git diff
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 623e2a43b5..85f1e3eab6 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -280,6 +280,7 @@ get_status_led() {
tl-wr841n-v11 | \
tl-wa830re-v2 | \
tl-wr842n-v2 | \
+tl-wr841n-v3 | \
tl-wr941nd | \
tl-wr941nd-v5)
status_led="tp-link:green:system"
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index 91f5875c2f..03f01c4050 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -519,6 +519,16 @@ tl-wr842n-v2)
ucidef_set_led_usbdev "usb" "USB" "tp-link:green:3g" "1-1"
;;
+tl-wr842n-v3)
+ ucidef_set_led_netdev "wan" "WAN" "tp-link:green:wan" "eth1"
+ ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0"
"0x10"
+ ucidef_set_led_switch "lan2" "LAN2" "tp-link:green:lan2" "switch0"
"0x08"
+ ucidef_set_led_switch "lan3" "LAN3" "tp-link:green:lan3" "switch0"
"0x04"
+ ucidef_set_led_switch "lan4" "LAN4" "tp-link:green:lan4" "switch0"
"0x02"
+ ucidef_set_led_wlan "wlan" "WLAN" "tp-link:green:wlan" "phy0tpt"
+ ucidef_set_led_usbdev "usb" "USB" "tp-link:green:3g" "1-1"
+ ;;
+
tl-wa801nd-v2 | \
tl-wa901nd-v3)
ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0"
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index 032c671341..0558c0f33d 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -439,6 +439,7 @@ tl-wr741nd |\
tl-wr741nd-v4 |\
tl-wr841n-v7 |\
tl-wr841n-v9 |\
+tl-wr842n-v3 |\
tl-wr841n-v11 |\
whr-g301n |\
whr-hp-g300n |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 1eb608..904ff4b10f 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -821,6 +821,9 @@ ar71xx_board_detect() {
*"TL-WR842N/ND v2")
name="tl-wr842n-v2"
;;
+ *"TL-WR842N/ND v3")
+ name="tl-wr842n-v3"
+ ;;
*TL-WR941ND)
name="tl-wr941nd"
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index fda7bc417c..bf1e0d295e 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -361,6 +361,7 @@ platform_check_image() {
tl-wr841n-v9 | \
tl-wr841n-v11 | \
tl-wr842n-v2 | \
+tl-wr842n-v3 | \
tl-wr941nd | \
tl-wr941nd-v5 | \
tl-wr941nd-v6 | \
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c
index 004f719613..f33ca2c906 100644
--- a/target/linux/ar71xx/files/arc
Re: [OpenWrt-Devel] [LEDE-DEV] LEDE call for vote on remerge proposal V3
> Transferring the openwrt.org domain to the SPI is seen as a > prerequisite before the next steps will be taken by the LEDE > developers. > > @Imre: I assume this needs multiple steps, could you please update us > on the status of transferring the openwrt.org domain to the SPI please. Almost two weeks later: What is the status of the domain transfer to the SPI? Is there an estimated timeline available for when the domain transfer will be done and the next steps can start? Please forgive me my impatience, but I'm already thinking of the merge of the two wikis, now that the voting has been done. Regards, Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal
> -Ursprüngliche Nachricht- > Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im > Auftrag von Imre Kaloz > Gesendet: Mittwoch, 10. Mai 2017 11:36 > > On 2017-05-09 18:29, Philip Prindeville wrote: > > > > > I’d like to suggest one more action item to this list if I can. It > would be handy to have a single database for user > authentication/identification for submitting bugs, editing the Wiki, > etc. > > > > Previously there were too many places where you had to create an > account. If we can’t do “single sign-on”, can we at least do “single > sign-up”? > > > > And part of a user’s profile should include their IRC handle > (assuming they have one). > > I agree, SSO would be way more user friendly. We should look into it > for sure. The LEDE wiki and LEDE forum currently offer login via github. Others are possible, e.g. Auth0, Google, Doorkeeper, Keycloak, ... Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] was the move to github complete/1:1?
> But more (most) importantly, that feed, even though it was being built > for BB and available to opkg, is not being built for CC, right? "The next release after barrier breaker will not include any unmaintained binary packages at all not even as opt-in." https://forum.openwrt.org/viewtopic.php?id=52219 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Create Technicolor brand in the new data entry page
Done! > -Ursprüngliche Nachricht- > Von: Linus Walleij [mailto:linus.wall...@linaro.org] > Gesendet: Dienstag, 31. Mai 2016 23:30 > An: openwrt-devel@lists.openwrt.org; tm...@gmx.de > Betreff: Re: Create Technicolor brand in the new data entry page > > Looping in tmo26, as mentioned at the page. Mea culpa. > > Yours, > Linus Walleij > > > On Tue, May 31, 2016 at 11:28 PM, Linus Walleij > wrote: > > Hi, > > > > I was trying to add a Technicolor router to the wiki here: > > https://wiki.openwrt.org/meta/create_new_dataentry_page > > > > But Technicolor does not exist in the Brand list. A previous entry > > uses Thomson but that is their old name. > > > > Can someone here add Technicolor to the brand list? > > > > Yours, > > Linus Walleij ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
