joerg has quit [Read error: Connection reset by peer]
joerg has joined #maemo-leste
System_Error has joined #maemo-leste
<Wizzup>
ok, I think I can make tsc2005 behave
<Wizzup>
but that really will happen after sleep :)
<Wizzup>
I just need to make sure on suspend the irq is disabled, and on resume it is enabled, and that they are balanced
* Wizzup
zzzz
cockroach has quit [Quit: leaving]
Pali has quit [Ping timeout: 268 seconds]
Wikiwide has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
mepy has quit [Ping timeout: 240 seconds]
inky_ has quit [Ping timeout: 268 seconds]
_inky has quit [Ping timeout: 268 seconds]
inky_ has joined #maemo-leste
_inky has joined #maemo-leste
yanu has joined #maemo-leste
<freemangordon>
ugh, triple-buffering that I implemented is incorrect :(
<freemangordon>
I wonder if I can get armsoc dri2 code and implant it in omap driver
mepy has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
mepy has quit [Quit: Leaving]
mepy has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
uvos has joined #maemo-leste
inky_ has quit [Ping timeout: 256 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
zhxt has quit [Ping timeout: 265 seconds]
alex1216 has joined #maemo-leste
<Wizzup>
freemangordon: what is incorrect about it?
<Wizzup>
tmlind: I know it's weekend and all so no rush, but if you have some time could you comment on my tsc2005 patches? With those applied, tsc2005 does not keep the device awake unless the fd is opened (it's fine after probe, and after fd release)
<Wizzup>
I suspect the next step is making it auto idle like you did with the droid4 ts atmel_mxt driver
inky_ has joined #maemo-leste
inky has quit [Remote host closed the connection]
Pali has joined #maemo-leste
<freemangordon>
Wizzup: not sure I can explain, but it is wrong
<freemangordon>
and I guess tearing is because of that, low FPS too
<freemangordon>
it seems I have implemented double-buffering with 3 buffers :)
<Wizzup>
freemangordon: aha
<uvos>
freemangordon: so you wait on the wrong buffer to be free?
<freemangordon>
or rather - do not mark buffer as free when it should be
<freemangordon>
or somesuch, I am not exactly sure what's wrong
System_Error has quit [Ping timeout: 276 seconds]
System_Error has joined #maemo-leste
<Wizzup>
hm looks like CONFIG_TIMER_STATS would be useful but they removed it from kernel
<Wizzup>
tracers are supposed to replace it?
<uvos>
Wizzup: i mean yeah
<uvos>
you can use the tracer to monitor the timer functions and see what callbacks they call
<Wizzup>
It's frustrating to just see delayed_work_timer_fn at the top always in powertop
<uvos>
so its techicly possible to get this information but this seams way way harder than
<uvos>
what CONFIG_TIMER_STATS seams to have been
<Wizzup>
it looks like CONFIG_TIMER_STATS would actually break it down per kernel thread and userspace process
<uvos>
yeah
<Wizzup>
but it broke container namespace whatever
<Wizzup>
blergh...
<Wizzup>
the commit that removes it also doesn't really say how to do it lol
<Wizzup>
'traces replace it'
<Wizzup>
ok
_inky has quit [Ping timeout: 268 seconds]
<Wizzup>
btw I think I fixed the sgx-ddk-um upgrade path again
<uvos>
btw sgx still blocks idle all the time on my d4
<uvos>
no idea why yet
<uvos>
only rmmod helps
<Wizzup>
this is leste?
<uvos>
yeah
<uvos>
its only this one d4
<Wizzup>
maybe try to upgrade to latest kernel and such
<uvos>
really strange
<Wizzup>
hmm interesting
<uvos>
i have
<Wizzup>
I also have some droids that use more power than they should even when not turned on
<Wizzup>
(on lab psu)
<uvos>
ok
<Wizzup>
I had one, now I have two that do that
<uvos>
but its fine with sgx not loaded
<Wizzup>
but idk if that's sgx
<uvos>
so i doubt its that
<Wizzup>
mhm, weird
<Wizzup>
yeah
<uvos>
i should try if it follows the sdcard
<Wizzup>
yes
<Wizzup>
freemangordon: btw I can't get the n900 to behave even with CMA size of 64MB
<Wizzup>
so there might be something else going on
<freemangordon>
Wizzup: hmm?
<freemangordon>
what do you mean?
<Wizzup>
X11 segfaults quite quickly
<freemangordon>
segfaults like?
<Wizzup>
let me check you an error, sec
<freemangordon>
cannot allocate BOs?
<Wizzup>
it's still booting, sec
<Wizzup>
I can usually get it to crash by just starting one or two apps and clicking on a menu
<uvos>
freemangordon: all isent big change from 2 -> 3 was that in 2 glx allocates buffers in the server while in 3 the clients allocate buffers,this subtaly breaks glx and i had to fight this in some sci applications, no idea how this works in egl or any real details
<Wizzup>
it uses omap3 as example
<freemangordon>
uvos: yes, I know the diff between 2 and 3, the point is that i don't know dri2 buffer lifecycle
<uvos>
yeah sorry
<freemangordon>
I'll try to find something over the inet
<uvos>
i know less here then you most likely
<freemangordon>
yeah
<uvos>
but i gues the buffer lifecylce has to be controlled by x
<freemangordon>
could be
<uvos>
it really has to
<freemangordon>
but I need to find some docs on the matter
<Wizzup>
>apt upgrade will upgrade all packages that can be upgraded without the need to install additional packages or remove any conflicting installed packages. Basically it will apply all package upgrades that do not include changed dependencies.
<Wizzup>
uvos: huh why did it do that?
<uvos>
because the old dsme had a bug that caused deamons to crash when reloaded to fast
<Wizzup>
ah
<uvos>
and then dmse helpfully distroys the system by shuting down during apt upgrade
<uvos>
we need new images
<Wizzup>
5.7.y is very unhappy in drm, so this bisect for the modem will be *fun*
<Wizzup>
uvos: yes, I've done my part, parazyd can finish it soon I hope
<uvos>
Wizzup: btw
<uvos>
it would also be very usefull
<uvos>
if we acctually packaged the version of rwmem that the droid4-powermanagement script uses
<uvos>
as it stands
<uvos>
the blockers dont work
<Wizzup>
modem works on v5.7.y at least
<uvos>
because there is no rwmem
<Wizzup>
hm
<Wizzup>
doesn
<Wizzup>
't busybox have that?
<uvos>
it dose
<Wizzup>
but not in debian
<uvos>
but the script dosent sue busybox's rwmem
<Wizzup>
so what do we depend on?
<uvos>
we have to package something
<uvos>
and with the version of rwmem i have it reports everything blocking all the time
<uvos>
because the output is formated slightly different
<uvos>
we should just package whatever version of rwmem tmlind used...
<uvos>
ok i finished upgrading the october image to experimental
<uvos>
lets see if it wokrs
<Wizzup>
ok
<Wizzup>
please suggest what to use wrt rwmem and I'll do it