**** BEGIN LOGGING AT Sat Jul 16 02:59:57 2011 Jul 16 11:54:28 current kexecboot from oe.dev is unusable on tosa Jul 16 11:54:50 no reaction at all Jul 16 11:55:03 seems frozen or no input Jul 16 12:08:27 seems '.:' key acting as enter or space Jul 16 12:08:36 allows to enter system menu Jul 16 12:08:47 but TUI freeze on 'back' Jul 16 12:10:15 and according to flickering we have real problems with events handling :( Jul 16 12:11:51 sh#t :( Jul 16 12:12:06 I'll recheck with 0.5 release Jul 16 12:25:50 well.. old ui is more usable Jul 16 12:26:02 down by left, select by OK Jul 16 12:26:50 but have scary orange vertical lines as with 8-bit memory transfers before.. Jul 16 12:39:14 well.. seems I know why now we have slow UI and semi-working keyboard Jul 16 12:44:56 another half of semi-working keyboard may be inconsistency between linux/input.h and kernel keymap Jul 16 13:01:21 tosa keymap is broken anyway Jul 16 13:01:33 I can't login into console-image Jul 16 21:51:10 hi Jay7 , bluelightning_ Jul 16 21:51:18 hi ant__ Jul 16 21:51:21 hi ant__ Jul 16 21:51:25 hi Jay7 Jul 16 21:51:25 look over log :) Jul 16 21:51:29 hi bluelightning_ Jul 16 21:51:42 ant__: I've played a bit with tosa today.. Jul 16 21:51:51 feeling sad :) Jul 16 21:52:20 ah, I see Jul 16 21:52:50 it seems keyboard are wrecked with 2.6.3x Jul 16 21:53:09 I've asked lumag about this Jul 16 21:53:12 no answer yet Jul 16 21:53:19 probably we need kernel keymap patch as for ben nanonote Jul 16 21:53:51 well, and collie ;] Jul 16 21:53:55 ? Jul 16 21:54:56 bluelightning: have you seen koen proposed to lower meta-oe priority in his scripts? Jul 16 21:55:20 I was about asking: what about dropping Angstrom alltogether? Jul 16 21:55:51 bluelightning: check logs Jul 16 21:55:53 pls Jul 16 21:55:58 which logs? Jul 16 21:56:00 ant__: yes, seems we need keymap patch for Z.. Jul 16 21:56:10 kexecboot Jul 16 21:56:10 or load keymap from initramfs Jul 16 21:56:12 sorry my connection is dodgy right now :/ Jul 16 21:56:32 url is in $topic :) Jul 16 21:56:43 btw, offtopic Jul 16 21:57:06 ant__: I've heard about some electronic clock collision in some province of Italy Jul 16 21:57:12 is it still true? Jul 16 21:57:22 ? Jul 16 21:57:34 unheard Jul 16 21:57:37 hm.. Jul 16 21:57:57 here in EU we have train collisions :/ Jul 16 21:58:29 ah, wait, found smthg Jul 16 21:58:53 heh..Sicily Jul 16 21:59:33 back in June Jul 16 21:59:46 yes, Sicily :) Jul 16 21:59:56 origin could be repairing of a submarine cable Jul 16 22:01:02 yes, since may they are working on the cable connecting Sicily Jul 16 22:01:15 bah Jul 16 22:01:26 to finish the OT's... Jul 16 22:01:29 so do clocks still running faster? :) Jul 16 22:01:39 no idea, Jul 16 22:01:43 ok :) Jul 16 22:01:48 I'll be in Sicily in a month Jul 16 22:01:50 :) Jul 16 22:02:04 will check on Zaurus rtc ;) Jul 16 22:02:33 OT OT: (Google+ == Facebook) ? Jul 16 22:03:07 I stay away for the moment Jul 16 22:03:09 hehe.. Jul 16 22:03:16 cortez invited me into G+ Jul 16 22:03:20 same Jul 16 22:03:24 I'll wait too Jul 16 22:03:39 I have no facebook account Jul 16 22:03:47 and seems will not have G+ one :) Jul 16 22:03:48 neither Jul 16 22:03:56 ant__: what were you wanting to draw my attention to specifically? Jul 16 22:04:02 bah..they already prepare your profile... Jul 16 22:04:13 about th eminimalistic layering Jul 16 22:04:27 what can one do with oe-core only? Jul 16 22:04:37 console-image ? Jul 16 22:05:15 it seems to me that at thi spoint there is an absolute confusion Jul 16 22:05:28 Koen is busy with TI so Angstrom starves Jul 16 22:05:42 oe-core is progressing very well Jul 16 22:05:56 what about the 'no-distro' idea? Jul 16 22:06:10 is a 'mini9mal' implicit nowaday? Jul 16 22:06:25 s/9// Jul 16 22:06:56 e.g. there is any use of the 'contribs' branches atm Jul 16 22:07:03 zareo commits Jul 16 22:07:45 well this Jul 16 22:07:47 er Jul 16 22:08:05 these are all issues... Jul 16 22:08:32 oe-core is distroless to avoid focusing on any particular distro, same reason why it has no real machines Jul 16 22:08:45 k Jul 16 22:09:07 we're not going to get the rich level of support back with all our layers until more people get involved with the new structure Jul 16 22:09:29 right now only a few people are using/contributing to meta-oe Jul 16 22:09:45 and it's not really clear what the split between oe-core and meta-oe is Jul 16 22:09:59 yes, the point is this: why pass through meta-oe if target is oe-core? Jul 16 22:10:11 easier do oe-dev -> oe-core Jul 16 22:10:37 well it depends on whether the item in question is a "core" item or not Jul 16 22:10:46 sure Jul 16 22:10:46 if it is, then yes it should go directly to oe-core Jul 16 22:10:57 now I talk about an hypotetical x11-image Jul 16 22:10:59 the definition of "core" isn't always clear atm though Jul 16 22:12:48 but what is this x11-image? Jul 16 22:14:37 I'm looking at the images provided in oe-core Jul 16 22:15:55 IMAGE_FEATURES += "apps-console-core ${X11_IMAGE_FEATURES}" Jul 16 22:16:04 ok, maybe this one Jul 16 22:16:19 core-image-core Jul 16 22:17:22 not very well named :/ Jul 16 22:18:50 the 'classic' images are provided by Angstrom layer Jul 16 22:19:17 recipes-angstrom/images/c Jul 16 22:19:39 I build console-image as test Jul 16 22:21:27 anyway, we need an updated device-table in oe-core Jul 16 22:21:45 ..and klibc... Jul 16 22:21:58 about this, I talked with fray last night Jul 16 22:22:20 we found out the strange OSError is a failed chown root:root Jul 16 22:24:41 he said the 'fixup_perms' should NOT happen on cross packages... :/ **** ENDING LOGGING AT Sun Jul 17 02:59:57 2011