Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
What I really wish the TOH listing had is some indication of whether the hardware is known to be out of production. Looking for hardware to buy to run OpenWRT is... less than straightforward. This is so absolutely true. I have gone as far as to create a snippet (link included, please don't click, it's horrible) that I run from Chrome's DevTools in order to hide all the routers that have less than certain amounts of flash and ram (https://gist.github.com/Zsub/7868748), but more comprehensive filtering would be very welcome! Joris___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
* Joris de Vries j.s.de.vr...@gmail.com [09.12.2013 09:52]: the hardware is known to be out of production. Looking for hardware to buy to run OpenWRT is... less than straightforward. This is so absolutely true. I have gone as far as to create a snippet (link included, please don't click, it's horrible) that I run from Chrome's DevTools in order to hide all the routers that have less than certain amounts of flash and ram (https://gist.github.com/Zsub/7868748), but more comprehensive filtering would be very welcome! so this leads to some new fields we should take for the upcoming(tm) template: RAM = e.g. '64' FLASH = e.g. '8' and i propose WIFI = '2.4' or '2.4 + 5' or '2.4/5' which means: 1 x 2.4 ghz, 1 x 2.4 and 1 x 5 ghz (sumultan), 1 x 2.4 or 5ghz (either or) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
Thanks for all your comments, there was some valuable input and things worth considering: * i like the idea to give start of sale and EOL dates * Integrating more information directly into the build system also sounds like a good idea, though i'm not really sure how that would be done on a per model basis. And then the question is how much information would we want to add there and if devs also think some model specific info should go directly in the repository. Might need some more thinking about it. But i still think the best way would be to have a database like the prototype i made which can be easily filled by (registered) contributors. That way we can ensure things are named consistently which is needed for good searchability. Then on the other side the most important thing is the api which can output results in json format. It wouldn't be too hard to populate some fields in the wiki which are stored in the database from ajax calls. The bad site about this is of course that it would require javascript (problems for some user groups and especially search engines). So one might think about dynamically creating static pages from the database once a day or so. So in short: Have some fields in the wiki that are populated from the db and at the same time keep it a wiki, so it is still possible to add a lot more info for each model. web2py (which i used for my prototype) could even provide a wiki - but its probably not as good/feature rich as the DokuWiki which is used now. But thats just my very own idea. Generally i would be happy with any solution that makes TOH better searchable and machine readable. Regards, Manuel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
* Manuel Munz freif...@somakoma.de [09.12.2013 14:16]: * Integrating more information directly into the build system also sounds like a good idea, though i'm not really sure how that would be done on a per model basis. And then the question is how much information would we want to add there and if devs also think some model specific info should go directly in the repository. Might need some more thinking about it. IMHO it is OK to just use the wiki for everything. We already have user/password/tracking there and as far as i understand, it should be possible to use this: http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Defining_forms (the openwrt-wiki is mediawiki - isnt'it?) so you can have such forms via a template: http://discoursedb.org/wiki/Special:FormEdit/Item/Some_new_opinion_item so we have all in one place and it gets backupped... (and is machine and user readable) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
* Daniel Golle dgo...@allnet.de [09.12.2013 14:35]: VENDOR - e.g. 'TP-LINK' MODEL - e.g. 'TL-WR1043ND' VERSION - e.g. empty or 'v2' ? SALE_START - e.g. '2013-05' SALE_STOP - e.g. empty or '2014-08' STATUS - e.g. 'broken' or 'r12345' or 'WIP' what about devices which work in old (brcm-2.4) builds but are no longer supported in recent builds? I we should reference a per-version status (e.g. 10.03 'not supported', 12.09 'supported', trunk confirmed to work with/since r). Ideally, openwrt-specific details of the device should thus also be referenced per openwrt build/release, e.g.: * openwrt version (e.g. git tag or revision) * openwrt target arch (e.g. 'ar71xx') * openwrt target flavor (e.g. 'generic') * openwrt profile (e.g. 'TLWR1043') * openwrt boardname (e.g. 'tl-wr1043nd-v1') [...and many other ideas...] hh stop! this is all possible and sounds good, but it drives in a direction where nobody can maintain this. IMHO for further reference the user can just read the wikipage. dont take me wrong. all your ideas are good and helpful to build something really good, but...it's just too much. e.g.: if a target does work anymore: if somebody is interested in getting this to work, he will take a look into git/svn or the wikipage e.g. if a target has multiple brands with the same hardware: just make several wikipages and fillout the template. e.g. if we try to categorize all chips in a router it never ends. so there is a need for such a database (otherwise there would'nt be a discussion), but for which needs? for me: - having a possibility to find firmware-files for the enduser (so we need a table with vendor/model - openwrt-filename) - searching a router which fits XY conditions, e.g. 5ghz (the question again, how far will you go? e.g.: 5ghz + 2.4ghz + 100mbit 5port switch + 64mb ram + not EOL) and you? bye, bastian. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
On 09.12.2013 14:18, Daniel Golle wrote:
what about devices which work in old (brcm-2.4) builds but are no longer
supported in recent builds? I we should reference a per-version status (e.g.
10.03 'not supported', 12.09 'supported', trunk confirmed to work with/since
r). Ideally, openwrt-specific details of the device should thus also be
referenced per openwrt build/release, e.g.:
* openwrt version (e.g. git tag or revision)
* openwrt target arch (e.g. 'ar71xx')
* openwrt target flavor (e.g. 'generic')
* openwrt profile (e.g. 'TLWR1043')
* openwrt boardname (e.g. 'tl-wr1043nd-v1')
Thats is almost like i proposed in my database schema, so i agree. We
need to have these things on a per-release basis (target name or profile
etc might change between releases). If a device does not have an entry
for firmware x then we can suppose the device is not supported by that
firmware. trunk will be a bit special and should indeed contain a
supported since rev field.
other ideas?
* EAN/barcode (image the can this box run openwrt bar-code-scanner android
app
which can eventually become a mobile installer tool to flash openwrt via the
stock firmware web-interface after scanning barcode on the package..)
yes, should be easy to build things upon such a database
* links (e.g. wikidevi record, vendor product page, stock firmware/dumps, ...)
i also implemented this partially, would be easy to add more links.
* target market ('ETSI', 'FCC', 'China', 'World', ...)
good idea, didn't think of that yet
* some way to add aliases for OEM products sold by multiple brands
i like that too
* maybe we should use a more atomic approach instead of a table with a lot of
rows?
i.e. have 4 tables, attributes, components and n-to-n mappings for
attributes-components and components-components
i tried to do it similar but with more tables because it also appears
most reasonable to me. e.g. specify which and how many chips
(flash/ram/wifi etc) are in the device and have infos for these in
seperate tables.
Regards, Manuel
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
On 2013-12-05 04:17, Bastian Bittorf wrote: * James Hilliard james.hillia...@gmail.com [05.12.2013 08:43]: Well, some information can likely be pulled directly from version control, such as model/chipset/broken status/supported etc. That information could then be tied into a wiki templating system to autogenerate pages which could have additional model specific information added if available. I what is missing then is the router name, e.g. VENDOR and MODEL - e.g. 'TP-LINK TL-WR1043ND' What I really wish the TOH listing had is some indication of whether the hardware is known to be out of production. Looking for hardware to buy to run OpenWRT is... less than straightforward. Maybe I should just go add a TOH field -- 'tis an ill wind that blows no minds. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
* Joshua Judson Rosen jro...@harvestai.com [09.12.2013 08:38]: what is missing then is the router name, e.g. VENDOR and MODEL - e.g. 'TP-LINK TL-WR1043ND' What I really wish the TOH listing had is some indication of whether the hardware is known to be out of production. Looking for hardware to buy to run OpenWRT is... less than straightforward. good idea! but must be human and machine readable that it not easy in a wiki, because everybody has to use the exact same syntax. Maybe I should just go add a TOH field so a template should contain: VENDOR - e.g. 'TP-LINK' MODEL - e.g. 'TL-WR1043ND' VERSION - e.g. empty or 'v2' ? SALE_START - e.g. '2013-05' SALE_STOP - e.g. empty or '2014-08' STATUS - e.g. 'broken' or 'r12345' or 'WIP' other ideas? im unsure if a template can be made of pulldown-menues. this can help to avoid mistakes in spelling e.g. for VENDOR, STATUS and dates. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
- Original Message - From: Bastian Bittorf bitt...@bluebottle.com To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Thursday, December 5, 2013 10:17:56 AM Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH? * James Hilliard james.hillia...@gmail.com [05.12.2013 08:43]: Well, some information can likely be pulled directly from version control, such as model/chipset/broken status/supported etc. That information could then be tied into a wiki templating system to autogenerate pages which could have additional model specific information added if available. I what is missing then is the router name, e.g. VENDOR and MODEL - e.g. 'TP-LINK TL-WR1043ND' there are e.g. images which are the same for ~10 models (atheros,brcm47xx,ar71xx/ubnt), but the real usage of this thing is a better searchable 'whatever' for the user, so it must be human-readable... IMHO the best thing would be to cleanly integrate that into the buildsystem and not in the wiki... You'd still need the wiki for further notes, though. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
Hi, i needed a database to be able to implement a selector where users can choose their router model and from that parameters like target/subtarget/profile/others are automatically set for the selected model. A first demo for this can be seen here (where it says WIP): http://testing.meshkit.freifunk.net/ For that reason i started playing with a router database using web2py as framework. A somehow working demo version can be found here: http://meshkit.freifunk.net/routerdb Login as user openwrt and with password openwrt to be able to edit routers (that part is still a bit ugly) and wiki pages (also not as nice as other wikis, but its usable). I already implemented a lot of stuff in the database schema as you can see here: http://meshkit.freifunk.net/routerdb/static/images/bg_graph_model.jpg I also just comitted the code for it: https://github.com/mmunz/openwrt-routerdb This is more than i need for my usecase, but i wanted to experiment what is possible. The question for me is now: Is it worth putting more time into this and further improve it? Is there any interest in trying to figure out how such a database could be combined with TOH in wiki? Regards, Manuel signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
- Original Message - From: Manuel Munz freif...@somakoma.de To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Wednesday, December 4, 2013 10:27:49 PM Subject: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH? Hi, i needed a database to be able to implement a selector where users can choose their router model and from that parameters like target/subtarget/profile/others are automatically set for the selected model. I like the idea. But you also need someone to maintain the content. Even the official TOH is obsolete already (e.g. there's no information about tp-link 1043nd v2). You'd need a full replacement for the wiki TOH (making the TOH obsolete once again) as well as an easy way to add loads of information and comments and people willing to update the data. Or, alternatively, you could just specify some format bits for the wiki and feed the database from the wiki. A first demo for this can be seen here (where it says WIP): http://testing.meshkit.freifunk.net/ It looks a little bit too javascripty for me. I would like to be able to *also* just view the table of hardware like I do in the wiki. Cheers, Pavel For that reason i started playing with a router database using web2py as framework. A somehow working demo version can be found here: http://meshkit.freifunk.net/routerdb Login as user openwrt and with password openwrt to be able to edit routers (that part is still a bit ugly) and wiki pages (also not as nice as other wikis, but its usable). I already implemented a lot of stuff in the database schema as you can see here: http://meshkit.freifunk.net/routerdb/static/images/bg_graph_model.jpg I also just comitted the code for it: https://github.com/mmunz/openwrt-routerdb This is more than i need for my usecase, but i wanted to experiment what is possible. The question for me is now: Is it worth putting more time into this and further improve it? Is there any interest in trying to figure out how such a database could be combined with TOH in wiki? Regards, Manuel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
I would say that the best thing to do would be to tie a replacement TOH directly into version control and have supported router models populate directly from there somehow. Maybe something along the lines of how cyanognmod uses their template system http://wiki.cyanogenmod.org/w/Template:Device_info would work. On Thu, Dec 5, 2013 at 12:25 AM, Pavel Simerda psime...@redhat.com wrote: - Original Message - From: Manuel Munz freif...@somakoma.de To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Wednesday, December 4, 2013 10:27:49 PM Subject: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH? Hi, i needed a database to be able to implement a selector where users can choose their router model and from that parameters like target/subtarget/profile/others are automatically set for the selected model. I like the idea. But you also need someone to maintain the content. Even the official TOH is obsolete already (e.g. there's no information about tp-link 1043nd v2). You'd need a full replacement for the wiki TOH (making the TOH obsolete once again) as well as an easy way to add loads of information and comments and people willing to update the data. Or, alternatively, you could just specify some format bits for the wiki and feed the database from the wiki. A first demo for this can be seen here (where it says WIP): http://testing.meshkit.freifunk.net/ It looks a little bit too javascripty for me. I would like to be able to *also* just view the table of hardware like I do in the wiki. Cheers, Pavel For that reason i started playing with a router database using web2py as framework. A somehow working demo version can be found here: http://meshkit.freifunk.net/routerdb Login as user openwrt and with password openwrt to be able to edit routers (that part is still a bit ugly) and wiki pages (also not as nice as other wikis, but its usable). I already implemented a lot of stuff in the database schema as you can see here: http://meshkit.freifunk.net/routerdb/static/images/bg_graph_model.jpg I also just comitted the code for it: https://github.com/mmunz/openwrt-routerdb This is more than i need for my usecase, but i wanted to experiment what is possible. The question for me is now: Is it worth putting more time into this and further improve it? Is there any interest in trying to figure out how such a database could be combined with TOH in wiki? Regards, Manuel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?
Well, some information can likely be pulled directly from version control, such as model/chipset/broken status/supported etc. That information could then be tied into a wiki templating system to autogenerate pages which could have additional model specific information added if available. I don't think Cyanognemod imports directly from version control but as many devices are extremely similar they use master templates to define aspects that are the same. Some devices would probably still have to be manually added but there may be a way to generate indexes from version control in mediawiki, such as target subtarget and device profiles. By creating corresponding templates there would at least be some usable information about a device under one page even if nobody wrote anything specifically about it in the wiki entry. Cyanogenmod also uses the repo system for version control which is a little different than traditional svn/git. I wonder if repo would be useable for a project like openwrt, it certainly makes readability better by clearly defining what is device specific in separate git repos. I think it also allows global build overrides per device. Right now OpenWRT is not all that accessable to the general public due its rather unique and somewhat confusing build system in addition to the source code itself being the only documentation for a number of devices. Just thinking of ideas that may make things more available to the general public. On Thu, Dec 5, 2013 at 12:52 AM, Pavel Simerda psime...@redhat.com wrote: - Original Message - From: James Hilliard james.hillia...@gmail.com To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Thursday, December 5, 2013 7:36:56 AM Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH? I would say that the best thing to do would be to tie a replacement TOH directly into version control and have supported router models populate directly from there somehow. Yeah, that sounds even better. But don't you still need a place (wiki) to handle the notes about specific (whether supported or unsupported) hardware, so that people can easily share the information? Maybe something along the lines of how cyanognmod uses their template system http://wiki.cyanogenmod.org/w/Template:Device_info would work. Does that mean they're importing the device info directly into the wiki? Pavel On Thu, Dec 5, 2013 at 12:25 AM, Pavel Simerda psime...@redhat.com wrote: - Original Message - From: Manuel Munz freif...@somakoma.de To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Wednesday, December 4, 2013 10:27:49 PM Subject: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH? Hi, i needed a database to be able to implement a selector where users can choose their router model and from that parameters like target/subtarget/profile/others are automatically set for the selected model. I like the idea. But you also need someone to maintain the content. Even the official TOH is obsolete already (e.g. there's no information about tp-link 1043nd v2). You'd need a full replacement for the wiki TOH (making the TOH obsolete once again) as well as an easy way to add loads of information and comments and people willing to update the data. Or, alternatively, you could just specify some format bits for the wiki and feed the database from the wiki. A first demo for this can be seen here (where it says WIP): http://testing.meshkit.freifunk.net/ It looks a little bit too javascripty for me. I would like to be able to *also* just view the table of hardware like I do in the wiki. Cheers, Pavel For that reason i started playing with a router database using web2py as framework. A somehow working demo version can be found here: http://meshkit.freifunk.net/routerdb Login as user openwrt and with password openwrt to be able to edit routers (that part is still a bit ugly) and wiki pages (also not as nice as other wikis, but its usable). I already implemented a lot of stuff in the database schema as you can see here: http://meshkit.freifunk.net/routerdb/static/images/bg_graph_model.jpg I also just comitted the code for it: https://github.com/mmunz/openwrt-routerdb This is more than i need for my usecase, but i wanted to experiment what is possible. The question for me is now: Is it worth putting more time into this and further improve it? Is there any interest in trying to figure out how such a database could be combined with TOH in wiki? Regards, Manuel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
