<vagrantc>
paulk-collins: many thanks for that work!
<paulk-collins>
(linux branch also builds the kernel)
<paulk-collins>
cheers!
<vagrantc>
i've managed to get all or most of the mainlined kernel features enabled in Debian's kernels
<paulk-collins>
vagrantc, and upcoming rk3399 chromebooks look very exciting too
<paulk-collins>
vagrantc, nice!
<vagrantc>
paulk-collins: curious if there's any sort of hardware information list dumps we could diff between the working and non-working speedys
<paulk-collins>
vagrantc, not sure, but we can always ask the cros team
<paulk-collins>
if looking at the cros kernel is not enough
paulk-collins has left #linux-rockchip ["Leaving"]
paulk-collins has joined #linux-rockchip
lorenzo64 has quit [Read error: Connection reset by peer]
<paulk-collins>
vagrantc, I'm seeing serious USB issues with ath9k_htc btw
<vagrantc>
haven't had much luck with that either
<vagrantc>
the built-in one with binary blobs works okish, but refuses to stop running somehow and crashes the machine on shutdown/reboot
<vagrantc>
yay binary blobs
<mmind00>
vagrantc paulk-collins: you could maybe check the 4.4 chromeos tree ... they did some veyron-work there in the past too, maybe that gives us a hint what we might be missing
<paulk-collins>
mmind00, ah interesting!
<paulk-collins>
mmind00, still, I'd be looking at 3.14 for a start
<paulk-collins>
bbl
<mmind00>
paulk-collins: yes, that as well ... I don't have a speedy device, so won't be of help here
<vagrantc>
4.4.x is recent enough to consider looking at ... but i have an aversion to ancient vendor trees
<vagrantc>
the speedy with mainline is currently useable enough to be taunting
<mmind00>
vagrantc: I'm currently not sure, if I'm keeping your tuning-disabling patch ... it really only seems to help on your device, makes paulk-collins less functional (as it was working sometimes there) and makes rperier 's device just slow when accessing the emmc
<mmind00>
vagrantc: so from that small sample-set it's definitly not possible to extrapolate if it will help or hinder speedy devices in general
<vagrantc>
mmind00: yeah, i understand
<paulk-collins>
mmind00, vagrantc, maybe I'll try to dig in the cros code and ask around later this week then
<vagrantc>
paulk-collins: i presume you were also using libreboot? :)
<paulk-collins>
vagrantc, well, a more recent build of coreboot
<paulk-collins>
vagrantc, but I doubt it does anything with emmc
<paulk-collins>
I'm usually loading the kernel and rootfs either for the microsd card or usb
<paulk-collins>
from
<vagrantc>
as the u-boot maintainer in debian, i've often been surprised by what the bootloader can impact
<paulk-collins>
right
<paulk-collins>
vagrantc, anyway, the same bootloader with chromeos-3.14 works reliably
<vagrantc>
right
<vagrantc>
i think i was using kali linu's 3.14 build for some of my early testing, and never had a problem with it
<paulk-collins>
makes sense
<vagrantc>
and really, that patch makes it go from a behavior that sounds similar to what you were experiencing to *always* working on my board
<vagrantc>
which, i can write up a hook to patch the .dts on the fly for my usecase if it doesn't get fixed in mainline... annoying though that may be
<paulk-collins>
vagrantc, there must be a proper solution :)
<paulk-collins>
vagrantc, I'm willing to find it, just lack the time right now
* vagrantc
lacks too much savvy to dig too deep, but is happy to test things
tlwoerner__ has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 252 seconds]
afaerber has quit [Quit: Ex-Chat]
paulk-collins has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
dr1337 has joined #linux-rockchip
nighty has quit [Remote host closed the connection]