[04:26:21] *** Joins: krnlyng (~liar@83.175.90.24) [05:01:32] *** Quits: prof_wolfff (~prof_wolf@89.141.51.203.dyn.user.ono.com) (Quit: Bye) [05:26:50] *** Joins: prof_wolfff (~prof_wolf@89.141.51.203.dyn.user.ono.com) [06:26:54] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Disconnected by services) [06:27:04] *** Joins: [7] (~quassel@rockbox/developer/TheSeven) [06:46:59] *** Quits: prof_wolfff (~prof_wolf@89.141.51.203.dyn.user.ono.com) (Quit: Bye) [07:16:17] *** Joins: prof_wolfff (~prof_wolf@89.141.51.203.dyn.user.ono.com) [16:06:54] *** Quits: [7] (~quassel@rockbox/developer/TheSeven) (Ping timeout: 250 seconds) [16:07:23] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [16:37:18] prof_wolfff: I guess for the typical remaining emCORE use cases after an RB bootloader is available for the general public, you won't need libui or a boot menu, but are mostly interested in the USB API and the ability to launch apps through that [16:37:50] so yeah, adding an option to boot an emcore kernel from the HDD seems useful [16:38:37] (that kernel image could also include libui/bootmenu of course, but I see little point in that) [18:32:24] TheSeven: the point is, that it's beautiful :) [18:33:31] TheSeven: do you have the time to look at the trunk emCORE kernel, it crashes on rename() [18:43:57] * TheSeven vaguely remembers seeing that before [18:44:15] do you already have an idea what's going on? [19:45:23] *** Quits: user030949 (~user03099@45.55.165.47) (Quit: WeeChat 0.3.8) [20:07:34] TheSeven: data abort, IIRC [20:07:52] if you do it via emcore.py, it'll crash