<ssvb>
calcprgmr1: was fbturbo compiled with libUMP support? are the permissions for /dev/mali, /dev/ump, /dev/dri/card0 set correctly?
<ssvb>
calcprgmr1: is es2info using mali dynamic libraries and not mesa?
<calcprgmr1>
I set the permissions for mali and ump according to the wiki
<calcprgmr1>
es2_info is using mesa I think
<ssvb>
running ldd on es2_info binary will reveal the dynamic libraries that are currently in use
<ssvb>
you will need to remove mesa out of the way
<calcprgmr1>
yeah, /usr/lib/arm-linux-gnueabihf/mesa-egl/libGLESv2.so.2, same for libEGL.so.1
<ssvb>
if you installed something after installing sunxi-mali, this could have overwritten the mali blobs with mesa
<calcprgmr1>
didn't install anything after installing sunxi-mali, but sunxi-mali installer didn't install to that path
<calcprgmr1>
it installed to /usr/lib
<calcprgmr1>
ok, I symlinked the ones from /usr/lib into /usr/lib/arm-linux-gnueabihf/mesa-egl/ and now it's working
bsdfox has quit [Read error: Operation timed out]
nazcafan has quit [Ping timeout: 264 seconds]
Wizzup has joined #linux-sunxi
bsdfox has joined #linux-sunxi
geecko has quit [Remote host closed the connection]
Black_Horseman has quit [Ping timeout: 240 seconds]
<steev>
so, i'm trying to play with this nand stuff from https://www.olimex.com/forum/index.php?topic=2028.0 - anyone happen to know why u-boot would be claiming the uImage is the wrong format for bootm ?
egbert has quit [Ping timeout: 264 seconds]
egbert has joined #linux-sunxi
dlan__ has joined #linux-sunxi
dlan__ has quit [Changing host]
dlan__ has joined #linux-sunxi
dlan__ is now known as dlan^
dlan^ has quit [Client Quit]
dlan__ has joined #linux-sunxi
dlan__ has quit [Client Quit]
pacopad has quit [Ping timeout: 264 seconds]
pacopad has joined #linux-sunxi
memleak has joined #linux-sunxi
<memleak>
hi all!
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
JohnDoe_71Rus has joined #linux-sunxi
memleak has quit [Ping timeout: 244 seconds]
newleaves_ has joined #linux-sunxi
TheSeven has quit [Read error: Operation timed out]
memleak has joined #linux-sunxi
TheSeven has joined #linux-sunxi
bsdfox has quit [Ping timeout: 265 seconds]
<mrnuke>
" EXT4-fs (mmcblk0p3): couldn't mount as ext2 due to feature incompatibilities"
<mrnuke>
with latest sunxi-devel branch. Wondering what I could be doing wrong
bsdfox has joined #linux-sunxi
memleak has quit [Ping timeout: 240 seconds]
memleak has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
<Nyuutwo>
mrnuke: you don't have enabled ext4 filesystem in kernel
<Nyuutwo>
mrnuke: eh, question before, does it boot?
<mrnuke>
Nyuutwo: I have EXT4 enabled, and, no, it does not boot. Lemme collect full output
<Nyuutwo>
mrnuke: so add rootfstype=ext4 to kernelargs
<wens>
vbus from the otg should be connected to the PMIC, to be regulated and avoid drawing too much power
<wens>
that said, the AXP209 even has a proper vbus voltage comparator
<mnemoc>
and it's not properly used in their reference design?
<wens>
well it's connected, just no driver support
<wens>
I'm not sure about their reference design, but I guess it's broken
<ccaione>
wens: I don't have hw otherwise I'd integrated the axp driver :(
<mnemoc>
EE-driven company... no one cares about proper sw support of things :\
<mnemoc>
ccaione: no CB?
<ccaione>
on CB is not connected IIUC
<mnemoc>
doh
<wens>
mnemoc: proper EE-driven would at least provide a proper comparator for the ID pin, and individually controllable pull-ups/downs for the USB data lines
<mnemoc>
(who, according to linkedin, has a degree in english literature)
<ccaione>
wens: my bad, on CB vbus in connected
<ccaione>
I can try to add support for it in v2
selsinork has quit [Ping timeout: 245 seconds]
FreezingCold has joined #linux-sunxi
selsinork has joined #linux-sunxi
FreezingCold has quit [Ping timeout: 244 seconds]
pwhalen has joined #linux-sunxi
pwhalen has joined #linux-sunxi
<wens>
ccaione: even with support, I don't know how to tie it in to the USB phy driver, or musb
selsinork has quit [Ping timeout: 245 seconds]
selsinork has joined #linux-sunxi
leviathanch2 has quit [Ping timeout: 240 seconds]
dpenev has joined #linux-sunxi
<dpenev>
Hello All. I am wondering if A10/A13/A20 SoC supports asynchreneous memory interface (8/16 bit data bus, Address bus, \RD, \WR, \CS etc.) Seems can not find info in the A20 datasheet.
leviathanch2 has joined #linux-sunxi
selsinork has quit [Ping timeout: 245 seconds]
selsinork has joined #linux-sunxi
FreezingCold has joined #linux-sunxi
kivutar has joined #linux-sunxi
FreezingCold has quit [Ping timeout: 265 seconds]
selsinork has quit [Ping timeout: 245 seconds]
selsinork has joined #linux-sunxi
hipboi has joined #linux-sunxi
nove has joined #linux-sunxi
Black_Horseman has quit [Quit: Zwi se logou mou!!!]
hipboi has quit []
hipboi has joined #linux-sunxi
deasy has joined #linux-sunxi
pwhalen has quit [Ping timeout: 265 seconds]
ssvb has quit [Remote host closed the connection]
pwhalen has joined #linux-sunxi
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
ssvb has joined #linux-sunxi
merbanan has quit [Read error: No route to host]
leviathanch2 has quit [Ping timeout: 240 seconds]
shineworld has joined #linux-sunxi
shineworld has left #linux-sunxi [#linux-sunxi]
FDCX_ has joined #linux-sunxi
FDCX_ has quit [Remote host closed the connection]
merbanan has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
<wens>
ccaione: the otg part would be a current regulator for vbus draw, and interrupts/status maps for vbus sensing, a bit like drivers/usb/phy/phy-gpio-vbus-usb.c
<ccaione>
wens: I'll take a look, tnx
<wens>
but I'm not sure a usb phy would be the proper thing to do :/
pacopad_ has joined #linux-sunxi
pacopad has quit [Ping timeout: 240 seconds]
<wens>
if you do do it as usb phy, do it like gpio-vbus, minus touching phy.state, or you'd have to do proper otg state transitions
pacopad_ has quit [Ping timeout: 265 seconds]
deasy has joined #linux-sunxi
pacopad has joined #linux-sunxi
pacopad_ has joined #linux-sunxi
pacopad has quit [Ping timeout: 240 seconds]
pacopad_ is now known as pacopad
pacopad has quit [Ping timeout: 240 seconds]
FreezingCold has joined #linux-sunxi
pacopad has joined #linux-sunxi
pacopad has quit [Ping timeout: 252 seconds]
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
FDCX has quit [Read error: Operation timed out]
jlj has quit [Remote host closed the connection]
printallthething has quit [Read error: No route to host]
_massi_ has quit [Remote host closed the connection]
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
pacopad has joined #linux-sunxi
pacopad_ has quit [Ping timeout: 240 seconds]
pacopad has quit [Ping timeout: 244 seconds]
bertrik has joined #linux-sunxi
pacopad has joined #linux-sunxi
wingrime has joined #linux-sunxi
<wingrime>
wow RPi now have open video decoder
<wingrime>
anyone can explain detals
<RaYmAn>
isn't that oversimplifying it insanely? 1) it doesn't work on RPI yet afaik 2) Did it even include the video decoder? I read it was missing it, though the generic compute stuff can of course do some of it
<RaYmAn>
(not syaing it's not a great thing, it is! but)
<wingrime>
RaYmAn: is bootloader are opened too?
<wingrime>
RaYmAn: Broadcom make VPU opensource and published docs
<mrnuke>
wingrime: they just published docs and reference code. Nothing usable. The community is expected to do the rest of the work. not very polite
<dpenev>
<Turl> no, I mean Intel or Motorolla like parallel asyncroneous memory interface so we have for example 16 bit data bus, for example 20 bits address bus Read and Write strobes and Chip Select etc. It seems this is not supported bu the Allrunner ARM SoC?
<mrnuke>
wingrime: also, this channel is for allwinner devices. RPI is definitely off-topic
<wingrime>
mrnuke: ineed, but , better ask from known people
<wingrime>
*indeed
<mrnuke>
wingrime: I can tell you from experience, that documentation and reference code is hardly half way there. I've worked on some VIA hardware in the past, where I had docs and reference code. It still took me 2 years to initialize their memory controller
<RaYmAn>
I guess that's why they did the 10k bounty =P
<wingrime>
mrnuke: also, I considered get futher detals about how VPU works on RPI and how it different from aw's one
<ssvb>
wingrime: you can go to #raspberrypi-internals
<wingrime>
ssvb: I still not have RPi
<dpenev>
Turl: I was thinking to implement an asyncroneous memory interface on top of GPIO system but I guess this will be relatively slow and as the Linux is not a real time OS I am not sure the timing restriction for the inteface can be acheived easily
<mrnuke>
wingrime: chances are, there's code for aw's VPU somewhere, as AW licenses most of their IP blocks.
<mrnuke>
wingrime: licenses == purchases a license to use them
<wingrime>
ssvb: also, I more interested how RPi VPU works in contrast from AW's
<ssvb>
wingrime: the video decoder in rpi still remains closed
<wingrime>
mrnuke: I't somehow get half of year to get working VPU on AW with opensorce decoder, so isn't dead end
pacopad_ has joined #linux-sunxi
<wingrime>
ssvb: I wonder why community still not do any RE for it, RPi much popular than AW's stuff
pacopad has quit [Ping timeout: 244 seconds]
<ssvb>
wingrime: as I said, go to #raspberrypi-internals and also check their mailing list archives, there is a lot of reverse engineering work going on
<mrnuke>
Huh? allwinner is not a dead end. Progress of sunxi code is light-speeds faster than epi ever was, and these guys don't get any funding
<mrnuke>
s/epi/rpi/
<wingrime>
ssvb: ok ok, I just wonders about news, but I not have RPi, so I not feel any intension to do RE for it
pacopad has joined #linux-sunxi
pacopad_ has quit [Ping timeout: 265 seconds]
<ssvb>
wingrime: there are a few competent people doing the reverse engineering work for Raspberry Pi
<ssvb>
wingrime: and appears that they already had known quite a lot even before the documentation about 3D engine became available
<wingrime>
ssvb: talk to right people will be interested, I agree in that context
<bertrik>
Can I help somehow with the sunxi code? I have an Olimex A10-LIME board.
<ssvb>
wingrime: it is even possible that these guys got so close to figuring everything out that broadcom did not see the reason to keep it secret anymore :)
<wingrime>
ssvb: nevertheless, any news about A80?
fredy has quit [Excess Flood]
<wingrime>
ssvb: wow, VLIW
fredy has joined #linux-sunxi
<ssvb>
wingrime: anyway, rpi is offtopic here and there are surely better places to discuss it
<wingrime>
ssvb: ssvb ok
<ssvb>
wingrime: still it's a bit sad that the rpi reverse engineering folks are going to remain unknown to the general public, with all the credit likely going to broadcom
<wingrime>
ssvb: not like that work style
<nove>
wingrime: A80 has 4K h265 encode/decode, by what says is the press release
<wingrime>
ssvb: my initial inital work with VPU give oppotunity to join others folks, thats impposible for me do all the hell
<wingrime>
nove: it will be interested to get a80 early
<wingrime>
ssvb: so, they limit themself
<ssvb>
wingrime: who?
<wingrime>
ssvb: > reverse engineering folks are going to remain unknown to the general public
<ssvb>
wingrime: this is not their fault, the general public is just mostly ignorant
<wingrime>
ssvb: ahh
<ssvb>
wingrime: and the official raspbery pi foundation is surely distracting attention
<wingrime>
ssvb: our community so different....
<ssvb>
yes, because the official support from allwinner did not exist in the first place, and the sunxi community could fill the void
<wingrime>
ssvb: ... and we not limited single board/soc
<nove>
and Allwinner joined Linaro, as founding member of Linaro Digital Home Group
<nove>
wants more than only tablets, good for us
<wingrime>
nove: not see any benefit for us
<nove>
meaning that future socs, will not only have tablet features
<nove>
like having sata
leviathanch2 has joined #linux-sunxi
dannym has joined #linux-sunxi
FR^2 has quit [Quit: Connection reset by peer]
leviathanch2 has quit [Ping timeout: 265 seconds]
<nove>
bertrik: you have to find yourself in how you can help. Is not for us to tell you what to do.
<bertrik>
I like reverse engineering stuff, is there any reverse engineering work that needs help?
<plaes>
bertrik: cedarX
diego_r has quit [Read error: Operation timed out]
wingrime has quit [Ping timeout: 241 seconds]
<bertrik>
plaes: ok, I'll have a look
<Turl>
dpenev: SPI?
<ssvb>
nove: samsung has been a linaro member since a long time ago, ask libv if he is happy with the quality of their soc support ;)
<nove>
bertrik: yes go ahead, and you can ask me questions about vpu RE
<nove>
ssvb: did you read the press release?
<nove>
"Allwinner has contributed to open source projects since open-sourcing the single-core Allwinner A10's code in 2011. "
<RaYmAn>
contributing is a strong word =P
<nove>
well, if that is the way how Allwinner see us. i think is good, but needs to be more than words
kuldeepdhaka has quit [Read error: Connection reset by peer]
<oliv3r>
having allwinner connect with linaro is amazing, even if it doesn't do anything just yet, it means they are heading the right way
<libv>
Turl: why do you post that link?
<libv>
well, ssvb is right
<libv>
i am not happy with either samsung or linaro
<libv>
if allwinner is serious about linaro and open source, they sure as hell know who they should talk to to a) get proper support b) get the right image to go with it
<libv>
giving us code was a prerequisite to anything, and luckily their customers ended up doing so
<libv>
giving us docs today, and hw today, that's a nice turn-around from where they were two years ago
<libv>
but given that they just joined linaro, they could and should go even further
<libv>
they can actually go and teach samsung and arm a lesson
<libv>
it will not end up breaking the bank
<libv>
but...
<libv>
i fear that it will happen ilke with all other companies that joined linaro
<libv>
there's almost no open source or community people involved
<Turl>
libv: I got an ad from dx, I thought those things were way more expensive
<libv>
i paid like 40 or so for a much bigger device a few years ago, with an external psu
<libv>
pretty crappy and stupid hw, but did the trick for my linuxtag demo
<Turl>
this one is 'no external power required', interestingly
<libv>
yeah, but it remains rather stupid
<oliv3r>
ssvb: mrnuke: in case you missed it (backreading the rpi stuff with wingrime) wingrime helped a lot of the early RE work on the VPU ;) Him and me looked at the blobs as the first ones I guess and did the first wiki RE pages :)
<libv>
you'll get lucky if you get 1024x768 out of it
<Turl>
libv: it says 1080p on the thing :p
<libv>
Turl: there goes the hope of using a projector at a conference :)
<oliv3r>
as to getting A80 early, I think eva may get us some early when they are produced properly
<Turl>
libv: that's about the only use for VGA these days innit? :p
<libv>
Turl: but a pretty important one
<mrnuke>
oliv3r: kudos to you two guys, but my disgust for rpi still stands :p
<libv>
mrnuke: the rpi guys are on the right track
<libv>
mrnuke: and they are the first in the mobile space to throw out docs and sample code
<Turl>
libv: indeed
<libv>
mrnuke: allwinner is not in a similar position as they do not own the vpu or the gpu
<Turl>
libv: rpi is into robile now?
<Turl>
mobile*
<libv>
the chip was originally designed for the mobile space
<mrnuke>
libv: their intentions (rpi guys) are honorable, but their pace is kinda slow. How many years since rpi first came out?
<Turl>
libv: I thought it was for STB usabe
<plaes>
about 2 years?
<Turl>
usage* sigh kbrd
<plaes>
29 February 2012
<ssvb>
mrnuke: ever worked for a big corporation?
<plaes>
:D
<libv>
mrnuke: to put things into perspective: i started workign on lima 3ys ago
<oliv3r>
mrnuke: oh there's plenty of hatred i'm sure :p
<libv>
mrnuke: the rpi REing guys had to first RE the videocore, and start creating a binutils for it
<oliv3r>
mrnuke: but wingrime has been afk for a while so hence me pointing out he's a 'familiar' :)
<libv>
criticizing the rpi foundation is ok, but you have to do it for the right reasons
<libv>
and those reasons have now changed.
<mrnuke>
oliv3r: familiar as in "a demon supposedly attending and obeying a witch, often said to assume the form of an animal."
<libv>
you can criticize them for having made the noise a year and a half ago
<mrnuke>
?
<libv>
and for only now doing the right thing
<mrnuke>
libv: agreed
<oliv3r>
what AW really has to do, is just one thing really
<oliv3r>
ignore GPU and VPU work; 'we' are doing that mostly anyway and they can't
<libv>
you can criticize them for not being fast enough, and for still not having a free bootloader, but they are slowly working towards it
<oliv3r>
they do have a lot of code out there that's crap
<oliv3r>
their engineers should improve that and submit it to mainline and get quality control over it
<libv>
and you can criticize them for their 10k bounty
<libv>
as that will not get a proper useful driver out
<libv>
but the 10k bounty is because of the same reason why they so vastly overplayed their hand a year and a half ago
<libv>
there's sadly still more marketing than content
<libv>
but in light of all of that
<libv>
what they just did was amazing
<mrnuke>
libv: sure, but by the time they'll have a halfway-free path from reset vector to OS the hardware will likely be obsolete, and we'll all be using a160s :p
<libv>
they are the first to release docs and code for a mobile gpu
<oliv3r>
if AW does well; they make us more or less obsolete (besides the VPU work :)
<libv>
mrnuke: how long has the a23 been out?
<libv>
mrnuke: how far have we advanced on that?
<oliv3r>
nothign!
<RaYmAn>
technically speaking rpi foundation didn't release the docs, broadcom did. (i know, ceo works for broadcom, but still.)
<libv>
mrnuke: it takes time.
<oliv3r>
but no dev boards
<libv>
it all takes time
<mrnuke>
libv: are you guys funded?
<oliv3r>
also a lot of us work on our spare time, so little time to do this stuff :(
<libv>
mrnuke: no, but that doesn't change the time factor
<libv>
mrnuke: mobile chip makers are throwing new chips on the market in 6 month cycles
<libv>
nobody can keep up with that
<libv>
plus
<libv>
rpi will live on for years still
<mrnuke>
libv: rpi touts how their success gave them tons of funds and how they donated to other projects.
<libv>
you cannot plainly compare rpi with allwinner based tablets
<libv>
mrnuke: yes, they do
<libv>
mrnuke: but as said, they are probably slightly more noisy than they could be
<libv>
but they also have to be that way
<libv>
because of the rpi community, and because of the mother company
<mrnuke>
and yet, allwinner is more free in many regards than rpi, despite rpi being funded and you guys do this on your free time
<libv>
fact of the matter is: with their slightly too noisy marketing, they did get docs and code out
<libv>
they are first, and they should get massive praise for that
<libv>
everything else is just side-notes.
<libv>
yes, allwinner is free-er
<libv>
still
<libv>
but once rpi has a free bootloader, we've lost that
<libv>
rpi has vendor support
<oliv3r>
the only reason we are still relevant i guess is that a10 and a20 (and a10s/a13) are all the same ip's
<oliv3r>
so small changes needed to support multiple chips
<oliv3r>
if all these chips where completly diff. we'd drown
<libv>
and even if allwinner starts supporting us more directly, it cannot support us for the gpu or the vpu, as it is not allwinners to give out
<ssvb>
libv: they also have a video decoder, which they probably don't want to open because they are selling codec licenses
<mrnuke>
integrated ethernet.Can't beat that vs enet over USB :)
<oliv3r>
ssvb: not so sure about that
<libv>
oliv3r: indeed, that's why we are so late on a23
<mrnuke>
ssvb: yeah, I always though that license selling should raise a dark-red flag
<libv>
ssvb: they will open source parts of it, but they have to tread carefully due to patents
<oliv3r>
ssvb: i think i read once that they only added the h264 bit, but didn't wanna bite the bullit on paying for the other 2 as they weren't gonna be used much
<ssvb>
libv: yes, mpla is rather aggressive
<libv>
the rpi release is properly groundbreaking
<libv>
and we have to praise broadcom and the rpi foundation for it
<libv>
but we also need to be very selective in our praise, as not all is well in rpi land, yet
<oliv3r>
technically; i think they don't have to pay for any licenses, but that's a EU law
<mrnuke>
software patents are of limited innovational benefit, if any
<libv>
mrnuke: you are preaching to the choir here
<mrnuke>
didn't mean to preach, sorry, but I appreciate your approval
<oliv3r>
libv: yeah a23 is a31; which we never had any official docs for
<oliv3r>
nor dev hardware; making it much aharder
dpenev has quit [Quit: Page closed]
<mrnuke>
BTW, any idea on why MMC driver would freeze while tryng to mount root?
<libv>
oliv3r: well, we are that lethargic on it not due to lack of docs, as we have some code
<mrnuke>
on cubieboard with sunxi/sunxi-devel ?
<libv>
dev hardware, could be a point, but i do not feel that this should be so
<libv>
but that's the script.fex->dt story again
merbanan has quit [Ping timeout: 240 seconds]
<oliv3r>
some do have the docs
<libv>
do we really still lack the u-boot code?
<oliv3r>
but there's no dev hardware so it also makes it harder
WarheadsSE has quit [Ping timeout: 241 seconds]
merbanan has joined #linux-sunxi
<oliv3r>
libv: officially, yes
<oliv3r>
but i've had it for almost a year now i guess
<oliv3r>
well the boot0 code i have
<libv>
was it not in the a23 sdk release we got a month or two ago?
<oliv3r>
yeah
<oliv3r>
but on the upside; we should be getting the boot0 code for a23 next week
<libv>
ok
<oliv3r>
and a tablet i get aswell; so i can start working on it again
<libv>
one of those Q88 style tablets, right?
<oliv3r>
no clue; eva is sending me one
<libv>
well, she should actually do what the cubie guys did
<oliv3r>
she asked if there was interest to work on a23
<libv>
and collect some names, emails and addresses and send out at least a dozen
<libv>
(not to me, i already have one sitting idle since half way december)
<oliv3r>
or create oshw for it; i said olimex said they have little interest ast he chip isn't that interesting. but we do care about a23 and wanting to support it; as it will likley look a lot like a70/a60
WarheadsSE has joined #linux-sunxi
<oliv3r>
so we buy random tablets hoping it's a23
<oliv3r>
to which she said 'i send you oen'
<libv>
tsvetan was surprised to learn that it had a mali
<libv>
when i spoke to him last week
<libv>
i am not sure whether that is enough for him to decide to build a device around it
<oliv3r>
and because of that, she oked the release of the a23 usermanual
<libv>
but perhaps if he gets some encouragement from allwinner
<oliv3r>
nah; no sata, no hdmi, no nothing; it's a pure tablet soc
<libv>
yeah, it is nice that they are warming to us like that
<oliv3r>
i think it's a nuttered a31 with the grahpics swapped out in preparetion for a70
<libv>
but allwinner could go much further
<oliv3r>
yeah much
<oliv3r>
but they can start to pick up where we are now
<libv>
and if they really want the community to jump on their ship, they should also talk to tsvetan and get him to make oshw boards
<oliv3r>
aye
<oliv3r>
oh i forgot to mention
<oliv3r>
ivy from marketing wants to know what they could do to setup a support forum
<libv>
nah, forums don't work :)
<libv>
they should hire mnemoc and give him money to run the linux-sunxi server
ega2002 has joined #linux-sunxi
<libv>
it would be the right thing to do, it will gain massive mindshare for allwinner, especially over the likes of samsung and arm
<libv>
and it will mean one less not-so-clued chinese guy that they have to somehow have to prep so he can work with linaro
<mnemoc>
o_O
<nove>
forums are preferred by users, maybe a sunxi forum to gather all board or hardware in one place
<mnemoc>
we have a wiki for that
<mnemoc>
and google knows it
<libv>
well, if the demand for that truly is there, what stops us from doing it on our site?
<libv>
but yeah, i am also not convinced that it is conductive for anything
<ssvb>
there is a reasonably active forum at cubieforums.com
* mnemoc
hasn't seen lawrence at #cubieboard in months
<mnemoc>
almost a year actually
<mnemoc>
(he runs that forum)
<oliv3r>
and I think the idea of regular online meeting between Allwinner engineers and developers sounds good, we can have a try after the establishment of our forum.
<oliv3r>
that's a quote from ivy
<oliv3r>
it's not perfect, but it's a good start at the least
fredy has quit [Excess Flood]
fredy has joined #linux-sunxi
techn_ has quit [Remote host closed the connection]
techn_ has joined #linux-sunxi
deasy has joined #linux-sunxi
<Turl>
oliv3r: AW engineers on irc would be cool
<Turl>
:p
notmart has quit [Quit: notmart terminated!]
<mnemoc>
indeed
tgaz has quit [Ping timeout: 245 seconds]
tgaz has joined #linux-sunxi
<jelly-home>
pardon my ignorance, but... do they write English?
<specing>
didn't hipboi count as one before he jumped ship?
Black_Horseman has joined #linux-sunxi
<jelly-home>
counted him more as an exception
pwhalen has quit [Ping timeout: 240 seconds]
<oliv3r>
Turl: yeah but that might not be acceptable to the managers
<oliv3r>
'what are you doing, irc, your fired!'
rz2k has quit []
<Turl>
oliv3r: :p
shineworld has joined #linux-sunxi
<Turl>
oliv3r: they could replace "it's compiling" with "it's community!" :p
<Turl>
jelly-home: I know for a fact some do
<Turl>
specing: that too
<shineworld>
hi all... after a very long pause time I'm trying to update my CB2 nand and back to work. Unfortunately after LiveSuit 3.05 update seem nothing would to work and when I connect the CB2 and I enter in FEL to begin download I get always error for "Livesuit get device stage failed"
<shineworld>
have you noticed (and solved) that ?
pwhalen has joined #linux-sunxi
pwhalen has quit [Changing host]
pwhalen has joined #linux-sunxi
ega2002 has quit [Quit: Page closed]
shineworld has quit [Quit: Leaving]
<rellla>
jemk: the g2d/layer problem remains if i play a video in mplayer afterwards. so there is something in mem or buffer or anywhere else, which blends over the video layer, even if another program starts. for me this seems to be a disp issue :(
<rellla>
we have to find out, where this bit is missing ...
<nove>
bertrik: if you are up to RE vpu, to avoid duplicate work, please announce what you will do before starting
popolon has joined #linux-sunxi
popolon has joined #linux-sunxi
dannym has quit [Quit: Leaving]
<rellla>
jemk: i can reproduce it. everytime g2d stops working, this message is in the logs: http://paste.debian.net/85154/
<ssvb>
rellla: could it be some sort of a race, caused by several different g2d users trying to do something at once?
<nazcafan>
two newbie questions here: the documentation for the A20 mentions emac as well as gmac, but I only see one ethernet adaptor on my cubietruck and the cubietruck device tree file seems to only describe gmac
<nazcafan>
are emac and gmac optional devices to the a20?