12:00 | rabeeh | XBMC frodo running on GeexBox |
12:16 | jnettlet | rabeeh, excellent!!! |
12:23 | Kiranos | rabeeh: http://www.solid-run.com/mw/index.php/XBMC_on_CuBox |
12:23 | Kiranos | sorry wrong url |
12:23 | Kiranos | http://wiki.xbmc.org/index.php?title=CuBox |
12:23 | Kiranos | you should update this somewhat |
12:23 | Kiranos | what is working and what is left to do might be outdated? |
12:33 | rabeeh | right |
17:15 | N30N | cryptodev support and xbmc-cubox-git now merged for arch :) |
17:18 | Coolgeek | core/linux-cubox 3.5.3-1 -> 3.5.7-3 <== hummm, time to update :p |
17:21 | N30N | Coolgeek: it'll be 3.5.7-4, the build system still compileing should hit the repos soon |
17:21 | Coolgeek | oh, ok |
17:21 | Coolgeek | how much time do it need ? |
17:22 | Coolgeek | N30N: combien de temps avant qu'il arrive dans le repo ? :p |
17:22 | N30N | your guess is as good as mine (I don't know what hardware they use). |
17:22 | rabeeh | i think we are wasting lots of time just maintaining off mainline trees |
17:23 | Coolgeek | how it will be good tomorow morning |
17:23 | Coolgeek | rabeeh: what about merging with the official one ? |
17:24 | rabeeh | Coolgeek: shesselba_ is the only one who started doing that; and actually has all the bits in place (including device tree which is a show stopped if we didn't have) |
17:24 | rabeeh | i think that the NXP HDMI TX and GPU drivers won't ever go mainline; but the rest should be. |
17:25 | rabeeh | besides that we started discussions with NXP to get a fully GPL compliant driver; but still no responses |
17:25 | Coolgeek | they are both closed sources ? |
17:29 | rabeeh | NXP is open source; but the licensing agreement is clumsy |
17:29 | rabeeh | (needs to be sorted out). |
17:29 | rabeeh | the GPU kernel part is open source; but I doubt it can be upstreamed. |
17:32 | jnettlet | rabeeh, I think if you strip the HDCP support out of the NXP driver you should be able to upstream it. |
17:33 | jnettlet | although I may be able to write a much simpler version of it that is more acceptable upstream based on the HDMI driver I just wrote for the MMP2/3 |
17:33 | jnettlet | it all depends how much hardware we are going to support with it. |
17:34 | jnettlet | I also need to track down RMK and see what the status of his work is. |
17:34 | rabeeh | jnettlet: that driver doesn't even the HDCP part |
17:34 | jnettlet | rabeeh, it doesn't? I thought I saw hooks for it. |
17:34 | rabeeh | it's really a HAL based driver from NXP that supports lots of NXP devices; written in a crappy way |
17:34 | jnettlet | yeah, much like galcore :-( |
17:35 | jnettlet | all the registers are there, so it should be simple work to write my own simplified version. |
17:36 | jnettlet | but I am only doing video/audio...have no plans for hdcp, cec, or hdmi ethernet any time soon |
21:47 | N30N | hhhmm… PPSSPP might become a good gaming option for the cubox. Think it'll be able to cope? |
21:50 | dotarray | oh, wow. |
21:50 | dotarray | that is rather interesting. |
21:59 | dotarray | ppsspp people not so helpful when it comes to detailing hardware requirements :) |
22:01 | N30N | dotarray: It's a new project. We'll need to wait till the ARM JIT compiler is added/finished. |
22:04 | dotarray | yep :) |
22:04 | N30N | They have Raspberry Pi marked as possible, so there's hope :) |
22:15 | dotarray | i might have a chat to them :) |
22:18 | dbsx | has anyone tried the Kaiser Baas BT-130 Bluetooth keyboard? |
22:32 | N30N | dbsx: you considered the RC11? http://www.measy.com.cn/product/showproduct48_en.htm |
22:32 | N30N | I've not used either |
22:46 | dbsx | The RC11 is not my sort of kbd. Thanks for the link |
23:40 | rmull | On my cubox, if I leave it completely idle, the output of 'uptime' always reports 0.00, 0.01, 0.05. Why is there always 0.01 and 0.05 in the 5 and 15min load averages, no matter what? |
23:40 | rmull | This is after days of idling |
23:40 | rmull | I can run uptime days apart and get the same thing |