Probably most common - no open source wireless drivers.

@tmo26, This is not the right master?
http://wiki.openwrt.org/toh/dataentry_template

Where do I find the updates you want?

Yes... except that is not supposed to make a device "unsupported"... (well, there are different opinions about it).

But I like the idea: can we have a multi choice / dropdown with "reasons for being unsupported / unsupported features"... perhaps "Unsupported aspects" or just "Unsupported". I can imagine a list like:

* Platform/target not supported by OpenWrt
* Insufficent hardware (too little RAM/Flash)
* WiFi (not working)
* WiFi (5GHz not working)
* WiFi (AC not working)
* Switch not supported (TP Link Archer C2)
* Installation issues (serial required)
* Hardware NAT not working (never is)
* USB not working
* Unknown
* Devs need hardware and time

What is missing? Can we make them shorter yet clear?

In principle, I think it is fine that the Supported Current Release is empty for non-supported devices, but it would be very nice with a "Unsupported" columns for details.

Hehehe... in the tohs, mainly supported + wip.
http://wiki.openwrt.org/toh/start
http://wiki.openwrt.org/toh/wip

We once had a column "Support" or "Status".
Now we're coming up with a column "Unsupported"? Just wondering ;-)

Do we really need this information in the dataentries and as a separate field, or would it be sufficient to show this info on the devicepage (if there is any for an unsupported device)?

Fair point. And the unsupported column is a great idea. It would really help new folks zero in on a device that does actually work for their needs.

Personally, wifi is core functionality in a router today. I would only consider a device supported if it  works as expected (both bands if dual band, AC if supported, etc.). I suppose MIMO and beam forming are a gray area. Devices that don't have wifi get a pass here. I would also say a similar thing about devices with a DSL modem or other special features that would be considered core functionality of that device.

Take a look at: http://wiki.openwrt.org/toh/t-com/spw504v
Very nice table within the device details page that clearly shows what does and does not work.

Current Status of the template_dataentry (see demowiki):

- I took out some comments, since for pure dropdown fields, we do not always need some explanation.
Especially the valid values for dropdowns should not be placed in the comments: If the valid values are changed in the admin area, the comments on existing pages would be wrong and misleading.

- Example values are gone (replaced by ¿). Not sure about this.
Q: Why only ¿ instead of detailed example values?
A: Anything that doesn't fit into the "valid values" of the dropdowns, will not be shown, neither in the dataentry (normal pageview in the wiki), nor in the dataentry editor. Only in the wikisource, you can see those example values.

Contra filling everything with '¿': When looking at the data in either dataentry view or datatable view, fields with no content will not be shown. Fields filled with '¿' however will be shown.

Note: that '@@' stuff is for automatically filling in those values via the bureaucracy plugin.

====== @@Brand@@ @@Model@@ @@Version|@@ ======

{{page>meta:infobox:dataentry_permanote&header&nofooter&noeditbtn&inline&indent&link}}

===== Dataentry =====
---- dataentry techdata ----
Device Type_devicetype               : ¿ # 
Brand                                : @@Brand@@ # ===>  Mandatory  <===
Model                                : @@Model@@ # ===>  Mandatory  <===
Version(s)s                          : @@Version|@@ # List versions comma separated: v1, v1.1, v1.5, v2, v2.5
Availability_availability            : ¿ # 
Supported Since Rev_url              : ¿ # https://dev.openwrt.org/changeset/xxxxx
Supported Since Rel_release          : ¿ # First official release (i.e. not trunk)
Supported Current Rel_release        : ¿ # Current official release (i.e. not trunk)
Platform                             : ¿ # https://dev.openwrt.org/wiki/platforms
Target_target                        : ¿ # https://dev.openwrt.org/wiki/platforms
Instruction Set_instructionset       : ¿ # https://en.wikipedia.org/wiki/List_of_instruction_sets
Sub Instruction Set_subinstructionset: ¿ #
Bootloader_bootloader                : ¿ # http://wiki.openwrt.org/doc/techref/bootloader
CPU MHz                              : ¿ # pure number without 'MHz'; use 'x' to show multiple cores, e.g. 2x 400; use space between 'x' and value;
Flash MB_mbflashs                    : ¿ # CTRL+click for multiselect
RAM MB_mbram                         : ¿ # 
Ethernet 100M ports_numethport       : ¿ # Number of 100Mbit ethernet ports
Ethernet GBit ports_numethport       : ¿ # Number of Gbit ethernet ports
Modem_modem                          : ¿ # Select type of modem
Comments network ports_              :   # Comments on Ethernet, Fibre and Modem
VLAN_yesno                           : ¿ # 
WLAN Hardwares                       : ¿ # "Manufacturer Model# [(onboard/integrated/(mini-)PCI(e))]" / "#x (mini-)PCI(e)"
WLAN Stds_wlanstds                   : ¿ # CTRL+click for multiselect
WLAN 2.4GHz_wlan24                   : ¿ #
WLAN 5.0GHz_wlan50                   : ¿ #
WLAN Comments_                       :   # MIMO, supported status and other WIFI information
Detachable Antennas_numdetachantenna : ¿ # # of detachable antennas
USB ports_usbmultiselects            : ¿ # # of USB2.0 & 3.0 ports; CTRL+click for multiselect
SATA ports_numsataport               : ¿ # # of SATA or eSATA ports
Comments USB SATA ports_             :   # Comments on USB, SATA and eSATA ports
Serial_yesno                         : ¿ # 
JTAG_yesno                           : ¿ # 
LED count_numled                     : ¿ # # of (user configurable) LEDs
Button count_numbutton               : ¿ # # of (user configurable) buttons/switches (other than Power)
Device Page_page                     : :create_new_device_page  # toh:brand:model_version
Device Techdata_hidden               : Techdata # ===>  Fixed value, do not edit!  <===
Forum Topic URL_url                  : http://¿ # forum.openwrt.org/viewtopic.php?id=xxxxx
WikiDevi URL_url                     : http://¿ # wikidevi.com/wiki/yourdevice
OEM device homepage_url              : http://¿ # yourbrand.com/yourdevice
Firmware OEM Stock_url               : http://¿ # yourbrand.com/yourdevice/stockfirmware
Firmware OpenWrt Install_url         : http://¿ # downloads.openwrt.org/…factory.bin
Firmware OpenWrt Upgrade_url         : http://¿ # downloads.openwrt.org/…sysupgrade.bin
Picture_img100s                      : ¿ # media:toh:brand:brand_model_general_view.jpg; Single general picture to identify the device; detail pictures to be provided on device page.
Comments_                            :   # Anything that's worth mentioning
----


{{section>:template_dataentry_background#conventions_for_dataentry_values&nofooter&noeditbtn}}

Still missing due to unclear definition: Reasons for being unsupported / unsupported features

Anything else missing? Comments?

BTW: I *would* start with the tryout, *if* there was that friendly supportive admin doing the neccessary things first... ;-)

Current status of the type alias definitions (see http://wiki.openwrt.org/toh/installatio … iki-admins -> #5)

Type Alias        Valid values
availability      ¿, Available, Discontinued, Discontinued 2010, Discontinued 2011, Discontinued 2012, Discontinued 2013, Discontinued 2014, Discontinued 2015, Discontinued 2016
bootloader        ¿, u-boot, RedBoot, CFE, Adam2, PSPBoot, Bootbase, brnboot, Yamon, MyLoader, NetBoot, PP_Boot, ThreadX, VxWorks, other
brand             (EXAMPLE), 3Com, ADB, ALFA Network, AVM, Actiontec, Airlink101, Allnet, Arcadyan / Astoria, AsiaRF, Asus, BT, Belkin, Buffalo, Cisco, Compex, Comtrend, Cubitech, D-Link, Edimax, EnGenius, Evaluation boards / unbranded boards, Fon, Gateway, Gateworks, Gigaset, Huawei, Inventel, Linksprite, Linksys, Meraki, Mercury, MikroTik, NetComm, Netgear, Nexx, Olimex, PC Engines, Pirelli, Planex, Poray, QNAP, Qemu, Raspberry Pi Foundation, Rosewill, SMC, Sagem, Samsung, Scientific Atlanta, Seagate, Siemens, Sitecom, T-Com / Telekom, TP-Link, Telsey, Tenda, Texas Instruments, Thomson, Trendnet, Turris CZ.NIC, US Robotics, Ubiquiti, Upvel, Western Digital, ZTE, ZyXEL, other
devicetype        WiFi Router, Router, Single Board Computer, Modem, NAS, unknown, other
instructionset    ¿, AVR32, ARM, MIPS, MIPS64, PPC, x86, x86_64, other
mbflash           ¿, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 64NAND, 128NAND, 256NAND, 512NAND, 1024NAND, 2048NAND, 4096NAND, 8192NAND, more than 8GB, more than 8GB NAND, SD, microSD, microSDHC
mbram             ¿, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, more than 4GB
modem             ¿, Yes, No, ADSL, ADSL2+, ADSL2+ Annex A, ADSL2+ Annex B, xDSL, DOCSIS, Powerline, Mobile Wireless/Cellular network
numbutton         ¿, -, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, more than 20
numdetachantenna  ¿, -, Yes, No, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, more than 10
numethport        ¿, -, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, more than 20
numled            ¿, -, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, more than 20
numsataport       ¿, -, 1, 2, 3, 4, 5, 6, more than 6
numusbport        ¿, -, Yes, No, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, more than 10
release           ¿, -, 0.9, 7.06, 7.09, 8.09, 8.09.2, 10.03, 10.03.1, 12.09, 14.07, 15.05, CC trunk, WIP, unsupportable, external image
subinstructionset ¿, ARMv4, ARMv5, ARMv6, ARMv7, ARMv7-A, MIPS IV, MIPS32, MIPS 4K, MIPS 4Kc, MIPS 4Kec, MIPS 24Kc, MIPS 24Kec, MIPS 74Kc, other
target            ¿, -, adm5120, adm8668, ar7, ar71xx, at91, atheros, au1000, avr32, bcm53xx, brcm-2.4, brcm2708, brcm47xx, brcm63xx, cns3xxx, cobalt, ep93xx, imx23, iop32x, ixp4xx, gemini, kirkwood, lantiq, magicbox, malta, mcs814x, mpc52xx, mpc83xx, mpc85xx, mvebu, mxs, netlogic, octeon, olpc, orion, ppc40x, ppc44x, ps3, pxa, ramips, rb532, realview, rdc, sibyte, sunxi, uml, x86
usbmultiselect    ¿, -, Yes, 1x 1.1, 1x 1.1 Device, 1x 2.0, 1x 2.0 Device, 2x 2.0, 3x 2.0, 4x 2.0, 5x 2.0, 6x 2.0, more than 6x 2.0, 1x 3.0, 2x 3.0, 3x 3.0, 4x 3.0, 5x 3.0, 6x 3.0, more than 6x 3.0, Mod, 1x Device, 1x Header, 1x OTG, 1x µUSB (charging), 1x Power only
wlan24            ¿, -, b, b/g, b/g/n
wlan50            ¿, -, a, a/n, a/n/ac
yesno             ¿, Yes, No

Anything missing? Comments?

I think your reasoning about default values and ¿ makes sense. Guess richbhanover is happy too

You want me to updated the comments according to your post 683?

I think we should have some "Unsupported"... not entirely sure if it should be multi choice or just free text.

1) Sorry - I have been swapped out lately on a totally unrelated project (www.pinnacleproject.info)

2) You've seen my note to kaloz - no response for ~48 hours. I think we should send one more note saying that we are almost ready to post our ~912 Technical Data pages to the wiki to enable to the new ToH. (Can we do this without administrative help?) Further, we should say, "We are hoping to do this with approval (or even the help) of the admins, but we really want to move this forward because it will be a significant improvement to the site."

3) I have not kept up with all your thoughts on the naming and contents of fields for the Technical Data pages. But I trust you to do it right (you've been thinking much more deeply about this than I have.)

4) My big concern is what "people see" when they go to create a new page for the router. How much of the wording of the demowiki page template_dataentry_reb is good enough?

5) Along those lines, I still would like to take a shot at making a bureaucracy page for the entire Device Details page.

Rich

PS I note that the demowiki seems to be down right now.

I'm afraid no. We need some more plugins installed, which can only be done by an admin.
http://wiki.openwrt.org/toh/installatio … ctionality

Creating new devicepages via bureaucracy is already implemented in the demowiki.  -> Section "Creating new dataentry / device pages"

1h complete DSL failure, followed by 4h of DDNS update failure
Should be working now.

Yes please!

Hmmm... not sure about that either. What about starting with free text?

I separated the pure template from all explicatory text:
pure template -> template_dataentry
explanations -> template_dataentry_background

New pages are created via create_new_dataentry_page / create_new_device_page.
This page should stay as simple as possible (i.e. do not add explications to this page -> put them in template_dataentry_background / toh:aboutdetailpage instead)

@zo0ok: Wow, we have many entries in the Network comments column.
Some of them seem wrong:
4xGbit , 4xGbit (ZTE ZXHN F660)
4 LAN, 4 LAN , 2 Tel    (Speedport W 503V, 504, 722)

Remark about template_dataentry:

Device Page_page                     : :create_new_device_page

This produces a link to the "create new devicepage" page. See demowiki "Table of hardware - short version" and look at the device page column: Easy way to spot missing pages and create them with the correct template and only a click. Nice

OK, it's not yet the one-click solution, since it only leads you to the "create new" page, but it has the potential: We can pass arguments over to the "create new" page, i.e. you click the link, and the "create new" page will be filled already with Brand, Model, Version. No need any more to enter this manually again.

However, until now, the demowiki resisted my attempts to make it act as expected, i.e. take the arguments and prefill the form. I'll keep trying!

I saw this comment now... considering how much I was against the supported/status column I guess you find it peculiar It will not be completely trivial to auto-fill this one from the old wiki, but I will see what I can do.

The duplication of 4xGbit and 4 LAN is clearly a bug. It replaced "A B" with "A A" from some reason. I need to fix.

However, I am not looking for 4xGbit, only for 4x Gbit. Perhaps we should fix those few instances in the data instead.

About the support from the developers. Either:
1) They don't like what we do and silently ignore it
2) They are busy with CC
3) They are not sure about the long term plan for the site/DokuWiki/documentation anyway, and they have some bigger plans, and now they don't know if they should encourage or discourage this initiative.

I understand why we don't publish @tmo26:s RPi2 version to everyone.

What happens if we get some simple hosting (VPS, Amazon, GoDaddy or whatever) and put a release candidate for public use? The worst thing that can happen is that:
1) People use both, and
2) The developers get pissed because of the confusion, and
3) We can't take the new site down because it contains updated information, and
4) We end up paying for it every month for the rest of our lives.

But with some luck:
1) We resolve the performance questions
2) Show the developers what it is going to be like, which makes them more interested in supporting it
3) Everyone else gets more involved too

Only a little bit.
We're free to change our minds, and sometimes only by playing around with the data, we get a different view.

Ok, I made an update.

1) I removed "WLAN Stds_wlanstds : ¿ # CTRL+click for multiselect" despite it was in 683
2) I REGRET THIS ONE AND UNDID IT
3) I populated the "Unsupported" field with NOTHING for supported devices, and wip/possible/unknown/unsupported for others. In the future, people can put more sensible things into the Unsupported field.
4) I fixed the 4x LAN, 4x LAN bug

The Flash thing... you have made a nice multichoice... but the current field contains stuff like:
  4096NAND+microSD
  8+128NAND
I think we should get rid of all NOR > 64MB and assume all such memory is NAND.
I better fix this, right?

(Last edited by zo0ok on 22 Jul 2015, 11:28)

Hi.

I welcome your initiative but am very low on time so I don't check the forum frequently.
The other developers are indeed busy with CC. If you need administrative changes to the wiki, please mail me directly (jow-at-openwrt-dot-org), this way I don't miss any of your requirements.

Weeee, nice, a reply from jow!

I'll email him regarding installation of the new toh.

Edit: Done.

(Last edited by tmo26 on 22 Jul 2015, 19:23)

I left that one in for comparing the two solutions (multiselect vs. two separate columns). Anyway, doesn't really matter.

Per-fect! Good to see that there's someone thinking along the same line
("Device Page_page: :create_new_device_page " is only meant to be for new devices, not for existing ones)

Good point.
According to the rules for multi-value fields, the '+' should be replaced with comma, i.e. "If comma separated, then the device has all the values listed to offer".
However, there are some devices that have multiple options, i.e. 4,8,16MB. We will lose these multi-options IMHO.

Can't we just pretend we are not aware of this

Another idea... can we add:
  2-8
  4-8
  4-16
  64-128
It is not an optimal solution, but since this is anyway the exception.
The alternative to generate multiple versions is intellectually the nicest, but in practice not even I like it.

We also have:
  16+16
I suppose there is a backup flash so in practice only 16 can be used (at any time). In that case I suggest we write 16. Otherwise I suggest we write 32.