| * enyc meows | 08:11 | |
| enyc | not got out the n900 in some time! | 08:12 |
|---|---|---|
| Wizzup | ovh seems back | 10:38 |
| lel | IMbackK opened a pull request: https://github.com/maemo-leste/libmatchbox2/pull/8 (Drop support for _MOTIF_WM_HINTS) | 13:35 |
| uvos | http://uvos.xyz/maserati/screenshots/2021-10-13-133110_960x540_scrot.png | 13:37 |
| uvos | look at gnome contacts with this ^^^ | 13:37 |
| uvos | works with sphone too | 13:37 |
| bencoh | is that standalone, or integrated with <insert osso-something here> ? | 13:41 |
| uvos | gnome-contacts is its own thing ofc, but it uses the same evolution data server data | 13:42 |
| uvos | sphone uses xdg spec to make the 2 interoperate | 13:42 |
| uvos | works with kde-pim too | 13:42 |
| uvos | but the interface is not so phone frendly | 13:42 |
| uvos | i hope to get abook to work with the same method, or with minimal additional (plugin) code | 13:43 |
| Wizzup | there's the osso_abook interface and code in yappari that shows how it can be used I think | 13:47 |
| uvos | yeah that kind of tight integration with abook is something id like to avoid | 13:47 |
| uvos | sphone must not depend on it | 13:47 |
| uvos | at least i will never implement sutch a thing | 13:47 |
| lel | IMbackK opened a pull request: https://github.com/maemo-leste/leste-config/pull/26 (Improve gtk3 usability some) | 13:48 |
| uvos | anyhow this is also needed to make gtk3 mameo /phosh applicaions look good | 13:48 |
| uvos | er gtk3 gnome /phosh | 13:49 |
| Wizzup | the scale, is that d4 specific | 13:52 |
| uvos | no | 13:52 |
| uvos | yes | 13:52 |
| uvos | its maemo specifc | 13:52 |
| uvos | it makes stuff about the size of the gtk2 elements | 13:52 |
| Wizzup | ok, we're also looking the gtk3 styling now btw | 13:52 |
| Wizzup | so not sure how long we need this | 13:52 |
| uvos | sure | 13:52 |
| uvos | i think it makes sense though to have the elements the standard size | 13:53 |
| uvos | i also hate that dpi scale is broken in gtk2 | 13:53 |
| uvos | you could just have gtk3 use the x11 dpi scale to scalle its widgets | 13:53 |
| uvos | but if you do that the font in mameo hacked gtk2 ends up huge | 13:54 |
| uvos | because they kept 96dpi and just scaled up the font for maemo5 | 13:54 |
| uvos | which was very dumb | 13:54 |
| uvos | if your new gtk3 theme has all elements at the correct standart size | 13:54 |
| uvos | instead of just makeing them larger like the gtk2 theme | 13:55 |
| uvos | then dpi scaling will work correctly | 13:55 |
| uvos | and you simply have to sett the correct dpi by telling x the size of the display | 13:55 |
| Wizzup | meridion might be/is looking at some of the gtk3 theming stuff, so if you have other tips/hints, would be good to know | 13:59 |
| freemangordon | tmlind: hmm, why the driver tries to set OCP regs for 3430? Is that ok? | 20:06 |
| freemangordon | like: | 20:07 |
| freemangordon | p, li { white-space: pre-wrap; } OSWriteHWReg(gpvOCPRegsLinAddr, EUR_CR_OCP_DEBUG_CONFIG, EUR_CR_OCP_DEBUG_CONFIG_THALIA_INT_BYPASS_MASK); | 20:07 |
| freemangordon | this is defined for 3630, but there is nothing int the 3430 TRM about those regs | 20:07 |
| uvos | write the register by hand and see what happens? on many devices if its in the register space but not a register often writing to it will just discard the value. | 20:48 |
| freemangordon | uvos: this is behind firewall, you can;t write it like that IIUC | 20:51 |
| uvos | ok | 20:51 |
| uvos | then different story :| | 20:52 |
| freemangordon | not to say this is in address space of SGX regs | 20:52 |
| freemangordon | but we have no description of what register is that | 20:52 |
| freemangordon | for 3430 at least | 20:52 |
| uvos | sure | 20:52 |
| uvos | but if you write to it and read it again and nothing changed | 20:53 |
| uvos | that suggests that its not a real registre | 20:53 |
| uvos | at least thats how many devcies behave i dont know anything about sgx specifics here | 20:53 |
| uvos | or how to even write to its register space as you mentioned | 20:53 |
| freemangordon | ugh: https://pastebin.com/3dQyKgNq | 20:58 |
| freemangordon | this is in fremantle kernel | 20:58 |
| uvos | is this true for your n900> | 20:59 |
| uvos | ? | 20:59 |
| uvos | wrt omap3 stepping | 20:59 |
| freemangordon | yes, it is es2 | 21:00 |
| freemangordon | I mean - all n900 omaps are es2 (or 2.1 not sure what was the latest revision) | 21:00 |
| uvos | ok | 21:00 |
| Wizzup | short downtime of the vm | 22:07 |
| uvos | so at-spi works great | 23:11 |
| uvos | i can see an text or entry event whenever an input field is clicked | 23:12 |
| uvos | in any application | 23:12 |
| uvos | focus:text focus:entry that is | 23:12 |
| uvos | these redhat people are funny people | 23:13 |
| Wizzup | funny how? | 23:13 |
| uvos | wayland makes things more secure... well at-spi allows anyone to get mouse events and be a keylogger | 23:14 |
| uvos | and it helpfully even tells you when the user clicks on a pw field | 23:14 |
| Wizzup | hehe | 23:14 |
| Wizzup | I only remember at-spi from 100% cpu hogging on my arm chromebooks | 23:14 |
| uvos | its really usefullt for us here | 23:15 |
| uvos | him can work everywhere | 23:15 |
| uvos | it even gives you the content of input fields | 23:15 |
| Wizzup | right | 23:15 |
| uvos | so you can place that into the him window | 23:15 |
| Wizzup | yeah | 23:17 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
