<wolfy>
mnemoc: I know. I spent two weeks compiling it in 1996
* Wizzup
sighs
<wolfy>
it's nice to learn
<Wizzup>
It's also nice for any kind of customisation or hardening of the system
TheSeven has joined #cubieboard
<Wizzup>
I only use pre-compiled (by myself) packages on my cubieboard
<Wizzup>
Done on quad core arm machines
<Wizzup>
Takes little time, and it gives me customisations my work requires
<aynam>
mnemoc: thx
wickwire has joined #cubieboard
<wolfy>
Wizzup: what systems / manufacturers are your quad cores ? I am shopping for some...
<swabbles>
wolfy: ODROID U2.
<wolfy>
swabbles: i have received an X2 2 weeks ago. DOA.
<Wizzup>
U3 would be better now
<wolfy>
i have to ship it back next week, waiting for new year's vacation to end
<Wizzup>
and I also have an IFC6410, but those are somewhat expensive
<wolfy>
Wizzup: yeah, I am looking at those.
<wolfy>
(u3)
<Wizzup>
What are you planning to use it for?
<wolfy>
multi-party video conferencing. one stream out , several in
<wolfy>
cubie2 is at limits, it kind of chokes
<Wizzup>
ach so
<Wizzup>
Well, the U2 is good, I haven't got it do to do accelerated video playback or even accelerated video scaling
<Wizzup>
but I never tried hard
<Wizzup>
:)
<wolfy>
i have on my todo list to keep optimizing the video playback, but i do not have the device handy anymore, I shipped it to a remote office out of country and the local guy who is in charge with putting hardware in place is . well.. "busy".
AdvancedNewbie has joined #cubieboard
Baronawesome has quit [Ping timeout: 246 seconds]
<Wizzup>
cubie does accelerated video playback quite well though?
<wolfy>
if you manage to use the GPU...
Baronawesome has joined #cubieboard
bizarro_1 has joined #cubieboard
<swabbles>
wolfy: /s/GPU/VPU/
<Wizzup>
wolfy: I've seen it work with mostly? foss parts
<Wizzup>
mplayer+vdpau
<wolfy>
i tried the patched vlc, as described in the wiki. it crashed big timr
<agath_at_work>
Is there anyone successfully using the watchdog under linux on the Cubieboard2 ?
<n01>
agath_at_work: kernel?
Ti_WB1110 has joined #cubieboard
wickwire has joined #cubieboard
weltall has quit [Read error: Operation timed out]
Baronawesome has quit [Ping timeout: 246 seconds]
Baronawesome has joined #cubieboard
shineworld has joined #cubieboard
ganbold_ has quit [Ping timeout: 264 seconds]
AndrevS has joined #cubieboard
gzamboni has quit [Ping timeout: 246 seconds]
zn414 has joined #cubieboard
smccarthy has joined #cubieboard
<rneese_>
what bluetooth adapters are supported on the cubie2android build
initbrain has quit [Changing host]
initbrain has joined #cubieboard
<agath_at_work>
actually I am using Arch Linux with a 3.3.0
<agath_at_work>
but I tried also the 3.4 version (compiled manually) without success.
gzamboni has joined #cubieboard
<agath_at_work>
I read that there is support of the Allwinner A20 in the 3.12 version... since compiling it from scratch on the cubieboard takes a lot of time, I wanted to know if someone already managed to try it with positive results...
Ti_WB1110 has quit [Quit: Nettalk6 - www.ntalk.de]
<n01>
agath_at_work: I wrote the wdt driver for 3.12 so yes, it works on mainline
<n01>
afaict should work also on linux-sunxi kernel
<n01>
agath_at_work: what's your problem on 3.4 with wdt?
Baronawesome has quit [Ping timeout: 272 seconds]
<agath_at_work>
the problem is that the watchdog gets armed, but it seems it doesn't receive "kicks" and after 20 seconds the cubieboard reboots
<agath_at_work>
I tried by using the systemd integrated watchdog feature, with watchdogd and by opening /dev/watchdog manually...
Baronawesome has joined #cubieboard
<agath_at_work>
is there a kernel configuration (3.12) already available, or should I try to configure everything from scratch?
shineworld has quit [Quit: Leaving]
<n01>
I tested the wdt using the watchdog utility in busybox. give it a try
<n01>
to be honest I never tried the driver of 3.4 so I'm not entirely sure that it works flawlessly
<mnemoc>
fix it :)
<n01>
mnemoc: lol ... I'm not a linux-sunxi guy ;))
<n01>
jooookiiiinggg
<mnemoc>
:(
<agath_at_work>
I may try to fix if nobody else already managed to make it work... I just don't want to waste time if someone else already did it....
<n01>
agath_at_work: I wrote the driver for mainline from scratch and it works. I can say nothing about the sunxi kernel
<mnemoc>
mach-sunxi is also part of the sunxi community....
<n01>
mnemoc: don't be picky
<n01>
;)
<agath_at_work>
n01: so you advice to try the mainline kernel?
<n01>
no, mainline is not ready yet for production
wickwire has quit [Ping timeout: 260 seconds]
<n01>
just make the 3.4 driver work
<mnemoc>
n01: talking about "the sunxi kernel" you make it sound as mainlining sunxi is done by a different community
<n01>
nope, sorry for the confusion. for me sunxi-kernel is just !mainline
<mnemoc>
what are sunxi-next and sunxi-devel ?
<n01>
aaargh ...
<mnemoc>
sunxi-3.4 just happens to be today's feature full stable branch
<mnemoc>
anyhow, time to go back home
<agath_at_work>
so, what do I need in order to compile the most recent/stable version with the configuration that supports the A20 SoC and everything is fitted on the CB2? Is there a kernel configuration ready?
<agath_at_work>
I mean.. if I download the sunxi-3.4 do I just need to compile it?
<agath_at_work>
n01: eventually would you give a little support to WarheadsSE? He may package it in the Arch Linux ARM distro...
<n01>
agath_at_work: ask him :)
WarheadsSE has joined #cubieboard
<WarheadsSE>
alright, fine, one more channel added
FR^2 has quit [Quit: Connection reset by peer]
<agath_at_work>
welcome WarheadsSE! I was talking to n01 about an updated kernel for the CB2 (A20)..
<agath_at_work>
n01 if you can give WarheadsSE some support he will update the linux-sunxi package on the ArchLinux ARM...
<n01>
??? me
<n01>
agath_at_work: maybe you misunderstood me
<WarheadsSE>
Is that from the linux-sunxi or mainline you are talking about? Because I need to have all A20 variants covered in that.
<agath_at_work>
what did you mean with "ask him" ? :-)
<WarheadsSE>
Like I said agath_at_work n01 was telling you to ask ME to do it.
<n01>
or do it yourself agath_at_work :)
<WarheadsSE>
connotation reversed.
<n01>
no offense. just I don't have time
<agath_at_work>
ok I will try to do it myself if needed...
<agath_at_work>
n01 no problem maybe I misunderstood a bit...
<agath_at_work>
however WarheadsSE, n01 was saying that 3.12 supports the A20 but it's not ready for production while 3.4 should be the best choice right now.
<WarheadsSE>
Which is what I thought, hence me saying #linux-sunxi
<WarheadsSE>
:P
mifritscher-- has quit [Ping timeout: 240 seconds]
mifritscher-- has joined #cubieboard
ninjak has quit [Quit: Sto andando via]
wickwire has joined #cubieboard
<rneese_>
ok anyone know what bluetooth usb dongles are supported with the cubie android build
<rneese_>
?
<rneese_>
I have tried 3 diff ones and cant get them to work
<rneese_>
I have the 4th on its way a bcm chip
wickwire has quit [Ping timeout: 272 seconds]
smccarthy has quit [Read error: Connection reset by peer]
wickwire has joined #cubieboard
n01 has quit [Ping timeout: 264 seconds]
R430R has quit [Read error: Connection reset by peer]
RA3OR has joined #cubieboard
Eyal__ has quit [Ping timeout: 272 seconds]
mifritscher-- has quit [Ping timeout: 272 seconds]
DEac- has joined #cubieboard
mifritscher-- has joined #cubieboard
Cpt-Oblivious has quit [Quit: ChatZilla 0.9.90.1-rdmsoft [XULRunner 22.0/20130619132145]]
printallthething has joined #cubieboard
_massi_ has quit [Quit: Leaving]
n01 has joined #cubieboard
wooy has quit [Read error: Connection reset by peer]
wooy has joined #cubieboard
wooy is now known as Guest15221
smccarthy has joined #cubieboard
FourthDr has joined #cubieboard
nils2 has joined #cubieboard
nils_2 has quit [Ping timeout: 272 seconds]
nils2 is now known as nils_2
wolfy has quit [Ping timeout: 252 seconds]
nighty^ has quit [Excess Flood]
nighty^ has joined #cubieboard
wickwire has quit [Remote host closed the connection]
ssvb has joined #cubieboard
patuck has left #cubieboard [#cubieboard]
rz2k has joined #cubieboard
Eyal_ has joined #cubieboard
RzR has quit [Read error: Connection reset by peer]