Since the BR-6225N has only 4Flash 16RAM, I suggest you first get it working, then report back in a forum thread (not here, create a new one), then add the device to the ToH.

Honestly, I doubt that you will get it working stably with an up to date OpenWrt. Surprise me!

@tmo26, @zo0ok, and others - The tabbox is spectacular! It provides a structured way for people to include the info from the ToH without having it drift all over the page.

I learned that you can put the tabbox in a <WRAP 80%> ... </WRAP> container to constrain it to fit within the TOC that appears on most Device Pages. See https://wiki.openwrt.org/toh/netgear/wndr3800

Would it make sense to modify the device page template (https://wiki.openwrt.org/meta/template_device) to replace the several datatable's with a tabbox near the top? (There would be some trickiness to auto-generating the filters properly...)

Please update the toh page for TL-WR710N.
See https://forum.openwrt.org/viewtopic.php?id=33908 for description of current issue (support for v2.1).

Hi Pato - You can update the Table of Hardware page yourself by registering for the OpenWrt wiki. (I'm not sure what the changes should be, and you are obviously very familiar...)

Update on Tabbox: See how it looks at: https://wiki.openwrt.org/toh/mqmaker/witi

Changes - all in the page above, or playground:template_datatemplatelinklist or playground:template_datatemplatelinklist

- I factored out the "Links" items (from the Hardware Details) into its own tab.
- Capitalize all tabs;
- Remove redundant "View/Edit" links (only in the "Links" tab now)
- Added OEM firmware link to the Firmware Downloads page
- Assorted other cleanups.

It looks good for a device with a single dataentry. Now to check it with multiple dataentry's.

re: Tabbox for device with multiple dataentry's... Not dreadful - see https://wiki.openwrt.org/toh/netgear/wn … cteristics

1) Comments: Which comment belongs to which device?
2) The WRAP is getting ugly big, especially with the comments below.
3) OpenWrt support needs to be first, before anything else.
4) Hardware highlights is second
5) Hardware details is next (no sense to tear those two hardware sections apart)
6) WRAP is not wide enough, wastes space
7) Links: urgs. This is ugly. Very ugly.
8) Forum link needs to be in "OpenWrt support" (i.e. in the first tab)
9) FW download links: Makes more sense to put them in a conventional datatable in the "Installation" section. That's were this information is really needed.
10) Links: No need to mention FW downloads twice (Links + FW downloads tab)

(Last edited by tmo26 on 20 Jan 2016, 19:25)

re: Netgear WNDR3700 and WNDR37AV – Added tab box showing all characteristics

richb: Sorry to say, but our task is not to confuse the reader by overwhelming him with lots of information.
Not sure which way to go for devices with multiple versions, but the tabbox on this page is the contrary of what we want to achieve.

EDIT: I have been thinking long time about devices with multiple versions, but havn't come to a final solution yet. It's complicated and needs more thorough thinking.

(Last edited by tmo26 on 20 Jan 2016, 20:05)

It is great to see that you are getting into the Device Pages, and including Data Entry-data dynamically!
The tab boxes look great, and they have potential.

Regarding the WNDR3700 page...
Hardware Higlights, OpenWrt Support and Firmware Downloads work pretty nice!
Links... lacks headers for each device... a Matrix/Table, not showing the entire link, just "link" would have been nice, but perhaps it is too much to ask?
Hardware details... I think the idea with the tabs is that it should all easily be visible on a single screen. My screen is 1366x768... and it does not fit

It seems to be quite the same result for WNDR3800.

I guess the purpose with the tab box is make the page easier to navigate (by not having very much tabular detailed data to scroll by). So each tab should be kept reasonably small, and they should have quite the same size as well, to help readability.

The primary/default tab...
Maybe SoC, WLAN Hardware and Modem are not needed.
Perhaps we should include Current Release instead.
...I dont know... just some gut feeling... we need to have a clear idea of what we want to achieve, so the result is consistant rather than confusing.

It already looks good, and I see plenty of potential (to hide, yet make easily available, information that otherwise takes up too much space and attention at first).

Maybe I'm just not into irony, but I'm for sure not familiar with that. I would like to install Chaos Calmer on my device, but there isn't any factory image at http://downloads.openwrt.org/ available. Since I do not have any knowledge and environment to build one, I would ask anyone to do so - and post it in the toh. If it does not work this way, I am sorry for bothering - as you can see - this is my third post.

I don't think there was any irony, but I understand you may have interpreted it that way.

We are a few people in this forum topic discussing and improving the structure of the Table of Hardware and the wiki. Occationally, it means we also improve the data or documentation about specific devices. However, maintaining and improving documentation about specific devices, must be done by the community: people who own the devices and have first hand experience.

So the suggestion above was not ironic: If you happen to know anything about TL-WR710N (I know nothing about that device), you are much encouraged to improve the documentation on the wiki. And since you seem to have found something in a forum topic that is not in the wiki, it is great if you update the wiki with that information.

Getting an account on the wiki and editing the information is not much harder than getting a forum account and posting here It is a little harder, and a little more scary: but it is great if you take the time!

If you really dont want to edit the wiki yourself: post exactly what paragraph you want changed, and how you want it to be. Then I can just copy-paste your changes.

(Last edited by zo0ok on 21 Jan 2016, 22:00)

Thanks for that useful information! I could maybe give you some suggestions in changing the wiki-page of TL-WR710N:
In the hardware highlights: Mark that v2.1 is not supported since 15.05, but only by current snapshot, because 1.x images do not work, even though v2.1 has 8MB flash (same as 1.x).
Hence the following sentence is not true (different hardware-revision?) :
"v2.1 is basically a re-issue of the v1.2."
In "Hardware Images" the following sentence is wrong:
15.05 Chaos Calmer:
v1.x and v2.1: (Image links)
Pls change to v1.x ONLY!

Maybe additionally info (see quote from https://forum.openwrt.org/viewtopic.php … &p=3):

Since i am also a total newbie, can someone pls tell me who is responsible for the builds listet in downloads.openwrt.org!
Are current unsupported devices going to be supported afterwards by recent releases (will there be in the future any CC-images for TL-WR710N v2.1)??
And if NOT: When will the next stable release (after Chaos Calmer) being submitted (give some suggestion)?
I don't want to run my device with the current snapshot, dont want to risk a brick. ;-)
Thanks in advance

(Last edited by pato on 22 Jan 2016, 17:37)

Thank you pato...

tmo26/richbhanover: lets talk about this here, since it is about understanding hardware versions and images
We have:

1.X => v1 image
2.0 => v2 image (dont know if it exists)
2.1 => v1 image (but requires simple source code modification)

I SUPPOSE the patch/source fixes that make it compatible with 2.1
  https://forum.openwrt.org/viewtopic.php … 28#p290628
can be made in such way that it is both compatible with 1.X and 2.1.

Otherwise we will get more images.

I dont know how to patch it to work with both 1.X and 2.1. But I can try to figure out.

Which leads to the question of submitting patches. I have submitted one patch that basically added two lines, and it took me several weeks to get it approved. But I should be able to be faster this time. Perhaps a newbie guide to submitting patches? Well, that should be a separate topic.

pato: does it work with trunk?
It seems 15.05.1 is not too far away: https://lists.openwrt.org/pipermail/ope … 38726.html
If it works with trunk, chances are it will work with 15.05.1.

Why patch?

https://dev.openwrt.org/changeset/47849 adds support for 2.1 -> 2.1 image available here https://dev.openwrt.org/changeset/47849

Can someone confirm that the 2.1 trunk image is working?
Do we have evidence that the v1 image and the v2 image are not working on v2.1?

There's not downloadable .bin image there I can flash. Can you point me to one? I just bought a new router after consulting the Wiki thinking it's a quick install and now I am stuck with a broken snapshop image not being able to even go back to stock

Any help would be highly appreciated!

(Last edited by el_commandante on 22 Jan 2016, 23:14)

Oooops!

https://downloads.openwrt.org/snapshots … x/generic/

So it (image for WR710N v2.1) will probably be in 15.05.1, which should not be too far away. Or use trunk today (which may not be so good for beginners).

Let's point out the important part of that issue:
Support in source code has been added for v2.1 recently (not in 15.05 release BUT in trunk).
E.g. I can confirm v1.x images not working for v2.1.
That is why I am asking someone to CHANGE the wiki page, because there is WRONG information.
Especially for newbies like me it is a critical thing, because devices may be bricked by flashing trunk images.

As you can see in the quote, other users are getting their devices not working because of wrong info.

Kind regards

Can someone confirm that the 2.1 trunk image is working?

I know you have emphasized your noobie status, but it appears that you are the one here with the expertise and experience to know that the wiki is "WRONG".  It's no one else's responsibility any more than it is yours to fix it, and no one else may know any more than you do about what is wrong with it.

(Last edited by lizby on 26 Jan 2016, 19:50)

lizby: Well phrased!

If $everyone relies on $someone to do $something, then $nothing will be done by $noone.
If $noone is doing it for you: DIY.

BTW: I updated the dataentry of 710N v2.1.

@pato: It looks as if @tmo26 has done it, but for future reference, it's pretty straightforward to edit info about a router. You need only create an account on the OpenWrt wiki. Once you're authorized, go to the Table of Hardware and find your device.

Click the "View/Edit Data" link for your device to get to its "Techdata" page. Click the "Edit" button at the bottom/left side of the page, and fill in the correct info. (Don't click the Edit button on the right - that risks the template that controls the ToH formatting.)

Refering to https://forum.openwrt.org/viewtopic.php … 49#p307249

"brcm47xx and bcm53xx don't need any special image for sysupgrade. You just use the standard one."
https://forum.openwrt.org/viewtopic.php … 83#p298683

One more piece of the puzzle

Interesting:

Here, none of the images are named sysupgrade (for the reason you just gave):
  https://downloads.openwrt.org/chaos_cal … x/mips74k/

Here, on the other hand:
  https://downloads.openwrt.org/chaos_cal … ps/mt7620/
almost all images are named sysupgrade (despite I know that for Archer C20i), the image can be used to install from OEM.

I've been playing around with these two pages:

1) https://wiki.openwrt.org/meta/create_new_dataentry_page
Depending on OpenWrt support status, you are able to create a new dataentry or not.
  - Supported -> OK for new dataentry; an additional fieldset pops up and requests more data (of which only the changeset is mandatory)
  - Unsupported -> NOK for new dataentry. We have too many I-wish-I-was-supported devices in the ToH.

2) https://wiki.openwrt.org/meta/playgroun … vice_page2
Added multiple templates to chose from:
  - empty (not much in there)
  - devel (development focused info)
  - supported (full template, makes use of datatables / dataentries)
Added destination (inbox for incomplete/WIP pages; toh for supported devices)

Please let me know your thoughts on this.