<toxicpsion>
yea... it's logcat.. not dmesg... original android and all.... i'll hafta dig for it.
<toxicpsion>
pastebin ok for ya?
<toxicpsion>
drachensun: ^^
<drachensun>
you can get a dmesg log in android also
<drachensun>
pastebin is fine
<toxicpsion>
ya.. it's just not totally handy... my net's kinda saturated atm too.... cloning some git:P
<drachensun>
I'm suprised the built in camera app didn't work. I've seen a lot of these chinese tablets where only the stock app would be able to use a feature but in that case there almost alwasy is a stock app that can do it.
<toxicpsion>
ya.... it works fine for the front camera, and crashed the minute i changed to the rear camera /w VIDIOC_S_INPUT error, now whenever i start the camera app, it immediately crashes with no gui... Device or resource busy. lsof says it's mediaserver holding /dev/video0
<toxicpsion>
it's a neat little tablet... the only one i've found with a vibe motor in it... tactile feedback and IPS... now just the stupid rear cam :(
itamarjp has quit [Remote host closed the connection]
itamar_ has quit [Read error: Connection reset by peer]
ibot has joined #arm-netbook
<drachensun>
that does looks like a driver mismatch
<drachensun>
this is a whole list of camera drivers in the sun4i_csi/driver directory
<drachensun>
yours might just one of the others
<toxicpsion>
yea... i think they mighta been in a hurry :|
<toxicpsion>
change the reference in script.fex csi0 & kernel should try different .ko right?
<drachensun>
I haven't had to mess with it but that sounds right
<drachensun>
and make you have the actual driver loaded of course
<drachensun>
I'm not really sure how to figure out what you actually have though
<toxicpsion>
it should automatically insmod based on the script parser i think.
<drachensun>
we usually figure out it by looking at what Android does :/
<toxicpsion>
and of course android does it wrong this time.
<drachensun>
well I'm off, good luck, let us know what you find out
<toxicpsion>
trial and error :P i'll keep you poseted... conpiling a bunch of script.bin..... i'll keep you posted.
<toxicpsion>
stupid typo. :P
sv has joined #arm-netbook
sv has joined #arm-netbook
sv has quit [Changing host]
aholler has joined #arm-netbook
XenGi is now known as XenGi_
aholler_ has quit [Ping timeout: 244 seconds]
Jef91 has quit [Remote host closed the connection]
Jef91 has joined #arm-netbook
Quarx has joined #arm-netbook
Quarx has quit []
DrFeelGood has joined #arm-netbook
DrFeelGood has left #arm-netbook ["Leaving"]
servili007 has quit [Quit: Leaving]
gsilvis has quit [Read error: Connection reset by peer]
<mnemoc>
this is the forum-age... if it's not a fancy web service it doesn't work
<mnemoc>
s/service/app/
<ibot>
mnemoc meant: this is the forum-age... if it's not a fancy web app it doesn't work
hg_5 has joined #arm-netbook
<Turl>
$ TZ="UTC-5" date -d "Friday 8 December 2012 13:50 GMT+8"
<Turl>
sáb dic 8 10:50:00 UTC 2012
<Turl>
didn't know date could do that :) you need to learn the correct TZ name though, GMT-5/UTC-5 doesn't seem to work
<Turl>
hm, it does seem to work but it prints UTC instead of UTC+/-X
<aholler>
if you already know the differene in hours, a bit brain should be enough
* Turl
's brain never gets time calculations right
hurtigbuffer is now known as jelly-home
Maqs has quit [Ping timeout: 244 seconds]
Maqs has joined #arm-netbook
drachensun has quit [Remote host closed the connection]
<slapin_>
mnemoc, Turl: don't count me into 'forum-age', I'm old fashioned and do all date calculations in scripts using TZ=Europe/Something date, but a problem is I don't know all the names I need, and TZ=CET and TZ=CEST doesn't actually work for me for unknown reason, while TZ=GMT or TZ=UTC works. I use Europe/Berlin for CET
<slapin_>
actually, time complexity is too big for my tiny brain
<slapin_>
also all these people especially from US calling for skype meeting at 8 not mentioning which time it is, not even adding am or pm, while knowing perfectly well that people they invite are from many places in world.
<jinzo>
what, you mean US is not the center of the world and everything that's happening?
<Turl>
to top it all US has several timezones :)
<slapin_>
jinzo: this is Moscow here, not US, so we have different defaults here.
<jinzo>
slapin_, ofcourse - as do we in Slovenia. I was joking.
<slapin_>
jinzo: but these US managers are too high on the ladder to hear people they are about to listen to.
<slapin_>
jinzo: not that Moscow is too different to US I'd say, both are very ambitious countries.
<jinzo>
but one focuses (for now at least) on internal problems it has aplenty, and the other is exporting their democracy
<slapin_>
Turl: that is also makes me wonder why these managers always act like these - forcing everyone be around their own clock.
<slapin_>
jinzo: I'd say first is focused on making more problems in creative way so people will forget old ones...
<slapin_>
anyway, interesting times we live in....
<slapin_>
hmmmm...
<slapin_>
espetially, everyone is waiting for 21.12.12 hoping that all the troubles will end soon enough...
<slapin_>
seriously, all the tv talks about this on all channels :(
<slapin_>
and nothing is about NAND controller of A1X...
* slapin_
is back to hacking...
<traeak>
irrelevant
<jinzo>
slapin_, priorities eh? :P
<traeak>
as lame as all those people claiming they know when the great tribulation is going to start
<jinzo>
Turl, reading the e-ink display (text) is way better
<jinzo>
than the text on a lcd
<traeak>
i can easily code with that level of refresh rate on a text screen
<jinzo>
traeak, yeah I saw that, but it's in developement
<traeak>
dual head setup, normal monitor for other stuff
<jinzo>
and you cannot readly purchase screens like that.
<traeak>
that's correct that's why i'm pissed
<jinzo>
at least you couldn't half a year ago.
<traeak>
let me find a video of a kindle doing exactly the same
<jinzo>
and I didn't check since.
<traeak>
ie: it's doable with today's eink, it's just they don't make large screens...why not?
<jinzo>
fabrication and overall technological problems.
<jinzo>
it's not trivial scaling stuff like that up
<jinzo>
and I think we'll first get bigger OLED displays than bigger e-ink displays
<RaYmAn>
there are a few 10" eink ereaders, but thye are stupidly expensive (comparatively)
<traeak>
just sit and wait for some passive screen technology
<jinzo>
yes - it was quite interesting when you could buy a 23" lcd ips for half the price of a 24" lcd ips - just because the technology could produce 23" panels cheaper
<Turl>
traeak: if you want it for coding you might want to wait a bit for color eink
<Turl>
shouldn't be too far away
<jinzo>
"a bit" :D
<Turl>
I saw a video of it
<jinzo>
for example - look at imx6, and it's a SoC
<jinzo>
a year or so has passed, and people still have troubles buying the quad core version
<Turl>
I bet amazon, b&n and kobo will be picking it up soon
<jinzo>
amazon probably
<hno>
Turl, Yes, the color e-ink technology is there, but it does not really meet any significant demand in current shape so not being produced.
<jinzo>
they're the only company in that space that can drive souch a technology forward (as has Apple with unibody designs, flat cells etc.)
<traeak>
only so much you can do with a tiny screen
<traeak>
and yes it would probaby take an apple like company to push this sadly
<Turl>
their not-backlit backlight is pretty good I heard
<traeak>
manufacturers don't like to change, it costs money to retool
<hno>
But saw some interesting article about a mobile phone with e-ink display on the back. Such application should fit color e-ink nicely.
<jinzo>
as Amazon pushed (and bought up the majority) of e-ink displays.
<jinzo>
YotaPhone from russia.
<traeak>
and that should deal with the biggest problem with phones burning their batteries: the lame display
<Turl>
hno: to show rather static info like notifications and weather?
<hno>
yes.
<traeak>
even time as well
<hno>
anything not requiring multiple fps update.
<traeak>
the only thing holding back higher refresh on eink is that it burns battery for the refresh rate, eink can do acceptable rates but it then loses its advantage
<jinzo>
traeak, again, the currently purchasable e-ink displays cannot do that.
<hno>
jinzo, yes that was the one.
<jinzo>
not even if you feed it the nearest electricity plant. Because if flickers. If you had a e-ink device in hand you know what I mean.
<traeak>
jinzo: the kindle which uses android internally can be overdriven to provide that refresh rate, it's just you burn through a whole book's wortrh of page turns in a few seconds
<Turl>
jinzo: the flicker is a software trick
<Turl>
you can disable it but you'd get considerable ghosting
<jinzo>
so, you can disable it but then it... doesen't work.?
<Turl>
it works
<Turl>
just grab a kindle or anything
<Turl>
and move a few pages
<Turl>
and if you look closely you'll see faint marks of the previous pages text
<jinzo>
ah I give up. Like I said - e-ink has some tech in the newer displays (latest gen) that allows changing a portion of the screen
itamarjp has quit [Ping timeout: 252 seconds]
<jinzo>
but when I tried the friends latest-1 gen it still flickered
<jinzo>
as it did when we worked on the e-ink displays.
<traeak>
looks like worst case for eink is 4fps, worse case
<traeak>
highest rate ~20fps
<traeak>
anyways totally moot since it's not there, sry
<traeak>
jinzo: what type of chip waas driving that eink display internally?
<jinzo>
epson one, don't know exactly which one - it was based around a 5" e-ink display, that was driven by some epson e-ink driver and ARM cortex-M3 processor.
<jinzo>
actually 6"
voronaam has joined #arm-netbook
<jinzo>
b/g/n wifi, and touchscreen ofcourse
<jinzo>
the battery life was advertised from 3 to 9 months
<jinzo>
but yes... :D
<jinzo>
(and no on/off switch)
<jinzo>
on the other hand, I see they're expecting color displays in Q1 2012
<jinzo>
*2013
<jinzo>
ofcourse :/
<jinzo>
so they're probably allready working on a prototype with them
rz2k has joined #arm-netbook
lkcl__ has joined #arm-netbook
lkcl_ has quit [Ping timeout: 250 seconds]
lkcl__ has quit [Ping timeout: 246 seconds]
lkcl__ has joined #arm-netbook
<steev_>
woo, new device arrived, supposed to be compatible with an mk802
Turl has quit [Excess Flood]
Turl has joined #arm-netbook
Turl has quit [Changing host]
Turl has joined #arm-netbook
<rz2k>
new mali400 stuff released r3p2-01rel0 - [13 December 2012]
<rz2k>
xenoxaos: you've checked what are the changes? I see xf86-video-mali getting new xorg config...
hurtigbuffer is now known as jelly-home
<xenoxaos>
i dunno
aholler has quit [Quit: 3.7.1]
gzamboni has joined #arm-netbook
aholler has joined #arm-netbook
<traeak>
there's an irc for the a10 soc ?
freakazoid0223 has joined #arm-netbook
gzamboni has quit [Ping timeout: 255 seconds]
rz2k has quit []
RITRedbeard has joined #arm-netbook
Jef91 has joined #arm-netbook
<libv>
hrm, g_ether is surprisingly unstable
<libv>
i constantly am losing ip addresses :(
<libv>
oh. what is NetworkManager running on this hw for.
<steev_>
cuz NM is awesome
<mnemoc>
it should be integrated into systemd
<libv>
of course it is.
<libv>
it all is mashed together
<libv>
and when one thing goes wrong, you're f-ed
<mnemoc>
it's perfect, like pulseaudio, if something goes wrong it's user's fault
<libv>
i was at SuSE when they introduced pulseaudio
<libv>
people were still whining about all the issues nm were causing
<libv>
i am happy to no longer be too near to the device enablement people there now that they are doing systemd
<libv>
what am i doing for new years again, oh wait, hearing about this same old shit again :)
<libv>
and how people fall for it every time :)
<mnemoc>
at least they haven't rewritten it in C# yet
<libv>
but... it could just be that the sunxi ucd driver is not too stable
<libv>
mnemoc: that will not happen
<libv>
although, it might
<libv>
now that the usual gnomies are no longer part of redhats biggest enemy
<libv>
give it a few years, the bashing will shift from the long conquered enemy novell, to a new one (canonical?)
<libv>
and given time, the bashing of mono will become less and less
<libv>
and then...
<libv>
oh yeah, with nm disabled, it seems to hold its ip longer now
<specing>
I like wicd
<specing>
well "like"
<libv>
the thing is, all of these bits and bobs are always going to cause trouble, there is no two ways about it
<specing>
made it to ignore eth0 once
<specing>
was *very* happy
<libv>
but the way this is being done is not nice
<libv>
loads of noise, and then the noisemaker runs off to break something else, and everyone else gets to pick up the pieces
<libv>
by which time, those others are forced to use those bits that so much noise was made about
<specing>
libv: where do you work now?
<libv>
specing: until 2 months ago, codethink, now german unemployment office, until i have delivered upon lima a bit.
<libv>
specing: why?
<specing>
just wondering
<libv>
"just"?
<specing>
"just".
<mnemoc>
so lima became state funded :p
<libv>
mnemoc: mostly libv funded.
<libv>
as it always has been
<libv>
specing: i do not by the just in anyway
<libv>
specing: what were you trying to imply?
<libv>
specing: because i can interprete your question in many directions
<mnemoc>
libv: leaving games and cubes aside, can one use current lima to write a simple GL-based HMI app?
<mnemoc>
on A10
<libv>
nope
<mnemoc>
ok
<libv>
we still have not left the research phase
<libv>
and there is no gl, there is something resembling gl (because thats how these things end up looking like) which runs on much barer infrastructure
<mnemoc>
i had the idea you already had a basic set of gl calls REed
<libv>
some, yes
<libv>
but you do not get a full fledged gl implementation that way
<libv>
you get some limare calls which somewhat amount to the same thing hw wise
<libv>
i am figuring out how the hw works and how it all fits together, i am not reimplementing a whole opengles stack
<libv>
that's what we will use mesa for in future
<mnemoc>
:)
<mnemoc>
sounds fair
<libv>
with nm disabled, g_ether does seem to work reliably