orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
rajivr has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-aarch64
ninjin has quit [Remote host closed the connection]
ninjin has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 246 seconds]
orivej has quit [Ping timeout: 260 seconds]
<samueldr>
I definitely broke my record for bricking a phone
<samueldr>
less than five minutes after unlocking!
<samueldr>
though luckily (or because I'm following my own instructions) I started with making sure the "brick safe" firmware was installed
<samueldr>
though, good news everyone, the "brick safe" firmware does allow unbricking!
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 240 seconds]
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 240 seconds]
cole-h has quit [Quit: Goodbye]
<ashkitten>
samueldr: i bricked my first feature phone within hours of getting it. apparently you can just permanently lock the sim card with those so it can't be unlocked except by the carrier
<ashkitten>
(so, not a traditional kind of brick, but it was essentially a brick)
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
<samueldr>
nice
<samueldr>
though the redmi note 8 pro has a reputation of being easy to brick... I just didn't know how easy it was
<samueldr>
I bricked it another time after
<samueldr>
and if it spooks anyone, it's either specific to this device, or specific to "newer" xiaomi anti-rollback code, which is apparently quite easy to trigger
<samueldr>
it's not a mediatek thing
<samueldr>
and it's not a non-android linux thing either, first time it bricked was before I tried running Mobile NixOS!
bigvalen[m] has quit [*.net *.split]
leonardp has quit [*.net *.split]
marius851000[m] has quit [*.net *.split]
bqy has quit [*.net *.split]
yangm has quit [*.net *.split]
NickHu has quit [*.net *.split]
kai_w has quit [*.net *.split]
ky0ko has quit [*.net *.split]
pkral has quit [Ping timeout: 246 seconds]
pkral has joined #nixos-aarch64
bigvalen[m] has joined #nixos-aarch64
NickHu has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
<samueldr>
nice, since last time I tried, it looks like overrideCC with clang work with cross 🎉
knerten2 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
knerten1 has quit [Ping timeout: 246 seconds]
<jwaksbaum[m]>
Does that mean you can compile for aarch64 on x86 without qemu?
<samueldr>
it's already possible
<samueldr>
now that's a particular compiler that has been fixed
<samueldr>
and it's notable because some android devices' bad bad kernel trees from bad bad OEMs often times end up booting fine only with some compilers
<samueldr>
(though it looks like that's not enough for my device :()
<samueldr>
like, if you take the kernel tree from xiaomi-lavender, it will compile fine with gcc6 or more recent, but it somehow will not boot
<jwaksbaum[m]>
<samueldr "it's already possible"> Woah I did not know that. I will check this out.
<samueldr>
note that there are caveats
<jwaksbaum[m]>
simpson: I guess this is relevant to you too
<samueldr>
cross-compilation is not equivalent to native compilation
<samueldr>
and some parts of Nixpkgs don't deal well with cross-compilation yet/still
<jwaksbaum[m]>
<samueldr "cross-compilation is not equival"> In what sense? Like it won't be the same derivation?
<samueldr>
exactly
<samueldr>
different inputs
<samueldr>
not the same compilers
<samueldr>
and not only that, but it's not executing with the same ambient impurities like the CPU instruction set
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<jwaksbaum[m]>
Oh that's a big oof. Like that makes it, at least the way it sounds on first glance, almost useless if what you have is a bunch of machines and you want them to be able to transparently help each other out building things.
<jwaksbaum[m]>
I guess it's a different use case: compiling for a not nix machine with different architecture
<samueldr>
compiling for a nix machine, with a different architecture, when you can't trivially build natively
<samueldr>
(or quickly)
<samueldr>
it can help if e.g. you have a device for which a forked kernel is required, but you don't have anything to build natively onto