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 > rXXXX). 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
