I've also killed the legacy EKH01-01 to keep things straightforward,
as this will enable us to remove all the BCF forcing code.
Approved-by: Sophronia Koilpillai
Approved-by: Lyall Beveridge
Forcing the 'old' morse,ekh01 name means we can
downgrade without forcing (in non-SPI cases).
Approved-by: Sophronia Koilpillai
Approved-by: Andrew Dodd
Need more dollars due to include, + allow upgrading ekh01-01 image
(which was previously used for rpi4+RD09) to the more generic rpi4 image.
Approved-by: Sophronia Koilpillai
Approved-by: Andrew Dodd
- push EKH01 -> MMx108-EKH01 change into more places
- separate SDIO from SPI images so:
- we can enable RPI's internal WiFi on SPI images
- we no longer have errors related to SPI/SDIO missing
- we can have a shared SDIO image that most people can use
- have an EKH style image which an RPI can use (i.e. no overlays)
(also leaves wifi enabled)
- all old images will upgrade to equivalent new images
- retain 'legacy' SPI+SDIO images with BCF forcing if
people prefer these, particularly since we don't
force BCF selection on the landing page
(and use would have to go to the networking config)
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
Previously, this was done in the frontend display only (e.g. model name).
We should have just properly done the change originally.
Approved-by: Prabha Murugesan
Approved-by: Lyall Beveridge
Without this change, the bcm bluetooth module wasn't built on non-bcm
boards but it was still included in the package so building
the ipk would fail. This change makes the bcm module be built
like the other modules.
I think the question re RAVE_SP is also related to the bluetooth
change, but I've seen it pop up way too many times to fix it again
in a specific config file (and putting a not set in is a safe operation).
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
When the new LED pwm driver was added, in certain circumstances
it now wants to ask a bunch of pwm related questions.
'not set' makes these go away.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
- add the ability to override the reset button handling
- add a package which handles the 'improved' reset button handling
- make the ekh-mt76x8 targets have a reset button
- allow diag_override.sh to use existing code in diag.sh
Approved-by: Sophronia Koilpillai
Approved-by: Milad Mohtashamirad
The blue LED was not working. I copied the gpio configuration from
ekh03v3 to ekh04. The LED is now working.
Approved-by: James Haggerty
Approved-by: Lyall Beveridge
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
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
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
Add OpenWrt target definitions to produce images for the EKH03 and EKH04
versions of Morse Micro evaluation kits. Included in this commit are:
* kernel config changes to enable pstore for ramoops, USB serial devices,
and other miscellaneous generated changes.
* a preinit script to mutate the board_name propagated through OpenWrt
* inittab changes to remap the default serial interface
The mainline mmc driver offers improvement in CPU performance by
allowing more data utilise DMA. This change resulted in a 3 Mbps
increase in Morse Micro HaLow throughput.
Add the driver by default to the mt76x8 kernel config and the mt7628
device tree.
Previously, we'd just been modifying the distroconfig.txt for
all RPIs. This has the advantage that we'd pick up any upstream
changes.
However, for SDK users this is potentially annoying, as they
may want their own set of customisations. It's also a bit
strange that a 'normal' RPI build would have our HAT overlay.
This changes it so we have a custom distroconfig.txt for
ekh01 devices only which completely replaces the base
distroconfig.txt.
Approved-by: Arien Judge
Approved-by: Evan Benn
We want to use the normal rpi4 device tree, but have OpenWrt
report different model names. To easily use multi-profile builds,
this has to happen somewhere outside the rootfs.
Approved-by: Arien Judge
Approved-by: Evan Benn
Add OpenWrt target definitions to produce images for the EKH01 versions
of Morse Micro evaluation kits. Included in this commit are:
* kernel changes to enable by default SPI support, pstore for ramoops,
USB serial device and the default CPU governor.
* a preinit script to mutate the board_name propagated through OpenWrt
* kernel cmdline changes to support a USB serial adapter for console
access
config.txt is the 'user' config which is retained on upgrade,
whereas distroconfig is the distro defaults that might change
on upgrade.
This also means we pick up the OpenWrt default of disabling bluetooth
and the miniuart.
Approved-by: Arien Judge
Approved-by: Evan Benn
keep.d: (APP-1962) Remove config.txt and cmdline from keep.d
* keep.d: (APP-1962) Remove config.txt and cmdline from keep.d
All filenames in keep.d are retained if the user chooses 'retain config'
in an update. There is no way for the update to override this at update
time. We may want to modify the command line or bootloader config in
a future update, and as we are supporting 'retain configs' we must
remove these files from keep.d. This will only affect updates FROM the
image that includes this patch.
Approved-by: Arien Judge
Approved-by: Takura Mapani
Otherwise, on upgrade we retain the overlay if the rootfs size is the
same (causing confusing behaviour). This was taken from
https://github.com/openwrt/openwrt/issues/9113#issuecomment-1572846457
However, ensure we only clear the bit at the end of the partition to
ensure we don't generate unnecessarily large images for the EKH01.
See https://github.com/openwrt/openwrt/pull/13793
Approved-by: Milad Mohtashamirad
Approved-by: Arien Judge
Approved-by: Evan Benn
For the Raspberry Pi based platforms, we add device tree overlays to
instantiate the appropriate hardware configuration for MM6108.
SPI and SDIO options are available, as well as relevant power save
configuration.
Also add a ramoops overlay.
MM6108 does not support 1.8V but offers voltage negotiation. Add
required quirk to kernel.
Additionally, issues in kernel 5.x versions of the BCM2835 SPI driver
have been reported, particular regarding CS polarity. The patch rolls
the driver back to 4.19.
When you have an RGB LED with every colour mapped individually,
it's useful to have a different colour for link on vs link off,
particularly in the case where the LED has multiple meanings
(i.e. it's a generic status/power LED as well, so shouldn't just be
turned off in the absence of a link).
This invert code is largely copied from similar code
in other triggers which already support invert.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
There's a bug in drivers/dma-buf/heaps/Makefile or /driver/dma-buf/Makefile
that doesn't allow heaps source files to get compiled.
we raised an issue in openwrt:
https://github.com/openwrt/openwrt/issues/13887
Approved-by: Arien Judge
Approved-by: James Haggerty
libcamera requires a number of v4l2 modules without packages
in OpenWrt.
Additionally, add support for the raspberry pi camera variants
APP-2145, APP-2097, APP-2003, APP-2197
Approved-by: James Haggerty
Approved-by: Matthew Forgie
Approved-by: Evan Benn
