**** BEGIN LOGGING AT Sun May 27 02:59:59 2012
May 27 10:14:01 <mrmoku`> JaMa|Off: the image built fine... behaves a bit strange though... still have to look into it via serial console
May 27 11:48:16 <JaMa|Off> mrmoku`: testing on om-gta04?
May 27 11:48:33 <JaMa|Off> mrmoku`: do you see wifi resource in fsoraw? I don't on gta02
May 27 12:07:22 <ayaka> GNUtoo-desktop hello, do you have received that amil
May 27 12:07:28 <ayaka> s/amil/mail
May 27 12:08:47 <ayaka> I can't find out a right way to modify the xorg.conf
May 27 12:45:28 <ayaka> ?
May 27 12:51:05 <mrmoku`> JaMa|Off: on gta04 yeah. Dunno about wifi resource yet. It's the first start wizard which somehow did not work
May 27 12:51:12 <mrmoku`> don't have usb networking either
May 27 12:51:30 <mrmoku`> and had no time yet for the serial console...
May 27 13:18:13 <ayaka> I don't know whether the fb0 copy from android to chroot can make fbset correct config, but I will test it
May 27 13:32:39 <GNUtoo-desktop> ayaka, hi
May 27 13:51:59 <GNUtoo-desktop> hi JaMa|Off 
May 27 13:52:03 <GNUtoo-desktop> I've that now:
May 27 13:52:04 <GNUtoo-desktop> | Requested 'fso-specs >= 2012.05.24.2' but version of fso-specs is 2012.05.24.1
May 27 16:46:26 <JaMa|Off> GNUtoo-desktop: I'm not using fso-autorev, but now with changes for fso-0.11 it should be fixed.. I just haven't tested it
May 27 16:46:42 <GNUtoo-desktop> ok
May 27 16:46:47 <GNUtoo-desktop> in what branch is the fix?
May 27 16:47:01 <JaMa|Off> it was merged on friday
May 27 16:47:12 <GNUtoo-desktop> note the versions.....
May 27 16:47:15 <GNUtoo-desktop> it's not fixed
May 27 16:47:18 <GNUtoo-desktop> it's a new bug
May 27 16:47:23 <GNUtoo-desktop> different from the last time bug
May 27 16:47:31 <GNUtoo-desktop> <GNUtoo-desktop> | Requested 'fso-specs >= 2012.05.24.2' but version of fso-specs is 2012.05.24.1
May 27 16:47:42 <GNUtoo-desktop> both are 2012.05
May 27 16:47:49 <GNUtoo-desktop> before there was a 2012.05 and a 2012.04
May 27 16:48:25 <JaMa|Off> do you have SRCREV 574526b825cca97be072b6369cabb56bf551186d ?
May 27 16:48:48 <GNUtoo-desktop> no
May 27 16:48:54 <GNUtoo-desktop> let me look
May 27 16:49:20 <JaMa|Off> but looks like morphis haven't pushed something to specs repo
May 27 16:49:24 <GNUtoo-desktop> but I'm up to date
May 27 16:49:48 <GNUtoo-desktop> <JaMa|Off> do you have SRCREV 574526b825cca97be072b6369cabb56bf551186d ? -> not in meta-smartphone
May 27 16:50:24 <JaMa|Off> you can downgrade libfso-glib to ce2c775ec207485216a1f9da4f90e0f6bf558cf4
May 27 16:50:28 <JaMa|Off> to fix that
May 27 16:50:42 <GNUtoo-desktop> I'm using autorev
May 27 16:50:57 <GNUtoo-desktop> I guess I have to remove autorev for libfso-glib
May 27 16:51:10 <JaMa|Off> OE @ ~/meta-smartphone $ git checkout shr
May 27 16:51:10 <JaMa|Off> giSwitched to branch 'shr'
May 27 16:51:10 <JaMa|Off> OE @ ~/meta-smartphone $ grep 574526b825cca97be072b6369cabb56bf551186d meta-fso/recipes-freesmartphone/freesmartphone/fso-specs_git.bb
May 27 16:51:14 <JaMa|Off> SRCREV = "574526b825cca97be072b6369cabb56bf551186d"
May 27 16:51:16 <JaMa|Off> hmm
May 27 16:51:24 <JaMa|Off> no uncommited changes here
May 27 16:51:41 <GNUtoo-desktop> I just tought you were talking about meta-shr repository
May 27 16:51:46 <GNUtoo-desktop> the git named meta-shr
May 27 16:51:55 <JaMa|Off> but specs repo don't have commit to bump it to 2012.05.24.2
May 27 16:52:00 <GNUtoo-desktop> so I git git show 574526b825cca97be072b6369cabb56bf551186d in meta-shr
May 27 16:52:02 <GNUtoo-desktop> ok
May 27 16:52:04 <JaMa|Off> so autorev wont work anyway
May 27 16:52:09 <GNUtoo-desktop> yes
May 27 16:52:30 <GNUtoo-desktop> anyway I'm trying to fix firefox and chromium
May 27 16:52:39 <GNUtoo-desktop> + doing a new kernel for gta02
May 27 16:52:52 <JaMa|Off> good
May 27 16:52:57 <GNUtoo-desktop> hoping that 3.4 will have fixed some bugs
May 27 16:53:38 <GNUtoo-desktop> because I'm tired of git bisecting
May 27 16:53:43 <GNUtoo-desktop> it's complicated and very long
May 27 16:53:52 <GNUtoo-desktop> because I bisect for a bug
May 27 16:53:58 <GNUtoo-desktop> then another bug appear during the bisection
May 27 16:54:08 <GNUtoo-desktop> and I've to bisect for the second bug
May 27 16:54:16 <GNUtoo-desktop> but then with merge bases etc...
May 27 16:54:19 <GNUtoo-desktop> it become very hard
May 27 19:27:54 <jake42> GNUtoo-desktop: what kernel where you bisecting before going over to 3.4?
May 27 19:45:31 <GNUtoo-desktop> jake42, I'm already rebasing on top of 3.4
May 27 19:46:51 <GNUtoo-desktop> but the problem I had was boot slowness on top of 3.3
May 27 20:27:12 <jake42> ok
May 27 21:49:49 <GNUtoo-desktop> hmmm
May 27 21:49:59 <GNUtoo-desktop> what is the gta02 regulator already?
May 27 21:50:11 <GNUtoo-desktop> glamo-mci glamo-mci.0: Cannot proceed without regulator.
May 27 21:50:20 <GNUtoo-desktop> gta02-pm-gps gta02-pm-gps.0: probe failed -517
May 27 21:50:22 <GNUtoo-desktop> etc...
May 27 22:00:30 <GNUtoo-desktop> bad defconfig I guess
May 27 22:00:47 <GNUtoo-desktop> I guess I lack some regulator functions like userspace regulator and such
May 27 22:02:49 <PaulFertser> GNUtoo-desktop: regulator is a voltage source.
May 27 22:02:56 <PaulFertser> GNUtoo-desktop: it's in-kernel framework.
May 27 22:03:05 <GNUtoo-desktop> yes but there are some kernel options
May 27 22:03:27 <PaulFertser> I think glamo-mci driver tries to request a regulator by name, but somehow platform data lacks that regulator, and so glamo-mci doesn't proceed.
May 27 22:03:38 <GNUtoo-desktop> ok thanks a lot
May 27 22:03:45 <GNUtoo-desktop> Userspace regulator consumer support (REGULATOR_USERSPACE_CONSUMER)
May 27 22:03:50 <GNUtoo-desktop> that's what I was talking abuot
May 27 22:03:54 <PaulFertser> I do not think this is any relevant :)
May 27 22:03:57 <GNUtoo-desktop> ok
May 27 22:04:48 <PaulFertser> But i can't tell you for sure what's needed, sorry. But the main idea is that drivers request regulators by name and they turn on (if they were off) automatically to start providing electricity to the components. 
May 27 22:05:31 <GNUtoo-desktop> ok
May 27 22:05:44 <GNUtoo-desktop> there are also documentation in the kernel source, I read it some time ago
May 27 22:06:27 <GNUtoo-desktop> I must find more infos on the API change
May 27 22:06:44 <GNUtoo-desktop> because the API changed and most probably I didn't do the change correctly
May 27 22:13:31 <GNUtoo-desktop> I suspect that it's .0 in the regulator name
May 27 22:13:33 <GNUtoo-desktop> like that:
May 27 22:13:44 <GNUtoo-desktop> REGULATOR_SUPPLY("GSM", "gta02-pm-gsm.0"),
May 27 22:13:46 <GNUtoo-desktop> instead of
May 27 22:13:47 <GNUtoo-desktop> REGULATOR_SUPPLY("GSM", "gta02-pm-gsm"),
May 27 22:17:51 <PaulFertser> Probably so, unfortunately, i'm not following. I hope you're on the right track though.
May 27 22:17:55 <PaulFertser> :)
May 27 22:20:09 <GNUtoo-desktop> yes it was that however new problems came up
May 27 22:20:31 <GNUtoo-desktop> [    5.345000] mmc1: host doesn't support card's voltages
May 27 22:20:35 <GNUtoo-desktop> I guess mmc1 is wifi
May 27 22:20:41 <GNUtoo-desktop> like s3c_sdio
May 27 22:20:43 <GNUtoo-desktop> oops
May 27 22:20:47 <GNUtoo-desktop> I mean the s3c mmc
May 27 22:25:18 <GNUtoo-desktop> hmmm
May 27 22:25:23 <GNUtoo-desktop> now it says:
May 27 22:25:25 <GNUtoo-desktop> [    8.160000] mmc0: host doesn't support card's voltages
May 27 22:27:57 <GNUtoo-desktop> hmmm beside there is MMC_SDHCI_MMC and MMC_S3C hmmm
May 27 22:28:59 <PaulFertser> GNUtoo-desktop: on gta02 S3C's mmc is connected to the SDIO wifi and glamo's MCI is to the SD card.
May 27 22:29:27 <GNUtoo-desktop> yes I know
May 27 22:29:36 <GNUtoo-desktop> but something is fishy with the voltage
May 27 22:29:38 <PaulFertser> I'm off unfortunately. Good luck!
May 27 22:30:04 <GNUtoo-desktop> but what I pointed out is that there was 2 drivers for s3c mmc
May 27 22:31:03 <GNUtoo-desktop> thanks for the help!
**** ENDING LOGGING AT Mon May 28 02:59:58 2012