<Wizzup> after cherry-picking your last commit in wip/exynos/wifi , the peach-pit dts doesn't want to compile
<Wizzup> I have dtc 1.4.1;
<Wizzup> Error: arch/arm/boot/dts/exynos5420-peach-pit.dts:605.50-51 syntax error
<Wizzup> FATAL ERROR: Unable to parse input tree
<Wizzup> scripts/Makefile.lib:282: recipe for target 'arch/arm/boot/dts/exynos5420-peach-pit.dtb' failed
<Wizzup> make[1]: *** [arch/arm/boot/dts/exynos5420-peach-pit.dtb] Error 1
liquidAcid has joined #linux-exynos
<Wizzup> I picked 2d3ec8572c2ccf2fb885f2955d608427523f36be, 32a8c818d5b77c379f33110585b60fb36fdac26d, aab775667536e355236fb5a049775fc6ff4cf4ed, f5fddbdafc4ea79dd441d74bdc9ae0948d5e6e1c, fc6cda418bc33ff26d57a003050849ca1ffac282, 34cdc779df1de3868ef98134c4b4b3ac96e9cc74
<Wizzup> (in that order)
<Wizzup> Also - wifi doesn't want to come up yet it seems
<Wizzup> Time to sleep first I guess
<Wizzup> hurr
<Wizzup> missed one
<Wizzup> had to do a trivial merge for it
<Wizzup> let's hope I don't blow anything up ;)
<Wizzup> Both snow and peach-pi error here: clocks = <&clock CLK_SDMMC3>, <&clock CLK_SCLK_MMC3>, <&max77686 MAX77686_CLK_PMIC>;
<Wizzup> with a syntax error
<Wizzup> right - so after merging aab775667536e355236fb5a049775fc6ff4cf4ed (there was a conflict that I think I solved fine -- merging pinctrl_0 stuff) ; there is a syntax error in the dts files for snow and peach-pit
<Wizzup> Diff compared to 'plain' dp-integ: http://sprunge.us/ZHhW
<Wizzup> The text MAX77686_CLK_PMIC may be the problem - but I really have no clue.
<Wizzup> http://sprunge.us/ZHhW?diff for nicer colours
<javier__> Wizzup: you need to add a label to the max77686 pmic dev node
<javier__> Wizzup: the wifi branch already has this http://cgit.collabora.com/git/user/javier/linux.git/commit/?h=wip/exynos/wifi&id=90fbb382dac5a09e72c3ef4ac7842924fc4f7cc3
<Wizzup> let me cherry-pick that too
<Wizzup> :)
<javier__> don't cherry pick, since I don't know if you already have the change in the s3c RTC driver that needs that change
<Wizzup> what do you mean?
<Wizzup> ah, ack.
<Wizzup> do I also use the rtc / clock line?
<javier__> read the commit message, 546b117fdf17 ("rtc: s3c: add support for RTC of Exynos3250 SoC") added a "rtc_src" property that is required but I don't remember if you already have in 3.18-rc5
<javier__> you just need for your wifi change
<javier__> +#include <dt-bindings/clock/maxim,max77686.h>\
<javier__> and
<javier__> - max77686@09 { + max77686: max77686@09 {
<Wizzup> ack ; sorry. it's late here
<Wizzup> yeah, took those two
<javier__> yeah, although on a second thought the rtc changes shouldn't do any harm if the s3c rtc driver doesn't query the second clock so you *I think* it should be safe to cherry-pick the whole commit
<javier__> going to sleep now, too late here as well, ttyl
<Wizzup> :) thx
<Wizzup> I'll do without the two lines
<Wizzup> I have an 'integration' branch, let's see what I can get to work :)
liquidAcid has quit [Quit: Leaving]
<Wizzup> [ 4.586100] mwifiex: rx work enabled, cpus 2
<Wizzup> [ 4.586297] mwifiex_sdio mmc2:0001:1: Direct firmware load for mrvl/sd8797_uapsta.bin failed with error -2
<Wizzup> [ 4.586301] mwifiex_sdio mmc2:0001:1: Failed to get firmware mrvl/sd8797_uapsta.bin
<Wizzup> much closer
<libv> Wizzup: chromebook, with a 1.5y ubuntu install
<javier__> Wizzup: do you have the firmware under /lib/firmware? -2 is -ENOENT (No such file or directory)
<libv> i still need to get something new on it, and work the wiki
<libv> but for now, it suits my command stream grabbing needs
<Wizzup> javier__: yes, /lib/firmware/mrvl/sd8797_uapsta.bin
<Wizzup> libv: ack. I've just been adding the first pictures to the wiki; and getting some of the devices that I have a bit better documented
<javier__> Wizzup: and you cherry-picked the patch to enable CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y ?
<Wizzup> yes. and I checked for it
<Wizzup> However, I just realised. I didn't do a defconfig again.
<Wizzup> So let me enable that option.
<Wizzup> uf :)
<javier__> Wizzup: I remember having issues and the in-kernel firmware loading to fail so I had to fallback to the user mode helper
<Wizzup> Yes, I saw the commit :) I just didn't run defconfig again
<libv> Wizzup: cool :)
<Wizzup> They don't look as professional as the sunxi wiki (I have the devices on my desk, but it's getting better in the last few days)
<Wizzup> once I've working out the odroid u2 and the chromebook1, I'll have a good idea of how to (fully) rewrite and continue
<javier__> Wizzup: ok, sorry. I missed that line from your comments
<Wizzup> once I've finished documenting* (working out is a dutchish and means something else)
<Wizzup> javier__: :)
<Wizzup> wireles works!
<Wizzup> wireless* even
* si1v3r works on peach pit boot
<Wizzup> cool
indy has joined #linux-exynos
<lancelot> ODROID-U3 .config used with 3.19.0-rc1 and 3.19.0-rc3 - no HDMI video - http://pastebin.com/25RQap8d
<Wizzup> what driver are you using
<Wizzup> for X
<Wizzup> I could not get armsoc and modesetting to work. fbdev/turbofb worked fine.
<Wizzup> do you get any hdmi output at all?
<Wizzup> does /dev/fb0 exist?
<lancelot> http://pastebin.com/A4wwNhv8 Xorg.0.log for 3.19-rc1 and 3.19-rc3
liquidAcid has joined #linux-exynos
<Wizzup> lancelot: tbh it just looks like the kernel has no drm/fb options at all
<Wizzup> are you sure the config is supposed to support it?
<Wizzup> lancelot: does /dev/dri/card0 exist?
<si1v3r> Ok, finally got uboot figured out. Now I need a good kernel. My vmlinux.uimg from linux3.19 just reboots.
<Wizzup> be sure to document it a bit :)
<si1v3r> Everything I've done so far is in the wiki
<si1v3r> Took a looooot of pictures too
* Wizzup looks~~~
<si1v3r> Probably need to move some stuff around. I was working in here: http://linux-exynos.org/index.php?title=Template:ARM_Chromebook/Installing_Linux&oldid=654
<Wizzup> For pictures I think you want http://linux-exynos.org/wiki/Samsung_Chromebook_2_XE503C12
<si1v3r> I fixed the fit image thing and the partitioning
<Wizzup> cool
<si1v3r> Need to start making official pages for each model's install
<si1v3r> like archarm has
<si1v3r> Why'd all the wiki links to outside stuff break?
<si1v3r> Seeing things like [{{{nv_uboot_url}}} nv u-boot]
<Wizzup> Did they break?
<si1v3r> I think they used to work. heh
<Swabbles> si1v3r: eh, why did you change dtb_filename to exynos5420-peach-pit.dts?
<Swabbles> That's now showing up on snow/daisy/peach pi pages as well.
<si1v3r> I'm going to revert that page to an old state and move my changes.
<si1v3r> Lots of chromebook2 links actually point to show stuff it seems.
<si1v3r> *snow
<Swabbles> What do you mean with point to snow stuff?
<si1v3r> Not sure, pretty sure I'm just having id10t errors.
afaerber__ has joined #linux-exynos
afaerber_ has quit [Ping timeout: 255 seconds]
<Swabbles> It says: "Then we can bundle up the kernel and the device tree into a FIT-image (replace <dtb_filename> with exynos5420-peach-pit.dtb):"
<Swabbles> But I have a better idea for that one :P.
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
afaerber__ is now known as afaerber
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos