With the release of the MM8108 USB dongles included with the EKH19, the
Morse Micro OpenWrt SDK now supports many targets - including devices
we don't manufacture.
Add Morse Micro evaluation kits as explicit targets in the README, and
point at the boards folder for other options.
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
This handles the situation where there are no ethernet ports on the bridge
and we want our wifi STA interface to have the MAC address of the bridge
so we can link assoclists with IPs.
Approved-by: Andrew Dodd
Approved-by: Evan Benn
The cgi-upload script (part of cgi-io) doesn't send any responses
while the upload is happening, only when it's finished.
Ideally this should be re-architected to stream 'something', but
for now, the simple option is just to bump the timeout here.
At 1Mbps, this means we should just be able to upload a 30MiB firmware
image within the timeout.
Approved-by: Sophronia Koilpillai
Approved-by: Prabha Murugesan
iwinfo will now ask the driver (i.e. BCF/OTP) for the countrylist,
and use the 1.16 morse driver channel list.
Approved-by: Sophronia Koilpillai
Approved-by: Andrew Dodd
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
I think these will all have enough space for this. At least ekh19
has a 256mb flash, so it's not at all constrained.
Approved-by: Sophronia Koilpillai
Approved-by: Andrew Dodd
Aside from it being a bit weird (why do we want this firmware on non
mm6108 devices?), this meant that if you didn't select a normal
firmware (e.g. mm6108/mm8108) the driver would still be included
since the tlm firmware would be there. This is confusing for
users of our fork bringing up new devices.
Approved-by: Arien Judge
Approved-by: Evan Benn
There are two downsides to all kmods:
- they increase build times when you're switching kernels
- you sometimes find odd dependency issues in upstream
which you don't want to fix
This change makes the minimal (-m) build config not use
ENABLE_ALL_KMODS. i.e. the defaults are the same, but using
'-m' the build time is significantly decreased.
We also amend the config application code so that
it's possible to override (almost) anything in
target_diffconfig.
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
Useful for qemu virtualisation, including big endian testing.
Unfortunately, USB interface seems unstable (maybe to do with quality of PCI virtualisation?).
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
This is particularly useful for qemu virtualisation
(but could also be used on any standard x86 system).
Approved-by: Sophronia Koilpillai
Approved-by: Evan Benn
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
When 2000 stations are connected the iwinfo assoclist command returns
a large amount of data. Use the head for the buffer in the rpcd iwinfo plugin,
the buffer is increased in a separate iwinfo patch.
Also increase the ubus max message size. 2000 stations sends a ~1.7MB
json message. This patch does not work for 8000 stations, which will
likely require a more well thought out fix.
Approved-by: James Haggerty
Approved-by: Lyall Beveridge
dpp-qrcode-key combines dpp-key-recovery (private key) with the
qrcode generation (i.e. public key + mac address, previously
in netifd-morse).
Approved-by: Milad Mohtashamirad
Approved-by: Lyall Beveridge
