**** BEGIN LOGGING AT Mon Jun 20 02:59:57 2011
Jun 20 12:14:00 <Jay7> ant_work: ping
Jun 20 12:14:12 <ant_work> hello
Jun 20 12:14:19 <Jay7> are you still using classic oe or oe-core?
Jun 20 12:24:14 <ant_work> still classic
Jun 20 12:24:28 <ant_work> until we debug kexecboot it's easier
Jun 20 12:52:52 <ant_work> btw, reverting the 3 patches and adding the guards around menu>current->current seems having resolved for poodle
Jun 20 12:54:18 <ant_work> we should debug the menu/submenu indexing
Jun 20 12:54:29 <ant_work> iirc the submenu id's are static
Jun 20 12:54:36 <ant_work> constant
Jun 20 13:07:24 <Jay7> yes, they are
Jun 20 13:21:17 <ant_work> if they are pre-populated, why NULL then?
Jun 20 13:23:43 <Jay7> there is no current menu level, not id
Jun 20 13:23:57 <Jay7> or menu item
Jun 20 13:24:13 <Jay7> yes, second current is NULL
Jun 20 13:24:23 <Jay7> imho, this is some initialization problem
Jun 20 13:24:29 <Jay7> I should recheck code
Jun 20 16:04:49 <ant_work> Jay7: what remains on the buglist after this menu-fix?
Jun 20 16:05:48 <ant_work> ah, the case gui + tui configured together
Jun 20 16:06:18 <ant_work> and the 'slow' input processing
Jun 20 16:19:31 <Jay7> I have todo list on noteboot
Jun 20 16:19:34 <Jay7> *k
Jun 20 16:19:50 <Jay7> iirc, nothing critical except notified by you
Jun 20 16:20:02 <ant_work> sounds good
Jun 20 16:20:47 <Jay7> yeah..
Jun 20 16:20:48 <ant_work> rest of issues are external (keymaps, kexec, ubifs)
Jun 20 16:21:12 <Jay7> anyway we should debug issues with at least Zaurus keyboards
Jun 20 16:21:28 <ant_work> where do the 2000,250 setting come from?
Jun 20 16:21:43 <Jay7> we may release kexecboot and after start to release Z kernel images
Jun 20 16:21:54 <Jay7> experimental values
Jun 20 16:23:09 <ant_work> these are ok with the old 4x code
Jun 20 16:26:07 <ant_work> try to imagine when we enter SysMenu a 'double-click' is passed and evaluated. what would happen?
Jun 20 16:26:34 <ant_work> (locomo kbd is very different compared to corgi/matrix)
Jun 20 16:27:00 <ant_work> can this lead to a null?
Jun 20 16:28:58 <Jay7> not sure..
Jun 20 16:29:16 <Jay7> is it happens second time?
Jun 20 16:29:19 <Jay7> or only once?
Jun 20 16:29:34 <ant_work> only on 1st it seems
Jun 20 16:30:16 <ant_work> I logged several and was only when entering submenu first time
Jun 20 16:33:32 <Jay7> looks like non-initialized variable
Jun 20 16:34:01 <ant_work> definitely, but why only on poodle?
Jun 20 16:34:44 <ant_work> I can retry to reproduce it on c7x0 but when I was logging nothing happened...
Jun 20 16:34:47 <Jay7> I don't know :)
Jun 20 16:35:01 <Jay7> I will look at code again
Jun 20 16:35:15 <ant_work> I was thinking about flattening the menu...
Jun 20 16:35:45 <Jay7> some UI code should be optimized
Jun 20 16:36:03 <Jay7> e.g. drawing framed & filled rectangle should be one function
Jun 20 16:36:15 <Jay7> not stack of filled rect's
Jun 20 16:36:27 <ant_work> ok, speed would not change much anyway
Jun 20 16:36:48 <ant_work> is this event/input testto check  imho
Jun 20 16:37:29 <ant_work> when you press you feel a delay, like some other operation on th ebg has not yet finished
Jun 20 16:37:38 <ant_work> press = UP/DOWN
Jun 20 16:38:10 <ant_work> with old event code no, snappy
Jun 20 16:38:42 <Jay7> check with TUI
Jun 20 16:38:53 <Jay7> there is no such feeling
Jun 20 16:39:07 <ant_work> I tried long ago and was not slow
Jun 20 16:39:17 <ant_work> I think before event rewrite
Jun 20 16:39:28 <Jay7> I've tested under valgrind
Jun 20 16:39:40 <Jay7> it's fast when FBUI is slow
Jun 20 16:39:52 <ant_work> ah
Jun 20 16:40:14 <ant_work> then is just gui?
Jun 20 16:40:34 <ant_work> tui was ok on poodle while gui was failing
Jun 20 17:15:00 <ant_work> bbl
Jun 20 22:12:31 <ant__> Jay7: ok, I see th eproblem gui+tui
Jun 20 22:12:57 <ant__> tui.c -> #include "res/theme.h"
Jun 20 22:13:21 <Jay7> yes, both are including same unprotected header
Jun 20 22:25:28 * Jay7 -> sleep
Jun 20 22:25:37 <ant__> 'nite
**** ENDING LOGGING AT Tue Jun 21 02:59:56 2011