<thefloweringash[>
thanks! I was looking too closely at nixos/trunk-combined
<sphalerit>
Dezgeg: do you remember what the missing piece was for getting stuff showing on my chromebook's screen, by any chance?
<Dezgeg>
pwm regulators?
<sphalerit>
Yeah that's what I thought, but I'd already added those. But it turns out I'm just an idiot — I was missing rootfstype from the cmdline
<duncan^>
OK if armv7hf is armv7 high-float what is armv7hl
<sphalerite>
hard-float not high
<sphalerite>
hl is hard-float little-endian
<sphalerite>
(hard-float as in there's a hardware FPU, and floating-point operations don't need to be implemented in software)
<sphalerite>
people can't seem to agree on the right names for this stuff.
<duncan^>
Ah yeah, hard-float, whoops.
<clever>
i think the armv6 is soft-float
<clever>
and the raspbian images all have v6softfloat userlands, so it works on both v6 and v7 cpu's
<Dezgeg>
our v6 is hard-float
<clever>
ah, maybe its an optional thing that the cpu vendor can decide on
<Dezgeg>
yes, as it is on v7
<clever>
maybe the original rpi was just recycling a generic cpu that was meant for all the floatpoint work to be done in hw accel, and now that its open to the public, and nda's block that, they decided to add an fpu
<Dezgeg>
I doubt it's much of an effort to add it (assuming your silicon has room), it's just the generic arm vfp instruction set
<clever>
i'm guessing the rpi v6 was trying to squeeze out every cent and didnt need to waste die space on an fpu
<Dezgeg>
they could have done totally without the arm ;)
<clever>
yeah
<clever>
they could have also done without the VC4, they have another chip which is just the QPU + h264 + arm
<duncan^>
but I think the Raspberry Pi people called it armhf