<javier__>
si1v3r: long story, short. No, it's not a bug although I still don't understand how the in-kernel firmware loading is supposed to work for built-in drivers
<javier__>
si1v3r: the problem is that the fw is not available by the time the driver is probed and there is no way to retry after the rootfs has been mounted
<javier__>
si1v3r: one way to get it working is to have the fw in a initramfs
<javier__>
si1v3r: for multi_v7_defconfig, the policy is to build as much as possibl as a module so I enabled all the options needed for the exynos chromebooks
jnettlet has quit [Remote host closed the connection]
jnettlet has joined #linux-exynos
gautam__ has quit [Ping timeout: 240 seconds]
amitk has quit [Quit: leaving]
twitch153 has quit [Ping timeout: 256 seconds]
twitch153 has joined #linux-exynos
zombah has quit [Quit: Leaving]
<si1v3r>
Seems suspend is working now, however resume doesn't quite work. Screen activated but peripherals did not respond.
<Wizzup>
exactly
<Wizzup>
snow?
<si1v3r>
pit
<Wizzup>
same on snow
<Wizzup>
I'm happily using mainline on snow though
<Wizzup>
I just don't suspend :)
<Wizzup>
si1v3r: does your pit power off completely on 'poweroff' or 'shutdown -hP now'?
<si1v3r>
I'm pretty thrilled. Futureproof is good.
<si1v3r>
poweroff works, yes.
<Wizzup>
it works here, but not completely, on snow
<Wizzup>
the keyboard led stays lit and it's not actually powered off until you hold the power button
<si1v3r>
Now I don't know if that actually works to shut down everything, but the light goes off.
<si1v3r>
I would need to test battery drain agains a poweroff and a hard button poweroff.
<si1v3r>
*between
<si1v3r>
I collected all my notes this morning. I've got instructions on partitioning flash media, flashing the correct nvuboot, making a rootfs for several distros and booting
<daniels>
si1v3r: the light is controlled by the EC; if the light is off, the cpu is
<si1v3r>
And the CPU being off means all the other normally off devices are off as well?
<si1v3r>
(Not sure how central power management is)
prahal has quit [Ping timeout: 255 seconds]
<daniels>
more or less - i guess the key point is that if the light is off, the state wrt power is the same as if it were button or not
<daniels>
(when you hold the power button down, the ec walks through the same cycle of pulling the cpu and primary power regulator down as it does when the cpu kindly requests it power off)
<si1v3r>
Ah ok then, sounds good.
afaerber has quit [Quit: Verlassend]
<si1v3r>
super thrilled about how all this is going. These are powerful machines and it's neat to be able to use them freely.
<Wizzup>
my snow also still turns on randomly
<si1v3r>
when closed?
<Wizzup>
when open
<si1v3r>
I never had that happen on my old snow...
<si1v3r>
Seek out a priest.
<Wizzup>
I saw it happen, turned on during 2am at night when I was in bed
<Wizzup>
the light woke me up
<si1v3r>
secret google auto wake up for updates mode?
<Wizzup>
perhaps
<daniels>
that's not triggered by the EC
<si1v3r>
chromebooks really don't like being off
<daniels>
wake-for-update only happens when running actual chromeos, is triggered by the cpu, and also doesn't pull the display up
afaerber has joined #linux-exynos
prahal has joined #linux-exynos
zombah has joined #linux-exynos
liquidAcid has joined #linux-exynos
prahal has quit [Quit: prahal]
afaerber has quit [Read error: Connection timed out]