*** ChanServ sets mode: +v T4 | 05:22 | |
*** kimmoli is now known as Guest45730 | 06:44 | |
*** Guest45730 is now known as kimmoli_ | 06:48 | |
*** kimmoli_ is now known as kimmoli | 06:49 | |
T4 | DylanVanAssche was added by: DylanVanAssche | 08:16 |
---|---|---|
ghosalmartin | guhl, morning. i mean we could continue building on top of the cm-14.1? | 08:22 |
guhl | ghosalmartin, but we never really had a stable CM14.1 for the chiron | 08:52 |
guhl | some sensors and camera only worked with the legacy kernel from MIUI | 08:53 |
guhl | so i was hoping that we have a better basis now with LOS15 where basically everything works in LOS using the current kernel sources | 08:55 |
ghosalmartin | so was I tbh. but i cant see a way around the config_vt issue. whats odd is that its plagued another device. so is the new LOS kernels breaking it intentionally | 08:59 |
guhl | ghosalmartin, i would not think that it's broken intentionally | 09:00 |
guhl | it's just not needed for android and therefore no one cares | 09:01 |
guhl | so i think something has been messed up in the kernel sources that are used for the android O basis | 09:02 |
guhl | it would be great if we could reproduce this for a device that does have at least some kind of output at boot time | 09:04 |
ghosalmartin | guhl, i can recheck the marlin device to see if theres anything obvious | 09:05 |
guhl | we could try i.e. to build a kernel for the RP3 | 09:06 |
ghosalmartin | do you got one of those? :P | 09:06 |
guhl | rasperry pi 3? | 09:06 |
ghosalmartin | yeha | 09:07 |
guhl | i got 4 of them | 09:07 |
ghosalmartin | ahh...couldnt we emulate with qemu? | 09:07 |
guhl | there is LOS 15.1 for the RP3 | 09:07 |
ghosalmartin | could attempt it and see whats what | 09:07 |
guhl | https://github.com/lineage-rpi | 09:08 |
ghosalmartin | could attempt it and see whats what i guess. is that due to serial access? | 09:10 |
ghosalmartin | mal, the nile device uses aosp doesn't it, not los? | 09:19 |
mal | ghosalmartin: yes, as you can see on mer-hybris | 09:22 |
ghosalmartin | mal: hmm okays ta | 09:22 |
ghosalmartin | guhl, there are 2 aosp ports we could try to use as base | 09:24 |
ghosalmartin | guhl, ill give em a shot today | 09:24 |
Thaodan | ghosalmartin: you could even try mainline on line | 09:37 |
Thaodan | *nile | 09:37 |
ghosalmartin | its not for nile device, but a different one atm | 09:37 |
mal | ghosalmartin: what do you mean you could use aosp as base? where do you get the device repps | 09:44 |
mal | *repos | 09:45 |
guhl | aosp for the chiron? | 09:45 |
ghosalmartin | guhl, possibly, mal for now getting kernel to work properly is a start. i guess id have to either patch manually or use the same ones nile uses? | 09:49 |
mal | why would you assume it works | 09:50 |
ghosalmartin | ah because nile has CONFIG_VT enabled and is aosp. while the two lineage 15.1 devices ive built. marlin and chiron both have big issues with CONFIG_VT so perhaps the lineage-15.1 kernel has just broken CONFIG_VT | 09:51 |
ghosalmartin | i could be grasping at straws. but right now its better than nothing | 09:52 |
Thaodan | is the gpu/drm driver broken or why the issues with CONFIG_VT? | 09:53 |
ghosalmartin | Thaodan, possibly? dont really know personally. someone said something interesting in lineageos "<BtbN> There probably isn't even a driver for it to spawn a VT. Hence the panic." But why leave the flag? | 09:54 |
Thaodan | thats strange. I didn't know that it was device specific | 09:54 |
ghosalmartin | neither did I | 09:55 |
Thaodan | can you log to remote debug console and see a backtrace? | 09:57 |
ghosalmartin | nahh | 09:57 |
ghosalmartin | no ramoops either | 09:57 |
Thaodan | https://wiki.archlinux.org/index.php/Netconsole | 09:58 |
Thaodan | there you could see at least dmesg | 09:58 |
ghosalmartin | might have to give it a look. ta :) | 09:59 |
ghosalmartin | is a panic required for things to be written to ramoops? | 09:59 |
ghosalmartin | guhl, i like your panic module :P | 10:02 |
lbt | Thaodan: wrt the discovery repo - I assume mal or sledges sorted you out? | 10:08 |
guhl | very straight forward .-) | 10:08 |
Thaodan | wrt? | 10:11 |
guhl | ghosalmartin, just so that you don't waste your time: I alread tried the kernel sources of AOSP based OmniROM for the chiron | 10:20 |
guhl | -> same problem | 10:20 |
Thaodan | i adapted the nile Port and fixed some stuff in hybris for that | 10:20 |
ghosalmartin | guhl, well aosp all seem to have the issue that if I build it reboots. with or without verity or VT | 10:21 |
mal | lbt: sledges had an idea what we might be able to use the same repo for all devices using the same sony platform, I think we need to do some testing first before adding the repo to OBS | 10:33 |
Mister_Magister | mal: i ditto in past :P | 10:37 |
mal | Mister_Magister: so you had two devices in same OBS repo? | 10:39 |
Mister_Magister | yeah | 10:39 |
Mister_Magister | they have different patterns so | 10:40 |
Mister_Magister | you have all xperias in one repo dont you? | 10:40 |
Mister_Magister | 2011 xperias | 10:40 |
mal | no, those are all in different OBS repos, they do share the same git repo | 10:41 |
Mister_Magister | ah :P | 10:41 |
Mister_Magister | so i had titan and thea in one cause they had same droid-configs repo | 10:41 |
Mister_Magister | and almost exact same base | 10:42 |
Mister_Magister | but that got too problematic in my case so i dumped that | 10:42 |
Mister_Magister | but thats no problem since one device picks its droid-config-xx that picks its patterns that picks packages specific to it | 10:43 |
Mister_Magister | so i see no problem with that | 10:43 |
abranson | Thaodan: did you get around that rpmbuild problem, or is it still an issue? | 10:51 |
lbt | mal: sledges: that sounds good. Let me know if there's anything needed | 10:52 |
Thaodan | abranson: yes rpm was to old. moved the updated mw packages into my obs repo. I'll try later building against ea again | 10:55 |
Thaodan | lbt: do you know what happened to mer build serice yesterday? | 11:11 |
abranson | Thaodan: ok, updating through these package management upgrades can be tricky, especially now we have tooling, targets and sdk to consider | 11:15 |
Thaodan | abranson: I saw it when sdk broke because of this. rpm needs to be updated first than the rest | 11:17 |
Thaodan | lbt: login is broken in mer buildservice | 11:18 |
mal | Thaodan: I did suggest that you do not update rpm but instead just patch the package that needed newer rpm | 11:22 |
mal | it was a trivial fix to the package spec | 11:23 |
T4 | Migasz was added by: Migasz | 11:56 |
T4 | jersobh was added by: jersobh | 12:29 |
Thaodan | mal: can you look at this? https://github.com/sonyxperiadev/bug_tracker/issues/163#issuecomment-419877500 | 14:27 |
krnlyng | Thaodan, hey, regarding your pull requests. for the discovery specific ones, can you create a bug on mer bugzilla (something like: "add support for sony-discovery/hX213") and use the bug id from that in the commits as you can see in other commits? | 14:53 |
krnlyng | Thaodan, also if it is not too much effort can you try supporting the dual sim model too? there should be only differences in the /vendor partition, /system partition (nothing to do) and in the droid-configs pkg (something to do but you can take an example from pioneer) | 14:55 |
Thaodan | krnlyng: about that bug thing. I already thought that I have to that too after sledges told me that about the commit on droid-configs-nile | 14:56 |
mal | Thaodan: also please do some testing so you will notice the typos and stuff, ref https://github.com/mer-hybris/droid-hal-version-sony-nile/pull/1 | 14:57 |
krnlyng | Thaodan, it would be nice because then your changes would be visible in the changelog | 14:57 |
Thaodan | i'll add the support for h4213 too | 14:58 |
krnlyng | thanks! | 14:58 |
mal | Thaodan: also when adding the single-sim and dual-sim variant add those is separate commits (but in same pull request), that would make review easier | 15:00 |
mal | *in separate commits | 15:01 |
Thaodan | mal: I'll but first I will clean up the discovery and nile stuff | 15:01 |
mal | sure | 15:01 |
Thaodan | should I do that for nile version too? | 15:03 |
mal | Thaodan: one more comment, I prefer that the commit messages start with capital letter after the tag so for example the way h3113 was added "[version] Add support for h3113 device.", you had "[version] support h3213" | 15:03 |
mal | Thaodan: what do you mean? | 15:04 |
Thaodan | i mean should I separate the support for discovery and h3213 on droid hal version nile | 15:05 |
mal | not quite sure what you mean, first commit adds the discovery file and h3213 and the second commit h4213 | 15:09 |
Thaodan | mal: that's what I asked but for the droid hal version nile | 15:18 |
mal | Thaodan: I don't understand the problem, I was referring to that repo | 15:30 |
Thaodan | okay | 15:32 |
Thaodan | can some of you in that mmc bug ? | 15:35 |
Thaodan | *look at the | 15:40 |
Thaodan | https://github.com/sonyxperiadev/bug_tracker/issues/163#issuecomment-41987750 | 15:41 |
piggz | mal: i'll try moving the sensor overrides out of the way and see what happens | 17:01 |
*** ChanServ sets mode: +v T4 | 17:02 | |
piggz | mal: yeah, that config file seems unnescessary | 18:40 |
piggz | mal: no positive effect on compass either | 18:43 |
*** Piece_Maker is now known as Acou_Bass | 21:54 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!