Also known as glinet spitz. The mips processor is big endian, so the
current release driver 1.14.1 will not work. I have however tested this
with the big endian patchset and it works.
The board has only 16MB flash, so I have restricted the packages.
The usb port is disabled by a gpio in the upstream dts. I have edited
that to enable the port at boot.
Approved-by: James Haggerty
Approved-by: Lyall Beveridge
The reason for this change is to ensure the wifi module is inserted before morse.
This reintroduces a change which we 'lost' in the rebase as theoretically
not necessary, but found it introduced a regression.
Putting the module this early in the load ensures that phy0 is reliably allocated
to the mt76 module; we were finding that it was variable due to mt7603/morse being next to each other alphabetically, which meant that the LED (set to phy0-ap0)
would sometimes not come up.
Ideally, we would have either a generic way of determining module order for
a particular board, OR make the LED code smarter such that you could
specify a device path or similar instead of an ifname, but both of these
are large changes that do not belong in a point release.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
We've decided that we shouldn't have matter in this release
until we sort out the doco.
Strictly, this should be in the 2.7 release branch, but I'm
pulling it in early to help our builds get faster.
Approved-by: Arien Judge
Approved-by: Lyall Beveridge
If you don’t have this a clean build now prompts you to select
an option for RAVE_SP (causing a failure unless you run with V=sc
and answer the option).
I'm a bit confused about why this is suddenly necessary AND why the
default make kernel_*config doesn't populate it, but it's echoing a
change that went in with the matter PR for artini.
I’m also concerned that this means we probably should be regenerating
other kernel configs (since people might take this SDK and expect it
to work for other archiectures), but the good news there is that most
of them already have the RAVE thingy.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
SW-12275 add support for releasing matter with openwrt
* Update bluetooth make components (other.mk) with correct config option
* Add matter defconfig for all ekh boards
Approved-by: Cedric Van den Bergh
Approved-by: James Haggerty
Approved-by: Julia Page
Plan is to rename ekh01s to include the chip id.
For now, let's just mess with the image name; we can
consider whether we want to modify the model name
(and the internal identifier) once MM8108 settles.
Approved-by: Sophronia Koilpillai
Approved-by: Arien Judge
It's more interesting to see a HaLow activity LED than an
SD card LED, and this lines up with our priorities on the EKH03
(where we now show HaLow link/activity on the single RGB LED).
Approved-by: Milad Mohtashamirad
Approved-by: Lyall Beveridge
This removes the extra functionality based aliases from the ekh03
(which are no longer used) and adds colour based aliases, which
make the diag_override.sh script clearer when we're using
multiple LEDs to construct a colour.
Note that we leave the old aliases in so that the board
will work without our custom LED package (morse-led-rgb).
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
Note that this is tricky because we want the LED to be green
when the link is off and purple when the link is on.
This requires a patch to the netdev driver to support invert.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
To achieve this, we repurpose dppd_diffconfig to be a
'include dpp qrcode support' thing, which implies
dpp-key-recovery (to recovery/generate the private key for
the STA side) and dppd (for the AP side).
Note that netifd-morse is still responsible for generating
the qrcode, as there's nasty 'look at the mac address
on initial module load' hacked in, but it now only
does this if the dpp private key exists.
Approved-by: Evan Benn
Approved-by: Milad Mohtashamirad
AP side wizard: configure in UI
STA side wizard: on first connection, reconfigure if it can
find an artini AP with config.
This leads to a lot of LED flashing:
- DPP config
- Bring down interface and bring up normally
- Potentially do this again once we find our config
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
Some targets may not support USB host mode. So move the kmod packages,
and disable the hardware in artini's dts.
Approved-by: James Haggerty
Approved-by: Sophronia Koilpillai
Add configuration to artini dts and code to the LED drivers to support
bringing up the status led in the desired pattern and color. Without
this patch the multicolor-led driver briefly turns the led off (uboot
turned it on) before diag.sh runs to turn it back on.
Approved-by: Sophronia Koilpillai
Approved-by: James Haggerty
The status LED is now driven by the PWM driver. When the driver is built as
a kmod module, it is loaded after the preinit state is set. This means
the diag.sh script cannot set the color and flashing pattern. Making the
driver built in means the LED can be controlled at preinit stage.
Approved-by: James Haggerty
Approved-by: Sophronia Koilpillai
With multi-profile builds, we lost the ability to be
very specific about our targets (e.g. -b ekh01 became
-b ekh-bcm2711).
Add aliases in based on the actual device names in the configs,
+ help for that. Bonus help for -x as well.
Approved-by: Evan Benn
Approved-by: Lyall Beveridge
This lets us build a bunch of images at the same time.
Note that I've rolled in all the ekh01_hw_diffconfig
and ekh_diffconfig into here since it's not shared around
as much. As a nice side effect of this, this also makes
minimal builds better (i.e. you don't have to add -x ekh -x ekh01_hw
to get a sane build).
Using multi-profile builds allows removal of duplicated configs.
(APP-3652, PR #318)
Approved-by: Arien Judge
Approved-by: Evan Benn
Approved-by: Milad Mohtashamirad
The virtual wire package allows for devices to be configured as an
access point or station with a jumper or switch. Assosciation is
handled by dpp push button, and channel selection by DCS on the
largest bandwidth for a region configured at device production.
Include the package as a configuration option.
Morse Micro's smart manager adds Dynamic Channel selection capability
within the configured bandwidth. Include the feature in the default
set of packages used by Morse Micro board targets.
