Hi! 👋

Thanks for your contribution.

The currrent state of armv7l in nixpkgs-unstable is being worked on. The glibc upgrade did cause bootstrap issues.

I have another armv7l device I will use to validate cross-compilation can happen. As a goal, the boot image / stage-1 should always be cross-compilable (when Nixpkgs allows it).

It may take a small while for me to come back to this PR. If you think it has been forgotten don't hesitate to ping me.

Anyway, I have added couple notes to the PR as a pre-review.

Got nixpkgs-unstable working, but get this

$ nix-build --argstr device oneplus-bacon -A build.android-bootimg
trace: ************************************
trace: * Evaluating device: oneplus-bacon *
trace: ************************************
trace: Building with crossSystem?: armv7l-linux != x86_64-linux → we are.
trace:     crossSystem: config: armv7l-unknown-linux-gnueabihf
these derivations will be built:
  /nix/store/8wj9mnj96zdxsxfm63p821fp0dqwx0v0-initrd-oneplus-bacon.drv
  /nix/store/4b5r8i5z7hcs8sbfb5yvxhl0q8yw12yb-mobile-nixos_oneplus-bacon_boot.img-armv7l-unknown-linux-gnueabihf.drv
error: path '/nix/store/m6132gqk3awijlm2qd5670w4gxq6hhmr-extra-utils-oneplus-bacon-extra-utils-armv7l-unknown-linux-gnueabihf/bin/sh' is not in the Nix store

I'll (we'll) have to investigate...

This looks like this is an issue with Nix, for now you can work around this by using Nix 2.3.*.

See NixOS/nix#3471

This looks like this is an issue with Nix, for now you can work around this by using Nix 2.3.*.

Thanks.

This allows me to run sucessfully (with current nixpkgs-unstable):

   $ nix-build --argstr device oneplus-bacon -A build.android-recovery
   $ nix-build examples/hello --argstr device oneplus-bacon -A build.default

Still need to figure out why my device screen remains black...

I was able to build example/demo.
But after flashing recovery and system partitions and fastboot boot boot.img the screen remains with "fastboot mode"... BTW I don't know much how to debug this :-/

Hi!

We just had some major~ish changes, at least one affecting new ports. I would heavily suggest rebasing on top of the latest master update.

The main change affecting ports is that we now have required kernel configuration options, which set known good values to a lot of "difficult to guess" options. A simple bin/kernel-normalize-config should be all that is needed.

Hope this helps!

Though uh... This port is a bit old, don't worry if it gets hard to rebase, you could always ping me if you need help going forward.

Hi Samuel,

As the phone has became my main phone again, I can't test it right now but example/hello and example/demo compile.

Heh, no worries, I broadcasted this message to every port :).

Take all the time you need, and even then, there's no rush.

I was able to build example/demo.
But after flashing recovery and system partitions and fastboot boot boot.img the screen remains with "fastboot mode"... BTW I don't know much how to debug this :-/

I reproduced this on the latest version of this branch and I also have no idea where to begin debugging.

$ fastboot boot result
Sending 'boot.img' (13850 KB)                      OKAY [  0.436s]
Booting                                            OKAY [  0.024s]
Finished. Total time: 0.477s

Hi! 👋

I have taken the (not so hard) decision to drop support for vendor-based devices.

I'm closing this PR since it only targets working with vendor-based devices. It is not a judgement of the quality of the changes, but really that I don't think it's healthy to keep hoping they may end-up working fine in that state.

Though, it doesn't mean there's no hope to ever see these devices end-up useful. Far from it. But to see them being useful, work on mainline Linux and other projects will need to happen.

I see hints of mainline stuff being WIP in your PR, so feel free to rework that into a mainline-based device! Either reopen the PR targeting development, or maybe make a new PR, since a lot changed since.

Thank you for your understanding,

(See also: #643)