Hi Adrian,
On Tue, Sep 24, 2019 at 6:22 PM wrote:
> I'm all about consistency. I just scanned the image definitions in ramips:
>
> ...
>
> The only device deviating from the pattern "zbtlink_zbt-something" is
> zbtlink_we1026-5g-16m.
>
> So, IMO the correct solution _in terms of consistency_
Hi,
> I prefer consistency, so my preference would be staying with the initial
> naming scheme used for this "family" of devices.
I'm all about consistency. I just scanned the image definitions in ramips:
define Device/zbtlink_zbt-we1226
DEVICE_VENDOR := ZBTlink
DEVICE_MODEL := ZBT-WE1226
Hi,
On Tue, Sep 24, 2019 at 1:28 PM Adrian Schmutzler
wrote:
>
> Hi,
>
> first of all:
> Naming scheme for ZBT devices is mixed in ramips. Some include the ZBT in
> model name, some don't. In your case, this means the following options:
> zbtlink,zbt-we1026-hcorresponding to model
> Subject: [OpenWrt-Devel] [PATCH v2 2/2] ramips: Add support for ZBT WE1026-H
>
> This commit adds support for the ZBT WE1026-H, an outdoor AP with
> support for adding an internal LTE modem. The detailed specs are:
>
> * CPU: MT7620A
> * 2x 10/100Mbps Ethernet (LAN port ha
This commit adds support for the ZBT WE1026-H, an outdoor AP with
support for adding an internal LTE modem. The detailed specs are:
* CPU: MT7620A
* 2x 10/100Mbps Ethernet (LAN port has passive PoE support).
* 16/32 MB Flash.
* 128/256 MB RAM.
* 1x USB 2.0 port.
* 1x mini-PCIe slot (only USB2.0
