premoboss has quit [Remote host closed the connection]
RayFlower has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
cristian_c has joined #linux-rockchip
wildea01 has joined #linux-rockchip
<rperier>
that's really frustrating... I hesitate between a radxa rock 2 and a chromebook (rockchip-based of course).... my heart says... an open hardware... but I am still hesitating because both of them seems really nice
<rperier>
:/
<rperier>
at the same time, I already have a rk3288-based device (my firefly), so I might wait for the first rk3368 board (in few months) instead...
<rperier>
arrrff ^^
gb_master has joined #linux-rockchip
<mmind00>
rperier: :-D
<mmind00>
rperier: the Chromebook of course has a better value in terms of usability ... I don't think the firefly vs. Rock2 matter that much in terms of what you can do with it ;-)
<rperier>
yes, that's a good point, I agree
<gb_master>
rperier: did you find something new about the rk3188 eth loss-of-packets/kernel-panics?
<rperier>
I don't compute something... these chromebook are available publically ? I only able to find them on google US website :/
<mmind00>
rperier: yeah from what I've seen, they're really us-only at the moment
<rperier>
gb_master: sorry, I am just back to kernel development right now (two days ago and I focused on rk3288), I was really busy (personnal needs). No I did not look at it, however that's really boring, I will try to find a solution if I have time . Do you know if the clock issue fixed in rk3188/rk3066 bootloaders changed something ?
<gb_master>
rperier: U-Boot or standard one?
<rperier>
it was u-boot if I remember correctly
<gb_master>
rperier: I don't use u-boot (yet)
<gb_master>
rperier: I might try, anyway, to migrate to u-boot and see what happens
<gb_master>
rperier: but I guess that the standard bootloader is fine, so we shouldn't have had that bug
<rperier>
mmind00: which model is the "pinky" exactly ? asus ?
<rperier>
this one looks very nice
<mmind00>
rperier: nope ... pinky (the black/white one) is an intermediate development model ... and from what I've gathered a nearly extinct species [it seems I'm caring for the last one :-) ]
<mmind00>
rperier: jerry is the Hisense Chromebook ... and this is really nice in terms of build and design
<rperier>
I will look for hardware tests in order to compare them (on omgchrome or youtube or something)
gb_master has quit [Ping timeout: 246 seconds]
cristian_c has quit [Quit: Sto andando via]
field^Mop has joined #linux-rockchip
tizbac has quit [Ping timeout: 265 seconds]
tizbac has joined #linux-rockchip
naobsd has joined #linux-rockchip
tizbac has quit [Ping timeout: 265 seconds]
tizbac has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
<rperier>
mmind00: is it good about power management ?
<rperier>
I mean, with real usecases and inside a laptop
<rperier>
I think that you have convinced me :p
<mmind00>
rperier: you mean the Chromebook? The runtime estimates on the shop site seem quite nice and also seem to match real world use-cases. Of course when running a _mainline kernel_ on it, it is still lacking some of the more esotheric powersaving measures, that haven't made it from the Chomeos kernel yet
markm_ has joined #linux-rockchip
markm has quit [Ping timeout: 245 seconds]
tizbac has quit [Ping timeout: 256 seconds]
tizbac has joined #linux-rockchip
GGflags has quit [Read error: Connection reset by peer]
GGflags has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
Astralix is now known as Astralix|away
arokux1 has joined #linux-rockchip
field^Mop has quit [Ping timeout: 252 seconds]
arokux has quit [*.net *.split]
GriefNorth has quit [Quit: Konversation terminated!]