**** BEGIN LOGGING AT Thu Dec 06 02:59:59 2012
Dec 06 10:08:00 <ant_work> hi bluelightning
Dec 06 10:08:32 <bluelightning> hi ant_work
Dec 06 10:09:45 <ant_work> seems there is one more chance for collie with Khem's patch (kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC)
Dec 06 10:10:05 <ant_work> the initramfs,though, is built with klibc no-thumb
Dec 06 10:11:51 <ant_work> so afais linux-kexecboot should boot, unless there are kernel bugs
Dec 06 10:15:48 <bluelightning> seemed to me that there were multiple kernel bugs previously
Dec 06 10:16:19 <bluelightning> once I've tried the image you sent me (maybe this evening) we'll know whether or not they are still present
Dec 06 10:33:36 <ant_work> btw I'm resending to you the older 2.6.3x kexecboot kernels I did send to you and Yuri last year
Dec 06 10:36:14 <ant_work> I found out 2.6.38-c3 was working, Yuri took a log
Dec 06 10:38:58 <ant_work> http://pastebin.com/se3BMrmU
Dec 06 10:39:28 <ant_work> "Hi,
Dec 06 10:39:28 <ant_work> here a log of vanilla 2.6.38-c3 booting:  http://pastebin.com/se3BMrmU
Dec 06 10:39:28 <ant_work> This kernel was still lacking the "[PATCH] collie: do actually pass
Dec 06 10:39:28 <ant_work> locomo_info to locomo driver"
Dec 06 10:39:28 <ant_work> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commit;h=34cd2d38db423a991a36d14e9f79e98993addd07
Dec 06 10:39:29 <ant_work> 2.6.39 and 3.0-rc4 are under testing.
Dec 06 10:39:31 <ant_work> Regards"
Dec 06 11:25:33 <ant_work> I've found a 2.6.39 which should have incorporated the patches...I justhope it was text-only
Dec 06 15:08:56 <Jay7> evening
Dec 06 15:09:28 <ant_work> hello Jay7
Dec 06 15:09:46 <ant_work> I see in Russia it is 'quite cold' :/
Dec 06 15:10:20 <Jay7> here is about -4
Dec 06 15:10:48 <Jay7> pretty warm for December :)
Dec 06 15:10:55 <Jay7> and still no snow..
Dec 06 15:11:26 <ant_work> I've seen 700km queue on tv somehwhere
Dec 06 15:12:14 <ant_work> maybe Moskow - St. Pieterburg
Dec 06 15:20:03 <ant_work> Jay7: how ill you merge the branches? patch-by patch?
Dec 06 15:21:00 <Jay7> ant_work: most likely
Dec 06 15:23:14 <ant_work> it seems you can first attack kexecboot.c and menu.c then concentrate on fb code
Dec 06 15:23:37 <ant_work> where there are merge conflicts
Dec 06 15:57:32 <Jay7> I'll ask art2art about current state of his work
Dec 06 16:08:14 <ant_work> the last patches for big endian could be done after the cleanings/fixes I think
Dec 06 16:09:31 <ant_work> or maybe before...you'll have to get the picture :)
Dec 06 16:15:10 <Jay7> big endian?
Dec 06 16:15:17 <Jay7> what patch you mean?
Dec 06 16:15:23 <Jay7> can't remember
Dec 06 16:17:22 <ant_work> is in one of the forks
Dec 06 16:17:35 <ant_work> the most recent
Dec 06 16:18:09 <ant_work> zeldin
Dec 06 16:18:10 <ant_work> https://github.com/kexecboot/kexecboot/network
Dec 06 16:29:05 <Jay7> hm
Dec 06 16:29:16 <Jay7> interesting
Dec 06 16:29:26 <Jay7> let's merge this as well
Dec 06 16:29:41 <Jay7> ant_work: do you know who is zeldin?
Dec 06 16:30:13 <ant_work> not yet ;)
Dec 06 16:31:07 <Jay7> can you please contact him and invite here at least for this weekend?
Dec 06 16:31:34 <Jay7> you may say we are doing kexecboot hackathon :)
Dec 06 16:35:19 <Jay7> ant_work: have you time to talk about last ubifs patch today?
Dec 06 16:35:35 <Jay7> I'd prefer some hours later
Dec 06 16:36:06 <ant_work> around 11 utc ?
Dec 06 16:36:38 <Jay7> now is 16:36 UTC :)
Dec 06 16:37:12 <Jay7> did you mean 23?
Dec 06 16:47:33 <ant_work> yes, maybe 10 UTC if my son decides to sleep
Dec 06 16:47:54 <ant_work> 10 PM
Dec 06 16:48:40 <ant_work> Jay7: around midnight for you
Dec 06 16:49:39 <Jay7> i.e. after 5-6 hours
Dec 06 16:50:08 <Jay7> well.. let's try but I may fall asleep before :)
Dec 06 16:50:57 <ant_work> I'll be around PC in the meantime, try to fire the questions
Dec 06 16:51:15 <ant_work> later when you'll see I'm logged
Dec 06 16:53:34 <ant_work> bluelightning: pls try to pull the kernel patches, I'll give a link to the layer to Bruce for debugging
Dec 06 16:55:20 <ant_work> ah, wrt patches, we should start with upstream tracking one day...
Dec 06 17:06:51 <ant_work> bbl
Dec 06 21:15:37 <ant_home> Jay7: ping
Dec 06 21:15:41 <Jay7> ant_home: hi
Dec 06 21:17:42 <ant_home> looks like I have some time now, dunno in 30 mins :)
Dec 06 21:17:54 <Jay7> well
Dec 06 21:18:07 <Jay7> I need to remember what we doing in last patch :)
Dec 06 21:18:20 <ant_home> ah, right
Dec 06 21:19:04 <ant_home> basically the commandline has two more arguments injected
Dec 06 21:20:08 <Jay7> so, we calling ubiattach somewhere
Dec 06 21:22:05 <Jay7> then trying to find ubi device corresponding to /dev/mtdX
Dec 06 21:22:24 <Jay7> by crawling over sysfs
Dec 06 21:23:18 <Jay7> and then constructing cmdline for kexec with ubi.mtd=<found device no>
Dec 06 21:24:07 <ant_home> and optionally the vid offset
Dec 06 21:26:34 <Jay7> do we have snprintf() in klibc?
Dec 06 21:26:52 <ant_home> yes , pretty usre
Dec 06 21:27:05 * Jay7 is thinking about replacing all that mess by snprintf()
Dec 06 21:28:04 <Jay7> and what's about hardcoded volume id 0?
Dec 06 21:28:09 <Jay7> is it critical?
Dec 06 21:28:36 <Jay7> do you know any scenario when non-zero id may be required to use?
Dec 06 21:29:51 <ant_home> I think most people default using id 0
Dec 06 21:30:56 <ant_home> but you can have more than one volume
Dec 06 21:31:13 <ant_home> realistically less than 10
Dec 06 21:33:57 <Jay7> do you have any idea how to detect free id?
Dec 06 21:35:03 <Jay7> ah, no
Dec 06 21:35:07 <Jay7> not free id
Dec 06 21:35:32 <Jay7> well.. let's leave it for later :)
Dec 06 21:51:17 * Jay7 -> sleep
Dec 06 21:57:00 <ant_home> gn
Dec 06 22:09:24 <ant_home> look at /kernel/Documentation/filesystems/ubifs.txt
Dec 06 23:20:07 <ant_home> bluelightning: I have a nasty git fetcher error I think
Dec 06 23:20:16 <bluelightning> hey
Dec 06 23:20:21 <bluelightning> what's happening?
Dec 06 23:20:36 <ant_home> last oe-core pull broke linux-yocto :/
Dec 06 23:21:17 <ant_home> http://paste.debian.net/214810/
Dec 06 23:22:01 <ant_home> now, -c cleansstate is not of help, I'll try -c cleanall
Dec 06 23:22:28 <ant_home> if I check the git repo in workdir I see those are not updated
Dec 06 23:27:35 <bluelightning> were there any changes to the fetcher recently?
Dec 06 23:27:47 <bluelightning> or is it a linux-yocto specific breakage?
Dec 06 23:28:47 <ant_home> http://cgit.openembedded.org/openembedded-core/log/meta/recipes-kernel/linux/linux-yocto_3.4.bb
Dec 06 23:28:51 <ant_home> 3 changes
Dec 06 23:29:10 <ant_home> but the git hashes seem ok, at least in the yocto git tree
Dec 06 23:29:53 <ant_home> the one-to-last, though, has misgiving title
Dec 06 23:34:05 <ant_home> strange that I have both in /downloads
Dec 06 23:34:27 <ant_home> git.yoctoproject.org.linux-yocto-3.4  & git.yoctoproject.org.linux-yocto-3.4.git
Dec 06 23:40:56 <ant_home> I'm refetching now
Dec 07 00:01:58 <ant_home> now I see b13bef6377719a488293af196236cc290566fad3 refs/heads/standard/base
Dec 07 00:02:05 <ant_home> in packed-refs
Dec 07 00:02:40 <ant_home> fwiw the dir is now  git.yoctoproject.org.linux-yocto-3.4.git
Dec 07 00:03:08 <ant_home> (but one line above I have git.yoctoproject.org.linux-yocto-3.4.git)
Dec 07 00:03:22 <ant_home> (err  but one line above I have git.yoctoproject.org.linux-yocto-3.2)
Dec 07 00:39:11 <ant_home> gn
**** ENDING LOGGING AT Fri Dec 07 02:59:59 2012