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.freif
- Original Message -
> From: "Manuel Munz"
> To: "OpenWrt Development List"
> Sent: Wednesday, December 4, 2013 10:27:49 PM
> Subject: [OpenWrt-Devel] Interest in a openwrt router database to partially
> replace TOH?
>
> Hi,
>
> i neede
/Template:Device_info would work.
On Thu, Dec 5, 2013 at 12:25 AM, Pavel Simerda wrote:
> - Original Message -
> > From: "Manuel Munz"
> > To: "OpenWrt Development List"
> > Sent: Wednesday, December 4, 2013 10:27:49 PM
> > Subject: [OpenWrt-Devel] Inter
- Original Message -
> From: "James Hilliard"
> To: "OpenWrt Development List"
> 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 th
52 AM, Pavel Simerda wrote:
> - Original Message -
> > From: "James Hilliard"
> > To: "OpenWrt Development List"
> > Sent: Thursday, December 5, 2013 7:36:56 AM
> > Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to
> p
* Manuel Munz [05.12.2013 08:43]:
> 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
this is interesting, we also did something like that, but manually:
bastian@gcc20:
* James Hilliard [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 speci
- Original Message -
> From: "Bastian Bittorf"
> To: "OpenWrt Development List"
> Sent: Thursday, December 5, 2013 10:17:56 AM
> Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to
> partially replace TOH?
>
> * James Hil
On 2013-12-05 04:17, Bastian Bittorf wrote:
* James Hilliard [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
* Joshua Judson Rosen [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 r
> 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
* Joris de Vries [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) t
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 mo
On 12/09/2013 08:52 AM, Bastian Bittorf wrote:
> * Joshua Judson Rosen [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
* Manuel Munz [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 th
* Daniel Golle [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
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, openw
17 matches
Mail list logo
