05:41 <Swabbles> steev: the instructions on the wiki do match my set-up.

05:42 <Swabbles> But then again, I don't agree with the boot.txt either, but it's one of the ways to get it to work.

05:42 <Swabbles> Preferably, I would have been able to compile u-boot for snow (without the compilation failing for some stupid reason).

05:43 <steev> How? The instructions say to put the rootfs on p3, and then the boot.txt says the rootfs is p2

05:43 <Swabbles> That's intentional.

05:43 <Swabbles> I don't remember why because you have to look at the env vars.

05:43 <Swabbles> I was confused as well, at first.

05:43 <Swabbles> But then I looked at the default env vars.

05:45 <Swabbles> The rootpart and bootpart are swapped around (and that does work, because the default env vars are like that anyway).

05:46 <Swabbles> Like the default env vars are something like: load linux kernel from rootpart.

05:46 <Swabbles> And use bootpart for the actual rootfs.

05:46 <Swabbles> And it makes sense, if /boot and / were on the same partition.

05:47 <Swabbles> In which case both would be rootpart.

05:47 <Swabbles> That's why, IIRC.

05:50 <Swabbles> Like the actual solution would be to modify the default env to have bootpart/rootpart be sane parameters.

05:51 <Swabbles> But for some reason I can't compile u-boot for snow/spring using the Google Chromium repositories.

14:18 <vishp> hi all, any one have experience bringing up fimc IP on Chromebook2?

14:20 <vishp> Issue is that the kernel pointed to by http://linux-exynos.org/wiki/Samsung_Chromebook_2_XE503C12/Installing_Linux

14:20 <vishp> which is https://chromium.googlesource.com/chromiumos/third_party/kernel.git

14:21 <vishp> doesn't have any support for fimc devices. Hence /dev/videox associated with fimc are not getting enumerated.

14:21 <vishp> Unfortunately, upstream kernel does not boot up on my Samsung Chromebook 2 11"

15:01 <daniels> vishp: you need the drm-bridge patches from ajay kumar to boot on the 11"

15:02 <daniels> vishp: and to enable the parade edp-lvds bridge

15:05 <vishp> daniels: this is to boot the tip kernel? or to enable fimc properly on chrome production kernel(3.8) based?

15:06 <javier__> vishp: that is to have display working using a proper kms/drm driver on mainline

15:07 <javier__> vishp: ChromeOS 3.8 kernel should already have display working (assuming you are building using their kernel config)

15:09 <vishp> javier__, daniels: thanks.. yes I have 3.8 kernel working with display.. For tip kernel, display does not come up yet.. and you info on kms/drm driver makes sense to me now.. thanks

15:09 <javier__> vishp: alternatively you can also use the simplefb driver but for that you should update your u-boot to one that injects the simplefb device node in the FDT

15:10 <javier__> vishp: and also disable the support for the tps65090 regulator driver since the regulators that provides power to the backlight and panel are for that PMIC

15:10 <javier__> but the regulator framework disables it since are not claimed by any hardware so is unused from its pov

15:11 <javier__> s/hardware/driver

15:27 <javier__> vishp: fyi, http://cgit.collabora.com/git/user/javier/linux.git/log/?h=wip/exynos/dp-integ is a branch that you can use to have display working on the 11" Chromebook2 (peach pit)

15:27 <vishp> javier__: nice.. I will give it a shot

15:28 <javier__> ok