**** BEGIN LOGGING AT Wed Oct 16 02:59:58 2013
Oct 16 09:03:16 <bluelightning> morning ant_work
Oct 16 09:03:43 <ant_work> gm
Oct 16 09:03:50 <bluelightning> ant_work: I think we're going to have to revert part of that removal; there is no way to completely do what the MACHINE_DISPLAY_* variables did
Oct 16 09:04:08 <ant_work> chatting with LinusW right now...
Oct 16 09:04:09 <bluelightning> formfactor unfortunately does not put files into the sysroot, so I can't even read them from there at packaging time :/
Oct 16 09:04:13 <ant_work> ah, yes
Oct 16 09:04:22 <bluelightning> maybe that's something to fix in future
Oct 16 09:04:35 <ant_work> question is: why don't we move the formfactor back to machine / include before?
Oct 16 09:04:44 <ant_work> exactly
Oct 16 09:05:08 <bluelightning> I guess most pieces of software don't care to know the values until runtime
Oct 16 09:05:43 <bluelightning> but if like the Opie recipes you want to make some choices about which resources to install into the image based on display size / DPI, formfactor doesn't seem to be able to help with that currently
Oct 16 09:06:00 <ant_work> hm
Oct 16 09:06:24 <ant_work> I associate OPIE with qvga
Oct 16 09:06:26 <bluelightning> I will probably start a thread on the OE-Core ml about that
Oct 16 09:06:38 <ant_work> and sato already does that
Oct 16 09:06:43 <bluelightning> it was extended to mostly support larger displays as well
Oct 16 09:07:15 <ant_work> I think you can extend MACHINE_FEATURES with the new large screen WXWGA, etc
Oct 16 09:07:29 <ant_work> now we have qvga, use it ;)
Oct 16 09:07:44 <ant_work> if qvga; else defaults
Oct 16 09:10:31 <ant_work> OT: there is smthg strange with linux-yocto-dev. Rercipe seems out of sync with .git tag in the Yocto repo..
Oct 16 09:10:48 <ant_work> linusW just stumbled on that
Oct 16 09:17:44 <bluelightning> the thing is not all of the machines exactly fit a feature; particularly some of the palms have odd display sizes
Oct 16 09:17:56 <ant_work> well, is almost all hardcoded in opie-taskbar-images.inc
Oct 16 09:18:06 <ant_work> (collie is missing)
Oct 16 09:18:40 <ant_work> at thi spoint you could put all this info in a generic .inc
Oct 16 09:19:42 <bluelightning> let's fix it properly post dora branching
Oct 16 09:21:30 <ant_work> ok, then pls pull pending patches and readd MACHINE_GUI & stuff on the top
Oct 16 09:21:52 <ant_work> even in an .inc
Oct 16 09:22:28 <ant_work> included by require conf/distro/include/preferred-opie-versions-1.2.5.inc
Oct 16 09:22:52 <ant_work> yes, I'd readd-it to meta-opie at this point...
Oct 16 09:22:58 <bluelightning> sigh
Oct 16 09:23:07 <ant_work> ..as other hardcodings ;)
Oct 16 09:23:41 <bluelightning> technically this is no more hardcoding than formfactor
Oct 16 09:23:46 <bluelightning> it's just deprecated is all
Oct 16 09:25:40 <ant_work> ehmm..where are the other sized images?
Oct 16 09:25:58 <ant_work> I see only 320x320
Oct 16 09:27:22 <ant_work> bluelightning: anyway, we need the 'same info' for kernel bootlogo and psplash
Oct 16 09:27:50 <ant_work> ofc formfactor for the init scripts
Oct 16 09:28:20 <ant_work> so you're right we need an hook, maybe in sysroot
Oct 16 09:43:38 <bluelightning> just checking, you have 13 commits waiting to be applied, right?
Oct 16 09:43:41 <bluelightning> ant_work: ^
Oct 16 09:43:51 <ant_work> hm..12?
Oct 16 09:44:21 <ant_work> right..13
Oct 16 09:44:49 <ant_work> one has been deprecated
Oct 16 09:45:35 <ant_work> yes, pls skip #59867
Oct 16 09:45:53 <bluelightning> the one you said not to apply already?
Oct 16 09:46:01 <ant_work> yes
Oct 16 09:46:24 <bluelightning> can you check what I've just pushed?
Oct 16 09:46:41 <bluelightning> pretty sure I skipped the right one
Oct 16 09:46:43 <bluelightning> but just to be sure
Oct 16 09:47:24 <ant_work> fin
Oct 16 09:47:25 <ant_work> e
Oct 16 09:47:38 <ant_work> still 4 in queue
Oct 16 09:48:43 <bluelightning> which are those?
Oct 16 09:48:55 <ant_work> mom, I'm checking patchwork
Oct 16 09:49:11 <ant_work> the ones of 15th oct
Oct 16 09:49:28 <ant_work> ah, ok, is just patchwork
Oct 16 09:50:02 <bluelightning> right, it doesn't pick up meta-handheld commits
Oct 16 09:50:59 <ant_work> only the  last of 15th are not archived somehow
Oct 16 09:55:07 <ant_work> bluelightning: is that PIXMAP_SIZE used actually?
Oct 16 09:56:49 <bluelightning> it looks like perhaps not
Oct 16 09:57:19 <bluelightning> will check OE-Classic to see where it stopped being used
Oct 16 09:58:19 <bluelightning> 2007 apparently...
Oct 16 09:58:30 <bluelightning> since then people have just cargo-cult added to the list
Oct 16 09:58:57 <bluelightning> (well, only once)
Oct 16 10:00:57 <bluelightning> ok, nuked, thanks
Oct 16 10:01:10 <bluelightning> I've branched for dora (and dylan) in meta-handheld now FYI
Oct 16 10:01:49 <ant_work> great
Oct 16 10:01:52 <ant_work> bluelightning: now I'd like to 'repair' the IMAGE_CMD_jffs2 and make '-n' optional setting
Oct 16 10:02:02 <ant_work> I'll have to ask for revert of http://cgit.openembedded.org/openembedded-core/commit/meta/classes/image_types.bbclass?id=70a276509f0f006fcc269296afc3dcc88d2825e1
Oct 16 10:02:12 <ant_work> well, not exactly..
Oct 16 10:02:40 <ant_work> I'd keep the '-n' in the default EXTRA_IMAGECMD_jffs in image_types.bbclass
Oct 16 10:03:13 <ant_work> in fact the machines only need to redeclare the EXTRA_
Oct 16 10:05:02 <ant_work> or do you think it is better to remove it from there as well ? This way all the NAND machines would need to specify the extra 'n', maybe as append
Oct 16 10:05:44 <ant_work> I don't want to make it more confuse than it is ;)
Oct 16 10:08:19 <ant_work> ah, ha...
Oct 16 10:08:21 <ant_work> http://cgit.openembedded.org/openembedded-core/commit/meta/classes/image_types.bbclass?id=7c803cea58737ea0abc62cd21c3813d955f07224
Oct 16 10:08:36 <ant_work> this added the '-n' to EXTRA_IMAGECMD_jffs2 ?=
Oct 16 10:09:43 <ant_work> I don't know how to specify that on device has NOR ant the other NAND...like we do for endianness
Oct 16 10:10:07 <bluelightning> hmm, that shouldn't have been accepted as is since it did not even bother to describe why the change was made in the commit message
Oct 16 10:10:45 <ant_work> pls think a bit about the best solution
Oct 16 10:11:12 <ant_work> maybe add JFFS2_CLEANMARKERS = "-n" var?
Oct 16 10:12:30 <ant_work> I'll drink a red wine thinking about it
Oct 16 10:12:32 <ant_work> brb
Oct 16 10:12:54 <bluelightning> red wine at work? or do you mean later? :)
Oct 16 10:41:17 <ant_work> was a short lunch
Oct 16 10:42:57 <ant_work> win helped a bit
Oct 16 10:43:34 <ant_work> the right name for the var in image_types.bbclass could be JFFS2_NOCLEANMARKERS ?= ""
Oct 16 10:44:22 <ant_work> and the machines with NAND will set it to '-n' in machine.conf
Oct 16 10:45:01 <ant_work> seems clear enough
Oct 16 10:46:11 <ant_work> while there, I could think to add the argument for --pad but this is used just by very few
Oct 16 12:55:11 <ant_work> bluelightning: I'm now sure NOR flash was used up to h1900 and h2200
Oct 16 12:55:20 <ant_work> http://www.samsung.com/global/business/semiconductor/news-events/press-releases/detail?newsId=4329
Oct 16 12:55:32 <ant_work> heh  Seoul, Korea on Jul. 30. 2003
Oct 16 12:56:11 <bluelightning> I think it wasn't enabled on some of the Linux ports because of the state of the drivers though
Oct 16 12:57:15 <ant_work> ok, it appears NOR is only used on sa1100 board
Oct 16 12:57:28 <ant_work> collie, h3600, simpad
Oct 16 12:59:33 <ant_work> h3800 too probably
Oct 16 13:06:50 <ant_work> oh, and jornada56x and jornada7xx
Oct 16 13:38:49 <ant_work> bluelightning: I think you could already use  INLINE_PICS = '${@base_contains("MACHINE_FEATURES", "qvga", "pics/inline", "pics-hires/inline", d)}'
Oct 16 13:39:54 <ant_work> but yes, that puppies 320x320 ...
Oct 16 13:50:45 <bluelightning> RFC sent
Oct 16 13:51:15 <bluelightning> that doesn't seem like the proper solution; now we have a stopgap I'd like to figure out how to fix it properly and just do that
Oct 16 13:51:52 <ant_work> ideally all should be specified once in one place
Oct 16 13:52:07 <ant_work> having external formfactor is not th ebest solution imho
Oct 16 13:52:23 <ant_work> at this point, all back in machine.conf...
Oct 16 13:52:55 <ant_work> let's see the what the other devs will say
Oct 16 13:54:33 <bluelightning> right
Oct 16 13:55:49 <ant_work> btw, do you think is worth opening a bug for the JFFS2 story? I was hoping RP would reply soon so to send a patch
Oct 16 14:00:26 <bluelightning> you could open up an enhancement bug I think yes
Oct 16 14:01:23 <ant_work> <linusw_> I can mount the JFFS2 filesystem from a booted initramfs but I cannot execute any binaries on it :-/
Oct 16 14:01:45 <bluelightning> hmm
Oct 16 14:01:51 <ant_work> that's 3600
Oct 16 14:01:56 <bluelightning> why would that be I wonder?
Oct 16 14:02:27 <ant_work> <linusw_> and that is typically due to how it was compiled.
Oct 16 14:02:38 <ant_work> <linusw_> (I would be wrong)
Oct 16 14:02:38 <ant_work> <linusw_> my booting initramfs has these flags: -msoft-float -marm -mabi=aapcs-linux -mno-thumb-interwork -mcpu=strongarm1100
Oct 16 14:02:38 <ant_work> <linusw_> is there a way to see the CCFLAGS used during compile?
Oct 16 14:02:47 <ant_work> ....
Oct 16 14:03:15 <ant_work> <linusw_> BTW it might be that I see crashes because I cannot ass -msoft-float or is this default?
Oct 16 14:03:15 <ant_work> <ant_work> is default
Oct 16 14:03:15 <ant_work> <linusw_> OK
Oct 16 14:03:15 <ant_work> <linusw_> that that is not my problem...
Oct 16 14:03:15 <ant_work> <linusw_> trying to disable --fix-v4bx and see what happens
Oct 16 14:03:16 <ant_work> <ant_work> I don't think you have to touch the toolchain
Oct 16 14:03:18 <ant_work> <linusw_> usually these flags cause these crashes though...
Oct 16 14:03:20 <ant_work> <ant_work> it runs ok on collie
Oct 16 14:39:56 <ant_work> heh. .seems h3600 has same flash chips liek collei
Oct 16 14:40:08 <ant_work> http://linux.swoz.net/wearables/linuxplay.html
Oct 16 14:40:15 <ant_work> on collie is LH28F640BF
Oct 16 14:40:34 <ant_work> and is read-only atm :/
Oct 16 14:46:57 <ant_work> hm.. similar  /* 2x Intel 28F640J3A (16MB) */
Oct 16 15:15:39 <ant_work> bbl
**** ENDING LOGGING AT Thu Oct 17 02:59:58 2013