**** BEGIN LOGGING AT Sun Oct 20 02:59:58 2013
Oct 20 22:35:13 <ant_home> hi lumag
Oct 20 22:35:22 <ant_home> bluelightning, last round of patches
Oct 20 22:35:34 <lumag> hi ant_home.
Oct 20 22:35:59 <lumag> Oh, btw: got a problem with kexecboot 0.6 on tosa/tmiofb
Oct 20 22:36:01 <ant_home> bluelightning, I've kept low profile this time
Oct 20 22:36:18 <ant_home> lumag, I've seen the kb patch btw
Oct 20 22:36:33 <ant_home> what was the problem?
Oct 20 22:37:05 <lumag> ant_home, kexecboot changed mmap() argument from width * bpp * height to line_length * height.
Oct 20 22:37:41 <ant_home> hm.. I remember it, was zeldin's patch?
Oct 20 22:37:43 <lumag> Unfortunately w/o VT (tty being active) on framebuffer, no mode is set (technically tmiofb_set_par is no called) and thus line_length = 0.
Oct 20 22:38:50 <lumag> My intuitive patch to add set_par() call to tmiofb_probe() was declined by framebuffer maintainer.
Oct 20 22:39:02 <lumag> s/intuitive/naive/
Oct 20 22:39:11 <lumag> with the reason 'fix kexecboot instead'
Oct 20 22:39:23 <ant_home> you mean this one?
Oct 20 22:39:24 <ant_home> https://github.com/kexecboot/kexecboot/commit/7d96d9a6d1d00b137416d320a5b00e385513d889
Oct 20 22:47:15 <lumag> I think proper fix would be first to (try to) set mode and only after that to mmap image.
Oct 20 22:47:33 <lumag> ant_home, no
Oct 20 22:49:54 <lumag> Hmm. Can't find it.
Oct 20 22:50:57 <lumag> Maybe I'm mistaken and it is just a coincidence of kernel and kexecboot simultaneous update.
Oct 20 22:52:54 <ant_home> hm.. maybe I've imported the 3.10 recipe too quickly
Oct 20 22:53:33 <ant_home> prolly I didn't reconfigure it properly
Oct 20 22:54:05 <ant_home> I did long tests on with kernel 3.2 and some with 3.8
Oct 20 23:02:27 <lumag> http://www.spinics.net/lists/linux-fbdev/msg12696.html
Oct 20 23:04:21 <ant_home> ok, we add it to linux-yocto-tiny-kexecboot then?
Oct 20 23:16:31 <lumag> ant_home, I think so
Oct 20 23:17:17 <ant_home> it sems fb.c was long declaring
Oct 20 23:17:18 <ant_home>         fb.base = (char *) mmap((caddr_t) NULL,
Oct 20 23:17:18 <ant_home>                                  /*fb_fix.smem_len */
Oct 20 23:17:18 <ant_home>                                  fb.stride * fb.height,
Oct 20 23:22:42 <ant_home> lumag: now with 3.12-rc6 all 'known' patches for Zaurus have been merged
Oct 20 23:23:14 <ant_home> pending is: locomokbd_hack (maybe we can send upstream ?)
Oct 20 23:23:53 <ant_home> is just for kexecboot, normally there are keymaps loaded in userspace
Oct 20 23:24:19 <ant_home> then, for collie, I'm trying to revive the SD/MMC driver
Oct 20 23:24:43 <lumag> ant_home, oh :)
Oct 20 23:24:52 <ant_home> but the framebuffer has still frequency issues
Oct 20 23:25:12 <lumag> it is an spi mode driver, isn't it?
Oct 20 23:25:20 <ant_home> yes
Oct 20 23:25:34 <lumag> ant_home, I have collie, but I don't want to brick it.
Oct 20 23:26:05 <lumag> Do you know of a way to boot original 2.4 and then kexec contnemporary kernels?
Oct 20 23:26:09 <ant_home> lumag, oh, and collie MTD is still Read Only :/
Oct 20 23:26:26 <ant_home> yes, you copy the old zImage on CF/SD
Oct 20 23:26:35 <ant_home> in /boot
Oct 20 23:26:53 <ant_home> and then boot.cfg redirects to another partition
Oct 20 23:27:04 <ant_home> i.e. root=/dev/mtd2
Oct 20 23:28:14 <lumag> ant_home, you mean to flash kexecboot?
Oct 20 23:28:27 <ant_home> yes, but the old one
Oct 20 23:28:38 <ant_home> the 2.6.31 on kexecboot.org
Oct 20 23:28:59 * lumag would like to have original 2.4.
Oct 20 23:29:08 <lumag> as a primary OS
Oct 20 23:29:24 <ant_home> yes, wait a min
Oct 20 23:29:35 <ant_home> http://brooknet.no-ip.com/~lex/public/zaurus/tosa/
Oct 20 23:29:44 <ant_home> he talks about collie, he did the same
Oct 20 23:30:50 <ant_home> what I fear, however, are the differences wrt jffs2
Oct 20 23:31:02 <ant_home> iirc collie original was cramfs 2.4
Oct 20 23:32:16 <ant_home> I have the 'ROM' here if you need
Oct 20 23:33:11 <ant_home> lumag, this is today's situation on collie
Oct 20 23:33:13 <ant_home> http://paste.debian.net/59988/
Oct 20 23:33:43 * lumag did not turn collie on for about two years.
Oct 20 23:34:21 <ant_home> as Read Only is good :p
Oct 20 23:34:48 <ant_home> and err.. locomo-spi is in progress...
Oct 20 23:35:13 <ant_home> at least is compiling now
Oct 20 23:35:52 <ant_home> LinusW and Broonie say that need to be converted to the new buffered interface and do_one_transfer
Oct 20 23:36:30 <lumag> ant_home, I can look on that if/when I have time. But I won't promise that I will have it anytime soon.
Oct 20 23:36:48 <ant_home> thx
Oct 20 23:36:55 <ant_home> I send all patches to OE
Oct 20 23:37:37 <lumag> Regarding patches: I have sent few fixes for pxa/ASoC. At least tosa does not resume properly w/o some of them.
Oct 20 23:38:52 <ant_home> I have marked the patches on LAKML
Oct 20 23:39:07 <ant_home> do these apply to 3.10 as well?
Oct 20 23:40:53 <lumag> Yes
Oct 20 23:41:16 <lumag> I did not send a meta-hh pull request/patches yet.
Oct 20 23:41:51 <ant_home> btw there is linux-yocto-dev: will soon be the 3.12-rcX
Oct 20 23:42:08 <ant_home> is still 3.10 iirc so is nonsense to use it
Oct 20 23:42:23 <lumag> I tend to use self-build kernels.
Oct 20 23:42:38 <lumag> Because it is much easier to tune debug options/features/etc.
Oct 20 23:42:43 <ant_home> sure but linux-yocto is ok for future maintainance
Oct 20 23:42:56 <ant_home> now it is well integrated with OE
Oct 20 23:43:02 <lumag> Yes.
Oct 20 23:43:11 <ant_home> and I can put the common patches back to SRC_URI
Oct 20 23:43:20 <ant_home> (it didn't work back then)
Oct 20 23:43:53 <ant_home> and the KERNEL_FEATURES fragments as well fwiw
Oct 20 23:45:27 <ant_home> the idea is having a modular set of features whit the minimum in <machine>.cfg
Oct 20 23:46:04 <ant_home> but surely 3MB for a collie kernel is a bit too much ;)
Oct 20 23:47:37 * ant_home packing luggages for tomorrow
Oct 20 23:47:39 <ant_home> gn
**** ENDING LOGGING AT Mon Oct 21 02:59:58 2013