add support for medaka Casio Pro Trek Smart WSD-F21hr
#165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
the defconfig misbehaves with regards to USB features, so the defconfig is currently the .config pulled from a working kernel build
added a custom android tarball built for a generic aosp_arm64 target. This is really not device-specific, but it's going here until it's confirmed working.
libhybris is currently failing to select the correct architecture at the configure stage, so it tries to build some arm 32bit specific code and fails. Further investigation is needed because this workaround should not be necessary.
previously, this would cause medaka's init to get stuck with uevent-related errors
the system dir actually contains the boot ramdisk, which means that the partition must be remounted from there. this is accomplished by the machine-specific init script.
it was discovered that all the android binaries are, in fact, 32 bit. This forces us to use a 32 bit userspace. as of now, lib32-asteroid-image must be built instead of asteroid-image. this will hopefully change in the future, but I'm not sure how this should work at the moment
This reverts commit bbf901d.
ngfd dependency was already added in the recipe this was based on
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the successor to
ayu, the Casio WSD-F20. Compared to that, this watch adds a heartrate sensor, with a different segment LCD and slight differences in styling - overall, the two look very similar and even use the same primary display panel, but they are internally based on completely different platforms, with this one running the 64 bit Exynos 7270.This port is not ready to merge for 2 reasons:
Firstly, the commit history is a total mess, since I removed and re-added a lot of beluga base in various commits. I'm not sure if it's worth slightly cleaning up but keeping all these changes, so that they act as a good log of the porting process, or if it's worth completely reworking the git history into something that would seem to be a more logical progression.
Secondly, the port currently uses a gross multilib hack to build a 64 bit kernel with a 32 bit userspace, which is necessary because all the android libraries are 32 bit. The multilib hack (from my minimal research) is the most correct solution for our build system, but it means that
lib32-must be prepended to any package name that is build - ie.lib32-asteroid-imageinstead ofasteroid-imageand all packages come out aslib32-[packagename]as well, such aslib32-lcd-tools_+git.....ipk. This isn't ideal, but I'm not sure how best to fix it.What works:
What doesn't work:
Untested:
Flashing requires identical disassembly steps to
ayu.it also seems like this port could be mostly shared for the WSD-F30, whenever one of us is lucky enough to get one of those rare and expensive watches in hand