<Wizzup>
tmlind: I briefly measured the ground of the microsd solder points on the mz617 and it does seem to be hooked up at least
xmn has quit [Ping timeout: 252 seconds]
xmn has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
xmn has joined #maemo-leste
ikmaak has quit [Ping timeout: 264 seconds]
ikmaak has joined #maemo-leste
xmn has quit [Ping timeout: 264 seconds]
Juest has quit [Ping timeout: 260 seconds]
mqlnv has quit [Ping timeout: 252 seconds]
mqlnv has joined #maemo-leste
mdz has joined #maemo-leste
<Wizzup>
uvos: hm, did you include powervr stuff in this kernel?
<Wizzup>
hm, I think I see what happened
STNX has joined #maemo-leste
<Wizzup>
tmlind: ok, I'm in :)
<Wizzup>
tmlind: amazing work
<Wizzup>
tmlind: somehow the sd card was just picked up with default mz617 dts
arno11 has joined #maemo-leste
<Wizzup>
so with the right dts it boots
<Wizzup>
scree nworks
<Wizzup>
touchscreen doesn't yet, but wifi works, serial works, usb otg works
<Wizzup>
now I can't help but wonder if it's just hooked up on the mz617 without us knowing
<Wizzup>
it being the microsd card
pere has quit [Ping timeout: 245 seconds]
<arno11>
Wizzup: hi, i need your advice/help to find those bloody ret/off mode blockers: i have a basic sdcard to try to load a very minimal config on the n900 and to try to add one by one every modules. But i don't know what's the trick to load a minimal config :P
<Wizzup>
tmlind: looks like ts works actually
<Wizzup>
arno11: give me 5-10 mins
<Wizzup>
tmlind: but some leste config or xorg config messes it up
uvos has joined #maemo-leste
<uvos>
ts worked, so thats a regession
<uvos>
the micro sdcard holder is not simply not installed, tmlind solderd one on his and that dident work
<uvos>
pvr works fine
<uvos>
d4 leste ofc stopes ts working
<uvos>
because the ts is blaklisted in libinput
<uvos>
since we use the filtered touchscreen device instead (from ts-buttons)
<Wizzup>
uvos: hi, just a few mins
<arno11>
Wizzup: finally i have to go, let's see pm stuff later ;)
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
uvos: hi
<Wizzup>
arno11: ok, I'll write here anyway
<Wizzup>
uvos: so it looks like there is a ts, but there are some probe errors
<Wizzup>
uvos it looks like X saw the ts but then dropped it
<Wizzup>
[ 451.889] (EE) libinput: Atmel maXTouch Touchscreen: Failed to create a device for /dev/input/event3
<Wizzup>
[ 451.889] (EE) PreInit returned 2 for "Atmel maXTouch Touchscreen"
<Wizzup>
uvos and of course there is still the droid4 calibration file in udev
<Wizzup>
uvos: so the mz609 and mz617 dts do not build, otherwise I might be able to try another kernel build for experimental
<Wizzup>
uvos: worth noting is that it seems like the cache partition containing kexecboot somehow gets messed up by android, so it's not just android getting buggy
<Wizzup>
uvos: I have some hack fixes for the dtses, shall I just push those to a test branch to debug the rest of the process?
fab__ has joined #maemo-leste
<Wizzup>
uvos: so this time on boot both atmel_mxt_ts probes failed
<Wizzup>
[ 7.488616] atmel_mxt_ts: probe of 1-004a failed with error -121
<Wizzup>
[ 8.142578] atmel_mxt_ts: probe of 1-005b failed with error -121
<Wizzup>
uvos: I suppose I could take the part from mz616 and put it on my mz617 and see if it seems a microsd
<uvos>
i never tried building the mz6xx dts's in that branch
<uvos>
so them being broken in the merge is not compleatly suprising
<Wizzup>
check
<uvos>
as i say
<Wizzup>
I would like to see if my changes to builddeb worked, so for that purpose I might commit a change that just kludge fixes them for building, not for using purposes
<uvos>
i presume you removed the blacklist of the ts
xmn has joined #maemo-leste
<uvos>
ok
<Wizzup>
yes I removed the blacklist and blacklisted ts buttons
<uvos>
ts-buttons should not load at all
<uvos>
as it should not be in the dts
<Wizzup>
not sure, I just flashed a d4 image, never booted it, then changed boot.cfg, added dtb and kernel and modules
<uvos>
ok
<freemangordon>
wow, that's fast
<freemangordon>
why it seems smoother than d4?
<uvos>
same as bionic
<uvos>
it lacs the pannel refesh bug of d4
<freemangordon>
ah
<Wizzup>
uvos: btw you said the display doesn't turn off yet, or idle correct, if I recall correctly?
<uvos>
no that used to be the case
<uvos>
it should now
<Wizzup>
ah, okay
<uvos>
it also sleeps fine
<uvos>
and has very low power cosumption when it dose
<uvos>
i can run weeks if you dont touch it
<Wizzup>
hmm
<Wizzup>
on leste?
<uvos>
no just minimal debian
<Wizzup>
I see
<uvos>
but leste too really
<Wizzup>
right now it uses about 0.180A at 3.85V on my lab psu
<Wizzup>
with the screen off, but wifi on
<uvos>
hmm
<Wizzup>
I suppose we might need some idling scripts
<uvos>
ret?
<Wizzup>
RET is 0 atm
<uvos>
hmm ok something is blocking
<Wizzup>
root@devuan-xt616:~# /etc/init.d/droid4-powermanagement status
<uvos>
yeah i mean once tmlind figured out whats wrong with the bridge driver
<Wizzup>
[ 39.827178] asoc-audio-graph-card: probe of soundcard failed with error -110
<uvos>
its just a big d4
<Wizzup>
still :)
<Wizzup>
which reminds me, does razr still have this screen issue?
<uvos>
you have some mz604 right
<uvos>
just mentioning: according to xda some of those have unlocked bootloaders
<uvos>
not that its super revelant to us
<uvos>
its not like we are going to use a different boot procedure for some random mz604
<Wizzup>
are those omap?
<Wizzup>
hm yeah so this time to atmel probe failed again
<Wizzup>
s/ to / the /
<uvos>
i ment 607 sry
<Wizzup>
ok
<uvos>
all 604s are unlocked
<uvos>
but thats nvidia powered xoom1
<Wizzup>
let me check @ mz607
<Wizzup>
I have something labelled mz608 here as that is what the firmware says, but it doesn't have a microsd card slot exposed
<Wizzup>
I *think* the rest are mz609
<uvos>
ok
<uvos>
no
<uvos>
mz607 european wifi only version
<uvos>
same story as xt912/xt910 some european examples have unlocked bootloaders
<uvos>
depends on where they where sold exactly
<Wizzup>
we have the luxury to get one on ebay in any case, or if you find specific xt91x es
<Wizzup>
if it helps with the devel we can use funding money to acquire them
<uvos>
i have one allready
<Wizzup>
mz607?
<uvos>
xt910 (or 12 i dont remember) with a unlocked bootloader
<Wizzup>
right
<uvos>
i have no mz60x variant at all
<Wizzup>
I know there's a lot of different chat threads, but do you recall if the razr still had this refresh bug?
<uvos>
yes it dose
<uvos>
i never got to that either
<Wizzup>
ok
<uvos>
i was going to ajust the timeings slightly to see if it goes away
<Wizzup>
ok
<Wizzup>
once the conversations/telepathy settles down a little I would like to retry droid3/razr/atrix 2
<uvos>
working droid3 would probubly be most usefull
<uvos>
razr has a nice display, atrix 2 is kinda just a bionic (maybe it even boots the bionic image, would not suprise me at all, stock android dmseg output suggests its exatcly the same as bionic)
<uvos>
minus the lte modem ofc
<Wizzup>
I think getting them all to work would be great and I agree d3 is most useful, in the sense that it is mostly d4, but just with less ram, but no modem restrictions in the us
<Wizzup>
(which is useful for me :))
<uvos>
well it also has the older non-vunerable bootloader
<uvos>
which is booo
<uvos>
thats a benefit xt91x has over bionic too
<Wizzup>
right, clown boot
<tmlind>
good to hear the micro-sd works with leste on some tablets :)
<Wizzup>
yes, it's amazing :D
<tmlind>
so which tablets are now confirmed to work for micro-sd?
<tmlind>
only mz616?
<Wizzup>
so far, yes
<Wizzup>
the mz608 that I have here (presumably) according to some websites has microsd, but it is not exposed, I had not pried it open yet
<Wizzup>
you're looking at it all wrong, this is a challenge to make the modem work ;)
<uvos>
xD
<Wizzup>
do you remember what made supporting mdm6600 over spi particularly hard?
* Wizzup
will try to grep irc logs
<uvos>
Wizzup: kernel just dosent implement qmi over spi (just from what tmlind explained from memory)
<Wizzup>
right
<Wizzup>
there must be non-omap phones using qmi over spi
<Wizzup>
but maybe not mainlind :)
<Wizzup>
mainlined*
<uvos>
iirc on android the kernel just exposes the modem interfaces to userspace and some blob talks qmi
<uvos>
so the downstream implementations are not very usefull
<Wizzup>
oof that would be ugly
<uvos>
now i wonder if mz608 is also mdm6600 over spi
<uvos>
that would complete the theory that all gsm only devices are so
<Wizzup>
from what I found tmlind wrote that xyboards have modem on spi
<uvos>
nah
<Wizzup>
16:22 < tmlind> uvos: xt910, xt912 and xyboard all uses qmi over spi for the modem i think, so at least i'm not working on that stuff
<Wizzup>
18:46 < tmlind> uvos: i think also droid4 has spi2 wired to the modem but not in use in the phone firmware. maybe that's just a config option though who knows
<Wizzup>
but this was many years ago
<uvos>
pretty sure he is wrong for xt617
<Wizzup>
probably 4+ years
<uvos>
he is def wrong for xt912
<uvos>
only xt910 has it over spi
<uvos>
and im pretty sure he is wrong too for mz617
<Wizzup>
right, I think he got the modem working on mz617 :)
<Wizzup>
just data only
<Wizzup>
if the blob speaks qmi over spi, it might not be super complicated, but yeah, maybe cm or lineage can tell us a bit more
<Wizzup>
on the mz616, I also don't see the modem on usb, but the kernel reported the modem powered up ok
<Wizzup>
uvos: there seems to be /sys/bus/platform/drivers/qmi-over-spi and /sys/module/qmi_spi on the 3.0.8 kernel
<Wizzup>
any idea where the kernel tree for edison could be found?
<uvos>
probubly its just the motorola_mapphone_common tree
<uvos>
otherwise motorola published the code on sourceforge
<uvos>
(we should really save all of that sourceforge gets iffier by the month)
<Wizzup>
yeah lsusb says nothing but that could just mean the modem didn't power
<Wizzup>
ok, ttyl
<uvos>
on android ofc
<Wizzup>
root@edison:/ # lsusb
<Wizzup>
Bus 001 Device 001: ID 1d6b:0002
<Wizzup>
that's just some root hub I think
uvos has quit [Quit: Konversation terminated!]
Twig has quit [Remote host closed the connection]
<Wizzup>
<6>[ 113.538391,0] omap_hsi omap_hsi.0: Modem wakeup detected from HSI CAWAKE Pad port 1
<Wizzup>
hm
<Wizzup>
isn't that what the n900 uses too? ssi/hsi?
<bencoh>
it is indeed
mdz has quit [Ping timeout: 264 seconds]
mdz has joined #maemo-leste
pere has joined #maemo-leste
<Wizzup>
arno11: on the n900 pw question... it's difficult/complicated. what you (imo) really need is the ability to use a serial device with the n900, and (probably) also some external power supply
<Wizzup>
the problem is that for these tests, you really probably don't even want the display on, or the keyboard enabled, initially
<Wizzup>
arno11: perhaps more feasible is just trying to identify blockers from a running maemo leste system, but this is also not at all easy unfortunately, we do have a way to print the (sub)system that is blocking idle, and then we can maybe guess the driver