**** BEGIN LOGGING AT Fri Nov 16 02:59:59 2012 Nov 16 14:32:26 bluelightning: I've noticed in the Yocto slides sume uncommon lines appear repeatedly Nov 16 14:32:39 ant_work: which slides? Nov 16 14:32:47 ROOTFS_POSTPROCESS_COMMAND += "remove_packaging_data_files;" Nov 16 14:33:06 https://docs.google.com/viewer?a=v&pid=gmail&attid=0.1&thid=13af8975e60ebd51&mt=application/pdf&url=https://mail.google.com/mail/?ui%3D2%26ik%3D625bf13c53%26view%3Datt%26th%3D13af8975e60ebd51%26attid%3D0.1%26disp%3Dsafe%26zw&sig=AHIEtbRN96-cAigk9DBpSRNg_eEGF42dmg Nov 16 14:33:11 oops, sry Nov 16 14:33:33 link did seem shorter ;) Nov 16 14:34:58 used in the other "hands on intro lab" slide too Nov 16 16:42:36 i've implemented the "pass through" boot option, or "immediate boot", in kexecboot Nov 16 16:42:42 not really sure how to call it Nov 16 16:43:03 so the user would add the keyword IMMEDIATE_BOOT to a kernel section Nov 16 16:43:23 kexecboot will immediately boot that section, without showing the menu Nov 16 16:43:42 the user can override this behavior by holding a specific key, Nov 16 16:43:53 currently i've hardcoded it to KEY_LEFT Nov 16 16:48:06 dromede: Jay7 will appreciate Nov 16 16:48:32 i find it really useful, at least for my usage scenario Nov 16 16:48:59 i mostly want to boot directly to zgrom Nov 16 16:49:21 i dont need to see or use the menu every time i want to use zgrom Nov 16 16:49:28 or any other distro for that matter Nov 16 16:49:39 immediate_boot comes in handy in such cases Nov 16 16:50:10 and if i do want the menu, i just hold the left key while kexecboot scans the partititons Nov 16 16:51:11 and it's not a lot of code, less than 100 lines Nov 16 16:59:19 nice Nov 16 16:59:57 will need to be adapted for no-kbd devices Nov 16 17:00:39 bbl, bye Nov 16 17:02:51 indeed Nov 16 17:03:01 touchscreen support should be trivial to implement in this case Nov 16 18:57:23 dromede: hi Nov 16 18:57:45 dromede: what happens if 2 items have IMMEDIATE_BOOT? Nov 16 18:58:06 will first by priority boot? Nov 16 18:58:57 and btw, may be good idea to stop immediate boot when any key is pressed, not just some special Nov 16 19:00:23 it makes little sense to have more than one section with IMMEDIATE_BOOT set Nov 16 19:00:45 but if there are more than one, the first one encountered will be booted Nov 16 19:01:04 I know, but this may happens when user insert 2 media (CF & SD e.g.) Nov 16 19:01:54 or 2 SD if device support it Nov 16 19:02:04 and btw both my have same priority Nov 16 19:02:13 s/my/may/ Nov 16 19:02:47 anyway your solution is better than no solution at all :) Nov 16 19:02:57 thanks you Nov 16 19:03:39 it doesn't really matter how many devices are scanned Nov 16 19:04:07 if you want to use immediate_boot, you should make sure that it's only defined once, in the section you want Nov 16 19:04:57 as for keypress detection, my first idea was as you suggested, any key should abort the boot sequence and show the menu Nov 16 19:05:45 keypress detection relies on the EVIOCGKEY ioctl Nov 16 19:06:49 ideally EVICGKEY should return a zero filled key bitfiled, if no keys are pressed Nov 16 19:07:43 but on my workstation this wasn't the case, even if i pressed no buttons on the keyboard, the EVIOCGKEY ioctl returned a key bitfield that indicated that some keys are always pressed Nov 16 19:08:18 so i thought that any keypress detection might not be reliable across all machines Nov 16 19:08:31 I mean any key of our 'registered' keys Nov 16 19:08:37 which we have in our code Nov 16 19:08:39 oh :) Nov 16 19:08:49 yeah, ok, that's very easy to do Nov 16 19:20:05 here's the patch if you want to test it: Nov 16 19:20:09 https://github.com/mkatic/kexecboot/commits/immediate_boot Nov 16 19:21:02 dromede: nice! Nov 16 19:21:37 btw, "remove config.h" - i've thought about this too Nov 16 19:21:55 the fb.c refactor patches are in gfx_opt branch Nov 16 19:22:12 well.. I need hackathon :) Nov 16 19:22:24 seems I should organize one myself Nov 16 19:23:48 i want to see a dialog mechanism and user defined menu entries implemented in kexecboot Nov 16 19:23:54 that's what i'm gonna work next Nov 16 19:24:35 dialogs can be used to change section options from the menu Nov 16 19:24:43 edit cmdline, enable options, etc. Nov 16 19:25:00 and user defined menu entries should also be relatively easy to implement Nov 16 19:36:35 this make me think that we may try to use some framebuffer UI library Nov 16 19:36:55 or make another one :) Nov 16 19:37:23 anyway UI polishing is one of planned task as well Nov 16 19:40:53 using a toolkit will probably mean abandoning klibc Nov 16 19:41:07 i doubt that any toolkit will work with klibc Nov 16 20:02:46 yeah Nov 16 20:03:17 well.. let's start with current base and look what will happens :) Nov 16 20:04:24 btw, my friend optimized our 'collections' code (menu lists, xpm lists, etc) Nov 16 20:04:37 but I still haven't seen that changes Nov 16 23:33:59 yes, pxa25x fixed:) ... http://paste.debian.net/210006/ Nov 16 23:34:07 I'll send patch to Eric now Nov 17 00:53:59 heh.. a new bug ? Nov 17 00:54:00 http://paste.debian.net/210018/ Nov 17 00:54:08 RTC :/ **** ENDING LOGGING AT Sat Nov 17 03:00:00 2012