libera/#maemo-leste/ Monday, 2024-03-04

Wizzupfreemangordon: I suppose I could make some fake pkg that provides all these translations, just for a small image01:34
Wizzupright now /usr/share/locale is like 150MB mostly because of these files I think01:34
Wizzupbut without it, I have a ~700MB image which should fit on the mz61701:34
Wizzuptmlind: ok, have my mz617 set up again, will look at what you mentioned re: cable being a problem02:37
uvosWizzup: sure, ill try and remember for next time09:15
uvosi gues having a bunch of stuff built into the kernel and not as kernel modules might bite us eventually09:17
uvosit would be good if it fits onto the n900s boot partition for instance09:17
uvosand n900 uboot did have some small kernel size limit that was a problem in the past09:18
uvosnot sure if that was lifted09:18
uvosi imagine btrfs is pretty large, given its featureset, but dont know how large in absolute terms09:19
siceloon n900 the u-boot sits on the kernel area. kernel itself can sit anywhere. i believe it's the same thing on D4. IOW, the size of actual kernel isn't really an issue for N90009:24
uvos__sicelo: it is if you want to append the kenrel11:02
uvos__D4 can have any size kernel yeah11:02
Wizzupuvos__: well as a module we can't use it as root11:36
Wizzupunless we start making initramfses11:36
sicelowhere are we planning to use btrfs11:43
uvos__sicelo: mz6xx11:45
uvos__to span the partitions11:45
Wizzupwell to span it we would still need a initramfs11:50
Wizzupin any case I did build a ~700MB ext4 leste image with the image builder that boots fine11:51
Wizzup(stripped down ofc)11:51
Wizzupso that is enough for mz617 to install to userdata11:51
Wizzup(which is like 13GB at least)11:51
uvos__you sure we need initramfs to span?11:56
uvos__i think just root=/one/device/of/the/span should work11:57
uvos__or could work at least11:57
Wizzupuvos__: doesn't work, tried that11:59
uvos__:(11:59
Wizzupbtrfs doesn't scan for devices in kernel11:59
Wizzupit needs userspace to scan somehow11:59
WizzupI agree it's dumb12:00
uvos__well now i dont know what we need btrfs to be built in for12:01
uvos__its not really a good filesystem for small flash volumes12:01
Wizzupcompression is still useful12:01
uvos__neither is ext4 but ok12:01
Wizzuproot@devuan-mz617:~# df -h12:03
WizzupFilesystem       Size  Used Avail Use% Mounted on12:03
Wizzup/dev/mmcblk1p20   13G  2.1G   11G  18% /12:03
Wizzupthis is default image with ext412:03
Wizzuper btrfs12:03
Wizzupbut no compression12:03
uvos__yeah sure12:03
Wizzupso it's not too bad space wise atm12:03
uvos__but the problem is user_data cant be flashed directly or12:03
uvos__that was one that could only be erased?12:04
Wizzupneither cache nor preinstall nor user data can be flashed directly12:04
uvos__cache can be flashed directly12:04
Wizzupbut from android you can write an image to cache12:04
Wizzupwell my cache can't I seem to remember12:05
Wizzupin any case,12:05
WizzupI flashed user data from my tiny leste on cache, which I dd't from android to cache12:05
Wizzupif we can flash directly to cache with fastboot that would be nice, and I'll probably try it some time soon12:05
uvos__ok but cache was where we originally placed fastboot because that was flashable12:06
uvos__er kexecboot not fastboot12:06
Wizzupok12:06
Wizzupcdrom is my kexecboot12:06
uvos__im not sure of the others12:06
Wizzupwell I can try this now that my userdata works12:06
uvos__preinstall for sure can be flashed too but that could be singed12:06
uvos__user_data cant be flashed at all, not evenby a signed image12:06
WizzupI made some image-builder changes with the hildon-meta-core split, and we can get pretty tiny images with just keyboard,wifi,h-d,cpa,ofono btw12:07
uvos__great12:07
Wizzuplocales are still 150MB, but without that it's like 750MB12:07
uvos__that seams pretty large still12:07
Wizzup(that is the debian translations)12:07
Wizzupyup, mesa is *huge*12:07
Wizzuplibllvm is like 70MB or so12:07
uvos__yeah gpu drivers can get absurldy huge12:08
WizzupThere was some other low hanging fruit that I tackled, like not adding iphbd or dkms, which pulls in gcc, and removing some pkgs devuan image builder installs that we don't need (htop, zsh, etc)12:08
uvos__(cires in 4GB AMD libdevice_opertions.so)12:08
Wizzupbut <800MB is enough for the mz6xx purposes I think12:08
Wizzupyeah that's probably some deeplearning stuff12:08
uvos__i think htop can go everywhere12:10
uvos__i was allways puzzeled why this was preinstalled12:10
Wizzupdevuan imagebuild does it12:10
Wizzupand yes it can go away12:10
WizzupI think having vim or htop preinstalled is nice for users of the regular image12:11
Wizzupit shows something in the debian submenu12:11
uvos__yeah12:11
uvos__i gues vim is needed for strict posix compat12:11
uvos__htop is just useless12:11
Wizzupit has a certain hackery feeling to it :P12:11
Wizzupbtw, I'm going to add razr and mzxxx images12:11
WizzupI was thinking of what we go through every time12:12
Wizzupleste-config can do in the xyboard "Section" I suppose12:12
Wizzupfor mzxxx12:12
Wizzup(since we made different ones for all the other devices)12:12
uvos__yes12:12
WizzupI wonder if we need more specific meta packages or leste-config's for the different mz61x12:12
uvos__well we dont know yet12:12
uvos__the accels could be oriented differently12:13
Wizzupand what do we call mz607,mz608,mz609 and what do we call mz615,mz616,mz617  - mz60x, mz61x ?12:13
uvos__for one thing12:13
uvos__mz60x and mz61x? :P12:13
uvos__oh yeah12:13
Wizzupok12:13
WizzupI would like to prevent buildimg images for all of the different submodels if possible (because the image building is inefficient)12:13
uvos__yeah12:14
Wizzupso I could name it either specifically, like mz617 or mz616, or mz61x)12:14
uvos__hopefully this wont bite us12:14
WizzupI suppose they will need a different inittab12:14
Wizzup(/boot/ on mz617 is really android /system)12:14
Wizzupif you keep the standard inittab it will error on boot and ask you to type in the root pw or ^D12:14
uvos__yeah12:15
Wizzup(since it wants to check /dev/mmcblk1p1 but can't)12:15
uvos__also what about the variants with sdcards12:15
uvos__i think sdcard images for those would be usefull12:15
Wizzupyes12:15
uvos__i know this gets messy12:15
Wizzupso maybe we can manage /etc/inittab with leste-config12:15
uvos__you also need to change boot.cfg12:15
WizzupI think for mz616 we can safely assume people will probably just use sdcards and not te internal emmc12:15
uvos__sure and if not mz617 is presuambly compatable12:16
Wizzupthe one thing lacking for mz61x images -now- is the kernel12:16
Wizzupyeah I think we'll find it all to be very compatible12:16
WizzupI haven't found any differences at all really12:16
Wizzup(apart from modem presumably)12:16
uvos__well mz60x is for sure different in varous ways12:17
uvos__but yeah the sub variants are presumably very samey12:17
Wizzupyeah that is what I meant12:17
Wizzupbtw, please ack that you saw my sphone changes12:17
uvos__i did12:17
WizzupI pushed to master only a minor debian/ change but then the build failed so I just decided to push a build fix to master12:17
uvos__dont worry, i hired the hitman already12:18
Wizzup:D12:18
uvos__so otherwise you  know what to do right?12:20
uvos__for sphone12:20
uvos__add a config to leste-config for it12:20
uvos__and tell me, i can then drop the maemo stuff from the default config12:21
Wizzupoh, so you mean the divert the default sphone.ini ?12:21
uvos__no, add a 20-maemo.ini or so12:21
Wizzupok, I thought we couldn't change the module load line there, did you change that?12:21
uvos__you can change anything12:22
uvos__do tell me if it dosent work12:22
uvos__but anything in sphone.init should be changeable12:22
Wizzupok, so if I add the comm-voicecallmanager via leste-config as a 20-maemo.ini it should work?12:22
uvos__yeah i mean you need to copy the whole modules= line12:22
Wizzupsame for qtloop?12:22
uvos__and overwrite it12:22
uvos__yes12:23
Wizzupok, I'll try that12:23
Wizzupthanks!12:23
uvos__and you can disable the sms feature to12:23
uvos__theres a value for that12:23
uvos__(and dont load the sms ui modules to save some ram)12:23
uvos__for recents to be the entry point (as you would like)12:24
uvos__you need to change the .desktop file atm12:24
uvos__need to figure out how to deal with this12:24
Wizzupyeah that's tricky12:25
Wizzupbtw, for new kernel, I think tony pushed our some more stuff recently, we still have the cpufreq issue with it not showing up right?12:25
uvos__have not tried it recently, sorry12:25
uvos__could be fixed yeah, no idea12:25
Wizzupokay, for the mz61x images themselves we'll need a new kernel build I think12:26
uvos__yes12:26
Wizzupif you could re-add the droid3 dts in there too, that would be good12:26
WizzupI have a local change for it on maemo-6.6-buildeb that I could push somewhere12:26
uvos__it needs to rewirtten because the layout of the dts files changed alot12:26
uvos__but yeah12:26
Wizzupsince 6.6?12:27
uvos__no to 6.612:27
WizzupI did this12:27
uvos__lots of stuff moved around12:27
uvos__great12:27
Wizzuplet me push this somewhere12:27
Wizzuphttps://github.com/maemo-leste/droid4-linux/tree/maemo-6.6-buildeb12:28
Wizzupit also updates this scripts/package/builddeb thing, but maybe you did have that already12:28
uvos__yeah12:28
uvos__btw mesa12:34
uvos__we build or own mesa for pvr anyhow12:34
uvos__we could disable all the drivers besides prv to make it pretty tiny presumably12:35
uvos__why have a drivers for all the desktop dgpus in there, its not like leste devices have pcie slots12:35
Wizzupright we need to rebase on mesa-amber right?12:42
Wizzupwell we do need mesa with other drivers for other devices12:42
Wizzuppinephone for example12:42
Wizzupor the librem soon (looks at sicelo :D)12:42
Wizzupand yes, we could make a special pvr mesa, but it actually costs a lot of time12:43
Wizzupeven to just upgrade mesa and deal with the packaging mess12:43
uvos__Wizzup: we need to split pvr mesa anyhow12:57
uvos__pvr mesa needs to be amber12:57
uvos__while the gallium3d drivers (like for pp) must not be amber12:57
uvos__so special mesa pvr is inevitable12:57
Wizzupright, ok, well, shall we do that for daedalus, or is there a need to do it sooner?13:00
Wizzupbecause I'm not kidding if I say it takes me 1-2 full days to switch us to new mesa, even with no code backporting :p13:00
Wizzupbtw, I think we took a bunch of notes on atrix2 to make some dts changes, I think you hosted those somewhere, right?13:00
uvos__i dont think i have ever hosted any notes13:12
uvos__i only have the related files hosted13:12
uvos__https://uvos.xyz/maserati/stockinfo/13:12
Wizzupyeah that counts I guess13:18
inkygsmarena has this info about mz617: it has gsm connectivity, but it cannot do neither voice nor sms. what does that mean? (i personally won't put a sim card in it anyway).13:40
inkyalso, i think it doesn't list the ram size.13:40
Wizzupit means that you can use it for data13:42
tmlindcool tablet install images sounds great :)13:45
inkyWizzup, oh thank you. but why sms won't work? just curious. or will (should) it work under linux?13:48
inkyalso if you work on it now, what's the ram size?13:48
inkyand the graphics card is powervr?13:48
siceloinky: there are data only modems ... e.g. what's inside those 'mifi' thingies.13:58
siceloof course it may also just be that there's no software for it :-)13:58
Wizzuptony said the modem or tablet hung when issuing sms or call commands iirc14:01
Wizzupuvos: I pushed one more commit to the 6.6 builddeb14:04
Wizzupthere is also 6.6 in experimental https://maedevu.maemo.org/pkgweb/chimaera-experimental/main/binary-armhf/linux-image-omap.html14:05
Wizzupbut I think this is an older version, without droid3 stuff, not that it matters14:05
buZzWizzup: searched for those carmounts yet?14:16
WizzupbuZz: can only find droid3 ones14:18
buZzaw :(14:19
Wizzupbut I am going to the US in ~4-5 days, so ...14:19
Wizzupfreemangordon: ping14:48
sicelo< Wizzup> or the librem soon (looks at sicelo :D)15:01
* sicelo looks outside the window :p15:01
Wizzup:p15:08
Wizzupuvos: experimental has the latest 6.6 based on your work with the d3 stuff mixed in, no btrfs yet20:00
uvosWizzup: check20:00
Wizzupit's not the latest 6.6 code or anything20:01
Wizzupsicelo: today on my mz617 I also did not find the usb0 interface on the tablet to be up21:25
Wizzupit did expose the rndis interface, but did not bring it up nor assign an ip21:25
WizzupI guess I should check if pcsuite-enable.sh fails or something21:26
Wizzuptmlind: thinking about it some more, I think it's pretty unlikely that both my tablets have damaged cables wrt ts not always working21:26
Wizzuptmlind: I could bring in a third one that I haven't opened up to see how that works21:26

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