libera/#maemo-leste/ Friday, 2021-10-08

Wizzupuvos: droid4 uses xserver-xorg-video-omap, n900 uses xserver-xorg-video-pvrsgx00:03
Wizzupso mm_width in output_info is also 000:06
Wizzuphttps://github.com/maemo-leste/n9xx-xf86-video-fbdev-sgx/blob/master/src/output.c#L79100:07
Wizzupuvos: correction n900 uses xf86-video-pvrsgx00:15
Wizzup(repo)00:15
Wizzupbut to be clear that is *not* n9xx-xf86-video-fbdev-sgx00:17
lelMerlijnWajer opened an issue: https://github.com/maemo-leste/bugtracker/issues/578 (N900: screen rotation segfaults in sgx_exa_update_pixmap)00:26
WizzupI think xf86-video-pvrsgx might not be building with debug symbols00:27
Wizzupyu[00:28
Wizzupwe need to fix that00:28
Wizzuprebuild with debug symbols00:50
Wizzupok so the qPixmap is a null pointer in sgx_exa_update_pixmap01:01
Wizzupmaybe PVR2D_PostFBReset should not be calling that on zeroed pixmaps01:01
Wizzupyeah so the pixmaps are deleted pvr2d_flip_put_bufs and never re-allocated it looks like (on rotation)01:07
WizzupI think I'm getting closer to the problems on the n900 wrt rotation02:22
Wizzupbut it's bed time now :)02:22
siceloWizzup: that would be awesome. i see  your ticket!08:12
Wizzupwe'll see, I'm not super deep into this X stuff10:57
Wizzupheh:11:28
Wizzup    /* SGX has a 2048x2048 maximum texture size limit */11:28
Wizzup    /* FIXME should be limited further based on the amount of vram */11:28
Wizzup    xf86CrtcSetSizeRange(pScrn, 1, 1, 2048, 2048);11:28
Wizzupmight make sense to do that I think11:29
uvosWizzup: hmm?12:22
Wizzupuvos: remind me?13:07
uvos"might make sense to do that I think"13:09
Wizzupthe crtc seems too large for n900 but that is not the bug13:09
uvosxf86CrtcSetSizeRange13:10
WizzupI decided to dive a bit into the rotate crash and why it crashes is obvious13:10
uvoseven modern fat desktop gpus have that13:10
Wizzupthe solution less so13:10
uvoswith a 16k maximum13:10
uvosas thats the texture size limit on amd gcn for instance13:10
Wizzupmhm, it might not be relevant13:10
uvosits not13:11
uvosbut anyhow geting rotation to work would be neat13:11
Wizzupuvos: unrelated, do you see ts buttons wake up device when it is locked13:11
uvosWizzup: no13:12
uvosand they should not13:12
Wizzuphm, now I do not see it13:12
Wizzupweird, might be me13:12
uvosim not sure fixing video-pvrsgx makes sense13:12
uvosvs fixing -modesetting on ddk1.1713:12
Wizzupit might be a relatively simple fix and sphone won't cause resets anymore ;)13:13
uvossure13:13
Wizzupunless you want to hold back hildon-desktop xinput changes until 1.1713:13
Wizzupsince it also breaks ts13:13
uvosno but a sanity check would be ok13:14
uvosi just would avoid spending to muich time on it13:14
Wizzupagreed13:14
WizzupI might have some questions a bit later wrt X13:14
uvosbtw we cant move to ddk1.17 wihtout either fixing chromeos mesa pvr13:15
uvosor moveng to a debian 1113:15
uvosbase13:15
uvosso gconf blocks here too a bit13:15
uvosbecasue mesa cant dlopen the pvr_dri plugin (because its compile agains later libc)13:17
uvosso even with weakend symbol versions you have to preload pvr_dri13:17
uvosbut having it preloaded for everything (since how would you know what uses libgles when setting the envvar)13:18
uvoscauses lots of funn issues13:18
uvoswrt symbol resolition in random binarys13:18
uvosand also stuff like cp sometimes segfaulting13:18
uvosthis getting  rid of gconf is pretty important13:19
uvos(or fixing foss pvr mesa pick your poison)13:19
sicelohow would a debian 11 base help?13:19
uvosit has newer libc13:19
uvosso mesa can dlopen binary pvr_dri.so13:20
sicelook13:20
uvosChimaera i gues13:22
uvosi just mentiond debain 11 becaus idk how devuan versions line up13:22
uvosobv. it would be something devuan based.13:22
Wizzupanother reason to first fix this ddx probably13:29
Wizzuproot@devuan-n900:/sys/devices/platform/omapdss/display0# ls|grep rotate15:16
Wizzuprotate15:16
Wizzuproot@devuan-n900:/sys/devices/platform/omapdss/display0# file rotate15:16
Wizzuprotate: ERROR: cannot read `rotate' (No such file or directory)15:16
Wizzupugh15:16
uvoswtf is it doing15:17
uvosit should be using the drm interface15:17
Wizzupn900 is not omapdrmfb15:18
Wizzupwith the powervr driver15:18
WizzupI think the pvr kernel driver we use doesn't support it?15:18
Wizzup(not sure about that)15:18
uvosits runing on the old fb video interface?15:18
uvosugh15:18
Wizzupyes15:18
uvosok15:18
Wizzupso this seems to be the problem: https://github.com/maemo-leste/bugtracker/issues/578#issuecomment-93863486215:18
Wizzupso the problem could be that the rotate just fails, which then makes that not work, but I need to check that15:19
uvosso ddk1.9 never was available for omap3?15:20
uvosat least its not this crusty15:20
WizzupI don't think so15:23
Wizzupwe could check, but no point in trying to go back15:23
Wizzup    r = dss2_read_int(dss2_fb, idx, "mirror", &mirror);15:24
Wizzup    if (r && errno != ENOENT)15:24
Wizzup        goto error;15:24
Wizzup    can_mirror = !r;15:24
Wizzuplol15:24
Wizzupuvos: I wonder if the zero width and height come from the other fb devices15:40
Wizzuphttps://wizzup.org/Xorg-rotate-fail.log15:54
Wizzupmost of that logic seems to be in crtc_set_mode_major15:56
Wizzupmaybe the problem is that the overlay rotate is 0 when it should not be?16:03
Wizzupyeah ovl_rotate is OMAP_ROTATE_0 when it should be OMAP_ROTATE_90 ?16:11
Wizzupnone of this makes any sense16:20
Wizzupfor example this call:16:23
Wizzup[   882.456] fbdev_crtc_config_resize(0x5ab518, 480, 800)16:23
Wizzupwhy would it have this effect:16:23
Wizzup[   882.485] overlay_update: putting fb_var_screeninfo xres 480 yres 48016:23
Wizzupand for this call:16:23
Wizzup[   882.501] crtc_set_mode_major(crtc=0x5ac358, mode=0xbeb69068, rotation=8, x=0, y=0)16:23
Wizzup[   882.501]  mode = 800x48016:23
WizzupI can imagine that maybe mode 800x480 with rotation=8 (RR_Rotate_270) means that the mode is actually 480x80016:24
Wizzupbut then a simple switch statement to set the omap mode to OMAP_ROTATE_90 just returns OMAP_ROTATE_016:24
Wizzupwhich I think is why the ovl does not fit16:24
Wizzupwhich makes the enable write fail16:24
uvoswell in x screen mode scann mode and screen size are different things16:25
uvos800x480 with rotation=8 makes perfect sense if the 800x480 is the scann mode16:25
uvosno idea how rotation works in the fbdev interface kernel side16:27
uvosthe kernel itself dosent change any buffers when you rotate the console on fbdev16:27
uvosit just renders stuff sideways16:27
uvosin drm mode it changes how the frambuffer is scanned out to really rotate it16:27
freemangordonWizzup: maybe ask tomi for help16:28
freemangordonthis looks like a bug in omapfb16:29
freemangordonalso, IIRC rotation was working on Pali's tree16:29
Wizzupyes, but this is one that spinal forked16:29
WizzupI really don't know what/which version is newest/latest, etc16:29
freemangordonhe forked which tree? Pali's?16:30
WizzupI don't know16:30
freemangordon:)16:30
Wizzupthis is it https://github.com/maemo-leste/xf86-video-pvrsgx/16:30
freemangordonWizzup: I mean - what kernel?16:30
Wizzuplooks like it's a fork from some fbdev omap fork https://github.com/maemo-leste/xf86-video-pvrsgx/commit/219c3da7796ec82634cb459d24e4747065ed22a916:31
Wizzupfreemangordon: 5.116:31
freemangordonmhm16:31
freemangordonoh, I see, we don;t have armhf meego binaries16:32
Wizzupyes16:32
freemangordonWizzup: the ^^6 logs are from dmesg, right?16:33
uvosits X16:34
Wizzupthe Xorg.log I pasted is from Xorg with pvrdrv with all debug on16:34
Wizzupthe few lines in the github issue are from kernel16:34
Wizzuphttps://github.com/maemo-leste/bugtracker/issues/578#issuecomment-93863486216:34
freemangordonok16:35
freemangordonand, what happens if you try to rotate through sysfs?16:35
Wizzupwith X on?16:36
freemangordonmhm16:36
Wizzupwill try in a bit16:36
WizzupI assume you mean the fb0/rotate file16:36
freemangordonright16:37
Wizzupwill try, but everything with n900 takes time16:37
freemangordon:)16:37
Wizzuplots of time16:37
freemangordonhmm:16:40
freemangordonhttps://github.com/maemo-leste/xf86-video-pvrsgx/commit/04273d50383c035652b76e43886b5571ec09feb416:40
freemangordonhttps://github.com/maemo-leste/xf86-video-pvrsgx/commit/49ec10cb645b3d4ab368d959c9abf813534fd30016:40
freemangordonunrelated, but still16:40
freemangordonWizzup: hmm, rotate 270 is rotate 0 + mirror16:42
freemangordonisn;t it?16:42
Wizzupoh I see16:44
Wizzupso maybe it works with blit and flip was just always broken16:44
Wizzupthose are kind of conflicting commits16:44
freemangordonno, wait, rotate 270 is not rotate 0 + mirror16:44
freemangordonyes, my point16:44
Wizzupit should just be rotate yes16:45
Wizzupin any case it looks like (still trying to figure it out) that the enable write fails (see kernel msg) because ovl_rotate = 016:46
Wizzupand it should not be 016:46
Wizzupthere is other weirdness going on, but that seems to be the main reason16:46
freemangordonok16:46
Wizzupapart from the segfault I fixed earlier16:46
freemangordondo you need any help with that?16:46
Wizzup(where they do not free the pixmap, and just null the pixmap pointers, and then try to access the pixmap pointers)16:46
Wizzupmaybe you can read through my thoughts on the issue and comment here16:47
Wizzupin particular16:47
Wizzuphttps://github.com/maemo-leste/bugtracker/issues/578#issuecomment-93822533716:47
Wizzupthe suggested fix is not perfect, since it still needs to destroy the pixmaps before they get nulled, but that's an easy fix later on16:47
Wizzupand yes I would appreciate help if you have spare cycles16:47
Wizzupbut if it's too much of a timesink I suggest we drop it and focus on new pvr stuff later16:48
freemangordonbut, is it possible that because of those contradicting commits, half of the code tries to blit, the other half to flip?16:48
Wizzupyes, we can try to synchronise that first16:49
freemangordonmhm16:49
Wizzupfirst I need to fix my driver because I forgot a break; in a switch where it had default: assert(0) :p16:49
freemangordon:)16:50
freemangordonre new ddk - is there any change since I last tried16:50
freemangordonon 5.10 it was just freezing the device16:50
Wizzupprobably nobody tried since16:50
freemangordon:(16:50
WizzupI wasn't going to look at the old driver at all except that the new hildon-desktop rotation code breaks all touch on n90016:51
freemangordonmaybe I can try latest, if anybody points me to the latest16:51
Wizzupbecause it reports some size of (0, 0) and maps all touch input  to 0, 016:51
Wizzupfreemangordon: I'd ask uvos or tmlind16:51
freemangordonuvos: any clue which one is the latest pvr?16:52
uvoswdym?16:52
freemangordonwhat repo/branch16:53
uvos5.11 (but realistcly you should use 5.10 because its lts) is the last version to support ddk 1.9 and 1.1416:53
freemangordon1.17 is what I mean16:53
freemangordonI want to build for n900 and see if it works16:53
freemangordonlat time I tried it was not16:53
uvosthere is 5.15 rc16:53
freemangordonwhere?16:53
uvoshttps://github.com/tmlind/linux_openpvrsgx.git16:54
uvosthe usual place16:54
freemangordonthanks16:54
uvosim pretty sure sicelo or someone tried 5.13 on n900 with ddk1.1716:55
uvosand it worked16:55
freemangordonthat would be great16:55
freemangordongoing to try 5.15-rc16:56
uvosmaybe he can comment16:56
Wizzup[   130.343] fbdev_rr_to_omap_rotate rotation = 8 -> rotate= 117:08
Wizzup[   130.343] ovl_mirror = 0, ovl_rotate=017:08
Wizzuplol17:08
Wizzuphow17:08
Wizzupoh, I see...17:09
Wizzupfreemangordon: doesn't look like the swap method makes xrandr work17:10
Wizzupuvos: re: ddk 1.17 and requiring chimeara17:11
Wizzupdon't we have a way to weaking the symbols in the pvr libs?17:12
Wizzupweaken*17:12
uvossortof helps partailly17:12
uvosbut dlopen in mesa still fails17:13
uvosso you have to preload the dri componant17:13
uvosand that causes a bounch of other issues17:13
Wizzupok17:13
uvosbecause you have to do it golbaly17:13
Wizzupwell we can import gconf in chimeara I bet :)17:13
uvosmaybe17:13
WizzupI did the same for python-gconf and some other things iirc17:13
uvosparazyd mentioned its hard17:14
uvosbecuase of dh involement not sure exactly17:14
uvosmanwhile i also ported maemo-input sounds away from gconf17:14
uvos*meanwhile17:14
Wizzupit might make sense to start a tracking ticket for all of this stuff17:14
Wizzuplike we did with beowulf17:14
uvoswe have one17:14
Wizzuphttps://github.com/maemo-leste/bugtracker/issues/29917:14
Wizzupah, where is it?17:15
uvosfor gconf17:15
uvosnot for porting to chimera generally17:15
Wizzupdo you have a link?17:15
uvosno just search gconf on the tracker17:15
uvosso i have mce, osso-applet-display, osso-applet-notificationlight, simple-brightness-applet and maemo-input-sounds ported away from gconf17:16
uvosall of these where just in the way when porting mce away really17:16
Wizzuphttps://github.com/maemo-leste/bugtracker/issues/481 this one?17:21
uvosyes17:21
Wizzupwell we can decide to bite the bullet if the 3d sitation is better, otherwise I don't feel like doing it yet17:22
Wizzupis gsettings and dconf available on beowulf then as well?17:23
freemangordonis port trivial?17:23
uvosport what?17:23
uvosaway from gconf?17:23
freemangordongconf->gsettings17:23
uvosno idea i havent done it17:23
Wizzupso what did you port them to, if not to gsettings?17:23
freemangordon"(18,16,30) uvos: so i have mce, osso-applet-display, osso-applet-notificationlight, simple-brightness-applet and maemo-input-sounds ported away from gconf" ?!?17:24
freemangordonyep, same question17:24
uvosok so with mce i ported to expose its external iterfaces that it has on gconf to also have getter/setter/notify methods on dbus17:25
uvosthen the mce faceing applets i ported to these dbus interfaces17:25
uvosmce also has selectable config backends so it can save to gconf of just a ini file with gsettings bein wip (havent finnished that yet)17:25
uvosand then  osso-applet-displa also set on other gconf key17:26
uvosthe one that tells maemo-input-sounds to vibrate the with touchscreen presses17:26
uvosthis is also the only gconf key it uses, with everthing else, (ie if a sound is to be played when the ts is touched etc) it gets from libprofile17:27
Wizzupso the ui can't set a value unless mce is running?17:27
Wizzupor do I misunderstand17:27
Wizzupfreemangordon: so uh, writing to the fb0/rotate doesn't do much with X running17:28
uvosso i just added a touchscreen.vibrattion.enabled key to profiled17:28
uvosand now that is profile dependant same as touchscreen.sounds.enabled17:28
uvoswhitch makes more sense anyhow17:28
uvosWizzup: yeah mce needs to be running for the ui to change the setting, but i dont see how thats a problem, gconf also had to be running and both of those are system global deamons17:29
Wizzupyes but gconf is the config management system17:29
Wizzupand for example settings keys in the ci when building images was already tricky17:30
Wizzupif it requires mce to run it will get a lot more tricky17:30
uvosthe main benefit with this is that now all mce interfaces are on dbus so they are allways availbe and dont change when mce changes settings backend.17:30
uvoswell mce still stores the stuff soemwhere17:30
uvosso in ci you can just chagne the gconf or gsettings key17:30
uvosi dont see the problem17:30
uvosor in the default ini file if you want to use the ini backend17:31
uvosbut thats mainly intended to be a fallback17:31
Wizzupit just seems backwards to me that if an app wants to change a config key that it has to go through mce to set the config key, instead of mce listening to config key changes, I suppose17:32
Wizzupthere is already a tool it needs to go through to changes, which is gconf/dconf iiuc17:32
uvossortof17:32
uvosbut if you look at the keys17:32
uvosonly really the led ones are really config17:32
uvosits allso really backwards for the external application to request a change in lcd brightness by setting some config key17:33
uvosimo17:33
uvosand since the gconf interfaces are so few (only 3 unique ones)17:33
uvosit makes sense to just move everything to dbus17:33
uvosin this case17:33
uvosi do agree that moveing everything to dbus is not a solution in the general case17:33
uvosoutside of mce17:33
uvosthe main point here also is that mce can be used with different settings backends and its not ok that mce dependant applicaitons (also outside of maemo leste here) cant be sure that x interface will be available becasue the user decidede to use a different settings strorage backend17:34
Wizzupso in the current beowulf setup, the keys will just end up back in gconf, is that right?17:35
Wizzupvia mce17:36
uvosyeah both interfaces are allways kept in sync by mce17:36
uvosie a dbus request to change the lcd brightness will cause mce to store this in gconf17:36
uvos(or in the ini file if you load that plugin instead)17:36
uvosand changing the gconf key with cause mce to notify its dbus clients of the change also17:37
uvosi would like to know if there are any remaining qualms about how this works...17:42
Wizzupall my qualms currently are with this fbdev clone :)17:45
uvosbtw we could also consider17:46
uvosinstead of moving to gsetttings17:46
uvosto minimally extending profiled to also provide profile independant keys (or even just using the override profile) and porting everthing to that since this accives independance from gnome wimms and we are lugging profiled around as a settings deamon anyhow17:47
uvoslibprofile and gconf are really close in terms of api too17:48
WizzupI think many things should not go in libprofile17:48
Wizzuplike when the email client last updated17:48
Wizzupjust check how many gconf keys there are for modest alone17:48
uvosyeah i mean profiled would need a special overarching noprofile profile17:49
uvosother than that i dont see the problem really17:49
WizzupI think it's not a bad idea to port to gsettings17:49
WizzupI hope the api will be similar (dconf)17:49
uvosthe amount of keys seams not relevant17:49
uvosdconf dosent have stable api at all afaik17:49
uvoswe should avoid using it directly17:50
Wizzuphttps://www.freedesktop.org/software/gstreamer-sdk/data/docs/2012.5/gio/GSettings.html17:50
WizzupI mean it seems literally the same17:50
uvossure yeah17:50
Wizzup%s/gconf/g_settings/g17:50
Wizzupdefault key handling seems different but we always did that anyway17:51
uvosyeah i dont think porting stuff to gesttings is hard17:54
mighty17[m]tmlind: wlroots + sway isnt working as well now :/18:27
mighty17[m]https://paste.debian.net/1214779/18:27
mighty17[m]wht sway version do you use?19:00
Wizzupfreemangordon: I am going to stop looking at the ddx for a bit20:32
Wizzup(the old one)20:32
freemangordonok20:39
freemangordonI am compiling 5.15-rc20:39
uvosWizzup: if your not going to solve the ddx problem20:39
MartijnBraam[m]5.15 for n900? :D20:39
freemangordonyes20:40
uvosplease add a workaround to the h-d function that detects the ddx failure and avoids setting the transform matrix20:40
freemangordonI want to see if pvr driver is working20:40
MartijnBraam[m]the pmos n900 kernel is a bit behind :P20:40
sicelonot a bit :-)20:40
freemangordonso is leste20:40
uvosthe leste kernel is more behind im sure20:40
siceloi wanted to work on it (pmos), then ... the usual20:40
freemangordonsicelo: do you have working config around?20:41
uvosdose omap2plus_defconfig not work?20:41
uvosit should20:41
uvospls report if it dosent....20:41
freemangordonit didn;t last time20:41
uvoswell thats a bug20:41
freemangordonalso, it has a pile of stuff not used on n90020:41
uvosjust searching for some other defconfig is not a solution20:42
uvosso its just modules20:42
freemangordoncould be, but my task is to check pvr, not omap2plus_defconfig20:42
MartijnBraam[m]I just remember skipping a few versions because the display was broken, and now we're still on 5.720:42
uvoswe are on 5.1 so we win20:42
siceloyes omap2plus should work. i also added a few more modules to it, and Tony kindly accepted my changes :-)20:43
MartijnBraam[m]oof20:43
MartijnBraam[m]are you really winning though?20:43
sicelofreemangordon: but let me quickly check what i have on my laptop20:43
freemangordonsicelo: so you think I should use omap2plus_defconfig to test pvr?20:43
freemangordonhmm20:43
freemangordonok20:43
siceloyes, should be fine20:44
freemangordonok20:45
uvosfreemangordon: maybe also try chromeos mesa while at it20:45
freemangordonlemme first have a kernel20:45
WizzupMartijnBraam[m]: we had trouble forward porting 3d to 5.2+20:45
Wizzupat least the old 3d20:45
uvossee https://github.com/maemo-leste/bugtracker/issues/524 for links20:45
Wizzupuvos: yeah ok @ workarounds, but not yet20:46
Wizzupuvos: if I add a workaround I will make sure that it also refuses to do xrandr so that sphone won't cause resets :P20:46
freemangordonuvos: this one does not require newer glibc, no?20:46
uvosright20:46
freemangordonso there is no hard dependency to chimaera, IIUC20:47
uvosno it works fine on beowulf20:47
freemangordonmhm20:47
uvoswell aside the ususal bugs20:47
freemangordonyeah20:47
* Wizzup curious20:50
Wizzupif it doesn't just straight up hang the device I would be up for trying to help making it work somehow20:50
Wizzupbrb20:51
uvoswelcome to the fun times of messing with imagination hw20:51
uvosimagination - its what you need so see it working.20:52
Wizzuplol20:52
freemangordonand it does not compile :(20:54
uvosthe kernel?20:54
freemangordonmhm20:54
uvosit compiles for sure20:54
uvosi do that often20:54
uvosgcc version maybe?20:54
freemangordonwell, the branch I checked out20:54
freemangordonI compile in leste20:55
uvoswhat did you check out?20:55
freemangordonletux-pvrsrvkm-5.15-rc120:55
uvosi use mutch newer gcc20:55
uvosoh20:55
uvoswhy20:55
freemangordonwhy what?20:55
uvosuse droid4-pending20:55
freemangordonfor n900?20:55
uvosyeah20:55
freemangordonwhy?20:55
freemangordonlast time it has droid patches which made it not boot on n90020:55
uvosits best maintiained and there are not d4 specific hacks in there really20:55
uvosthe droid4-pending sgx branch20:56
freemangordoncould you provide link?20:56
uvoshas nothing d4 specific20:56
uvoshttps://github.com/tmlind/linux_openpvrsgx/tree/droid4-pending-pvr-omapdrm-v5.1520:57
uvosthis contains just plain 5.15 with tmlinds latest sgx patches20:57
uvoshttps://github.com/tmlind/linux/tree/droid4-pending-v5.1520:57
uvosthis is where the real pending d4 specific patches are20:57
uvosts-buttons and modem code and so on20:58
uvoscpcap charger20:58
uvosso i would checkout latest rc20:58
uvosand then merge droid4-pending-pvr-omapdrm-v5.1520:58
freemangordonuvos: latest -rc is supposed to have sgx driver as well20:59
uvos?20:59
uvoswe are on 5.15 rc321:00
uvoser 4 now21:00
freemangordonok21:00
uvosdroid4-pending-pvr-omapdrm-v5.15 is rc221:00
uvosso checkout mainline 5.15 rc4 and merge in droid4-pending-pvr-omapdrm-v5.1521:01
freemangordonhmm, only 1.17 is there21:01
freemangordonbut that's fine21:01
uvosofc21:01
uvosthe old ones where dropeed with 5.11 because major rework is needed to get them to compile with omapdrm > 5.1321:02
uvosbecasue it tunnels the ioctls through it before ddk1.1721:02
freemangordonthats fine as we are not interested in anything < 1.1721:06
Wizzupright21:06
freemangordonsame failur :(21:08
Wizzupit resets when?21:09
Wizzuphangs?21:09
freemangordonhttps://pastebin.com/SBGfKb0r21:09
freemangordonI cannot compile the kernel21:09
Wizzupyou need newer uh21:10
Wizzupdtc21:10
freemangordonhmm?21:10
Wizzupactually, git reset --hard (save the config)21:10
Wizzupso I had this problem recently21:10
uvosor mrproper21:10
freemangordonI think I already did21:10
uvosit compiles fine for me21:11
Wizzupfrom old logs21:11
Wizzup18:23 < uvos> mrproper aka rebuild everything helped in these cases21:11
Wizzup18:23 < bencoh> yeah, mrproper is magic sometimes21:11
Wizzup18:24 < Wizzup> ok, trying21:11
Wizzup18:25 -!- Pali [~pali@user/pali] has joined #maemo-leste21:11
Wizzup18:28 < Wizzup> I mean I don't really need a new dtb anyway21:11
Wizzup18:30 < Wizzup> ah, no, it looks like the fdt.c errors are from the kernel needing libfdt to unpack the dts21:11
Wizzup18:31 < Wizzup> I'm using droid4-linux droid4-pending-pvr-omapdrm-v5.1121:11
Wizzup18:32 < Wizzup> internet suggests git clean -xdf21:11
Wizzup18:36 < Wizzup> that fixed it21:11
freemangordonok, lemme try21:11
freemangordonah, this is also known as -dfx :D21:12
Wizzupwhat's the joke?21:13
freemangordonWizzup: no need to keep the config as I am using vanilla omap2plus_defconfig21:13
freemangordonWizzup: I am using -dfx and was wondering what -xdf does21:13
Wizzupdfx is Don't FiX21:14
freemangordonor rather - I am used to -dfx21:14
freemangordonI see21:14
Wizzup(that was a joke)21:14
Wizzup(and not funny)21:14
freemangordonyeah21:14
WizzupI try too hard21:14
uvosbtw21:19
uvoscharging light on n900 works again right?21:19
freemangordonok, this time it compiles21:22
sicelorgb led? i won't be surprised if it doesn't, because there are some issues with the lp55xx LED drivers. 'charging light' is h/w controlled, so that works at all times, unless i'm forgetting something21:22
uvossicelo: this is about a spcific mce but i fixed21:24
uvos(and introduced in the first place)21:24
sicelook. no idea about *that*. if kernel driver doesn't work though ...21:26
uvosit works21:26
uvos(on 5.1)21:26
freemangordonhmm, latest u-boot should boot zImage, right?21:28
freemangordon*should be able to boot21:29
uvostheoreticly yeah21:30
uvosthe new uboot that is21:30
uvosbut i havent gotten it to work21:30
uvosbut i also gave up almost immidatly21:30
freemangordonok, will do with uImage21:30
freemangordonsicelo: hmm, with omap2plus_defconfig, shall I appned the dtb?21:35
siceloyes, if you're using uImage21:36
freemangordonbut, in kernel config this is not set. or, u-boot is smart enough?21:37
siceloit isn't set? last i remember it was21:37
freemangordonin omap2plus_defconfig?21:37
freemangordondidn;t check but I doubt it is21:37
uvoscmdline is ofc not forced21:38
siceloit is21:38
siceloCONFIG_ARM_APPENDED_DTB=y21:38
uvosidk what you mean21:38
siceloCONFIG_ARM_ATAG_DTB_COMPAT=y21:38
uvosoh that yeah21:38
uvosyes21:38
freemangordonok21:38
freemangordonmkimage: Can't read zImage: Invalid argument21:39
freemangordon:(21:39
freemangordonany idea?21:39
freemangordonok, PEBCAK21:40
sicelo:-)21:41
* sicelo has his fingers crossed that the N900 will boot fine (to a working display)21:43
freemangordonI doubt :)21:43
uvosi still find it kindof funny that the d4 with its locked bootloader ends up with more user frendly boot ergonimics21:43
sicelofreemangordon: the display is the most annoying part of booting a new kernel on N900. (i still need to build my console thingy for N900)21:44
freemangordonand... poweroff21:44
uvosmh21:44
uvosyou have the debugkit right21:45
freemangordonno21:45
uvoshmm21:45
uvosgreat21:45
sicelooh :-)         i don't recall facing that one, but then, i haven't been building N900 kernels for too long21:45
freemangordonyeah :)21:45
freemangordon(debugkit)21:45
Wizzupuvos: latest u-boot for n900? the one I built should work fine?21:47
Wizzupuvos: yes, the mce fix worked for charging light21:47
freemangordonhmm, it has usb console21:48
siceloi didn't find the uboot console super useful, since kernel disables it once it starts. and the problems are in the kernel. maybe there's a way to ask kernel to not disable it?21:49
Wizzupit is useful for testing / remote stuff21:55
Wizzupcompared to typing on that keyboard... ugh21:55
WizzupI mean I like the keyboard, but not in u-boot :)21:55
siceloyeah21:59
siceloit's just that most of the time, the real problems are in the kernel, not uboot :-(21:59
sicelomaybe we really should check if there's no way to have that console persist22:00
freemangordonok, as expected, omap2plus_defconfig doesn;t boot22:02
freemangordonif anyone has a working config around, please share22:02
sicelomake the watchdog built in. that's one change i usually make to omap2plus22:06
sicelo+CONFIG_OMAP_WATCHDOG=y22:06
sicelo+CONFIG_TWL4030_WATCHDOG=y22:06
freemangordonI am trying leste config ATM22:06
sicelowe should get you its serial console - i want to build one (based on sre's design), but i don't know if i'll be able to understand issues it reports. at least you would22:10
freemangordondo you have the schematics around?22:12
freemangordonor, are those available to buy online?22:13
siceloeven though he didn't provide schematic, it's a bit straightforward. https://n900.elektranox.org/serial-adapter.html22:14
freemangordonhmm, I wonder if I can build something that can fit bellow the battery, so no external power to be needed22:19
siceloi think so. something that could fit snuggly in the cutout under the battery, then have some thin/flexible wires or ribbon as a breakout22:24
freemangordonmhm22:24
freemangordonbut I am not sure I want to take that as well22:25
freemangordonmaybe tomorrow I will try to boot vanilla 5.1522:25
freemangordonif it boots, then maybe a bisect22:25
freemangordonnow going to have some sleep. good night!22:25
siceloo/22:26
Wizzupsicelo: weird idea but maybe we can get some made in china if the schematics are there23:06
Wizzup(yeah, I'm a bit lazy)23:06
Wizzupfreemangordon: if you send me your kernel I can boot it with my serial23:07
sicelo:-)23:07
Wizzup(also modules pls)23:07
Wizzupuvos: do you test mce in a vm?23:39

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!