<swabbles>
Wizzup: branch should be firmware. truncate is used to pad the binary up to 640K (I am not sure if it is needed, but it is what the cros_bundle_firmware util does as well).
<swabbles>
And I am not sure why you get that error exactly.
<swabbles>
Because I don't get it on my snow chromebook, I do get it on peach (using a Gentoo chroot).
<swabbles>
Wizzup: I think you need =sys-apps/dtc-1.4.0 (instead of 1.3.0).
<Wizzup>
swabbles: I am doing this on my chromebook as well
<Wizzup>
swabbles: aaah.......
<Wizzup>
swabbles: What didn't work wrt kernel?
<Wizzup>
You said ``kernel didn't work yet''
<swabbles>
Same issue when booting it, black screen.
<Wizzup>
No trace?
<swabbles>
Nothing at all.
<Wizzup>
but you do have u-boot shell on the screen?
<Wizzup>
(before loading kernel)
<swabbles>
Yes.
<Wizzup>
wouldn't a serial be nice ;-)
<Wizzup>
and you're sure your u-boot is not simplefb enabled?
<swabbles>
I use like ext2load mmc 1:3 0x42000000 /uImage; ext2load mmc 1:3 0x43000000 /exynos5422-peach-pi.dtb; bootm 0x42000000 - 0x43000000
<swabbles>
I don't even know how to enable/disable simplefb atm.
<Wizzup>
dtc-1.4.0 fixes is.
liquidAcid has joined #linux-exynos
<Wizzup>
\o/ got a kernel to boot with normal u-boot + cmdline force
<Wizzup>
WarheadsSE: ^
<liquidAcid>
tfiga, thanks for the update on the PD situation
<liquidAcid>
i haven't found time yet to test the patch by inki, the 'drm/exynos: hdmi: fix power order issue' one
<tfiga>
liquidAcid: np
<tfiga>
we need to test it too
<tfiga>
but it might be solving the second problem
<swabbles>
WarheadsSE: well, using verified boot, and forcing the bootargs atm.
<tfiga>
although the patch is a bit strange, as it might look like the dpms off might be called twice...
<swabbles>
Something in nv u-boot seems to be broken/missing.
<liquidAcid>
tfiga, it sure looks a bit hacky
<liquidAcid>
but i won't jump to conclusions yet, still have to see if it really fixes the issue for me
<tfiga>
yep
<tfiga>
as for the dependency on LCD0 power domain, we have two solutions in mind
<tfiga>
either disable VP for now or make it a separate device in LCD0 domain
<tfiga>
the only use case for it right now is support for NV12 and NV12MT formats directly
<liquidAcid>
ah, ok, that's one thing i wanted to ask -- from your description it looked that the vp didn't have any function at all
<tfiga>
this might be useful for hardware overlay in future, though
<tfiga>
as the MFC outputs NV12MT
<liquidAcid>
would be indeed be useful to have something that detiles the format in hw
<liquidAcid>
i think the g3d/mali at least can't natively cope with that format
<tfiga>
hmm
ssvb has quit [Ping timeout: 252 seconds]
<tfiga>
liquidAcid: you might be able to resort to two-pass processing using fimc if I'm not mistaken
<tfiga>
yep, it seems to support NV12MT in mem-to-mem mode
<liquidAcid>
i think that is what most video players that use the mfc do atm
<liquidAcid>
xbmc and gstreamer afaik
<liquidAcid>
does someone know if vin-supply properties in the dts also allow for multiple regulators? so something like vmmc-supply = <&ldo4_reg &ldo5_reg>; ?
<swabbles>
Wizzup: what did you put in your boot.txt? (Mine doesn't seem to override the root path)
<Wizzup>
swabbles: give me 5 mins
<Wizzup>
well,15.
<Wizzup>
need to walk to the train
<Wizzup>
swabbles: hey
<Wizzup>
I just set root=/dev/mmcblk1p3 rootwait debug earlyprintk console=tty1 rootwait rw
<Wizzup>
(note that I got rid of the {devpart} thing
<Wizzup>
)
<Wizzup>
swabbles: did you select append, override or force?
<Wizzup>
( for cmdline )
<swabbles>
override.
<Wizzup>
let me check
<Wizzup>
so CONFIG_CMDLINE_FROM_BOOTLOADER=y
<Wizzup>
hm, I see I also had the CMDLINE set to p3 in my config, still... I think I set it to p4 to test. But maybe I forgot (which may mean that p12 doesn't work for config - but I think it should just work)
<swabbles>
Yes @ CONFIG_CMDLINE_FROM_BOOTLOADER=y
<Wizzup>
do you have a CMDLINE set?
<Wizzup>
I'll be home in an hour or so, btw.
<swabbles>
Yes, I do.
<Wizzup>
set to?
<Wizzup>
Or rather, how are you testing overriding the root path?
<swabbles>
I am not trying to get it to work with CMDLINE, I am trying to get it to work with the script.