<javier__>
Wizzup: if you generate your .config with $ ./scripts/kconfig/merge_config.sh -r arch/arm/configs/exynos_defconfig arch/arm/configs/ccu_exynos.config
<javier__>
you will have all the needed kconfig options to have eDP/LVDS, HDMI and USB working as well
<javier__>
Wizzup: I don't have a branch for linux-next with all the needed patches, just many branches testing different things so I guess ^ is the more sensible option now
<Wizzup>
Awesome, thanks for that info
<Wizzup>
When I get off work I'll have a look at it :)
<Wizzup>
javier__: We're currently trying to provide a nice document (on the wiki) for people who want to get mainline to work
<chrs_>
yeah a chromebook 2 mainline kernel install wiki would be great
<Wizzup>
After that we're also hoping to document other system components, and if they currently work or not
<Wizzup>
javier__: jw, are you working for some company on this, or just hobby?
<Wizzup>
anyway, thx a lot for the info
<Wizzup>
will look at it soon
<javier__>
Wizzup: awesome, I'll try to get you a list of patches in patchwork on top of linux-next
<Wizzup>
thanks!
<javier__>
I guess linux-next + a list of pwclient git-am commands would be useful indeed
<javier__>
Wizzup: you're welcome
liquidAcid has joined #linux-exynos
<javier__>
Wizzup: answering your question about which company I work for, it's collabora which you can already see from the git repo :)
liquidAcid has quit [Quit: Leaving]
si1v3r_ has joined #linux-exynos
<chrs_>
what does collabora do?
<javier__>
chrs_: it's a consulting company specialised in FOSS
<chrs_>
and you do embedded too?
<javier__>
chrs_: we do embedded as well
<si1v3r_>
Would this be a good place to ask about a samsung chromebook kernel?
<si1v3r_>
I git cloned the repo, ran make exynoxdefconfig, ran make modules uImage dtbs, and make modueles_install, then copied the uImage to /boot/vmlinux.uimg. u-boot seems to pick the kernel up but it does not output anything after loading it.
<si1v3r_>
I got similar results using a stock torvalds kernel. Not sure what else is needed to make it work.
<Wizzup>
si1v3r_: what guide did you follow exactly
<Wizzup>
and what chromebook do you have
<si1v3r_>
I havn't really been following a guide
<si1v3r_>
I have a samsung chromebook. the dual 1.7 one.
<si1v3r_>
I'm using arch's repacked google 3.4 kernel right now with debian.
<Wizzup>
I'll help you out later
<Wizzup>
bbl :)
<si1v3r_>
Sure
<si1v3r_>
Thanks
<libv>
mdrjr: is odroid this time going to donate some hw to developers, like for instance the linux-exynos project?
<mdrjr>
libv: and you are talking about what board ?
<libv>
any really, but specifically the one that is due
<mdrjr>
libv: if we are talking about XU3, we didn't had much ES samples to donate.. only 6 units. that some people had been contacted that they will receive.
<libv>
ok
<mdrjr>
and the first batch of production is going to customers who ordered it first.. once a minimum stock is kept I can think in donating to a few selected people
<libv>
well, for linux-sunxi, the cubietech and olimex people have their boards as highly recommended, and they have the most complete support
<mdrjr>
libv: good for those guys.. :) competition is important :)
<libv>
quite a lot of us have this hw, and we of course test our stuff on these devices first, and document these guys best
<si1v3r_>
What hardware is common here?
<mdrjr>
si1v3r_: chromebook
<si1v3r_>
Jolly good then. Been having a hard time finding chromebook hackers.
<si1v3r_>
Any luck with a mainline kernel?
<mdrjr>
I have only the original chromebook.. and its sitting on my shelf of unused hardware.
<libv>
seems like a lot of people are talking about it, and perhaps some are even doing it
<libv>
16:24 < chrs_> yeah a chromebook 2 mainline kernel install wiki would be great
<libv>
it's a wiki, everyone can edit it
<libv>
but if everyone just talks about how great a wiki page about a certain topic would be, and noone goes and creates it, things are not going to advance, now are they?
* Wizzup
ran into an error on the wiki when creating accounts just now
<libv>
Wizzup: still, someone should've complained if they truly were looking to help improve things instead of being purely selfserving
<si1v3r_>
I've mostly been working on this from a bus with very limited bandwidth. Will be happy to wikidump anything useful if I get this working.
<Wizzup>
:)
<Wizzup>
well, not just dump please ;-)
* Wizzup
is working on his chromebook2 atm
<si1v3r_>
My freetime has been gutted so badly I'm doing personal projects from a bus to work. :/
<si1v3r_>
Hmm. So you guys are using google's sources still eh?
<Wizzup>
Currently. But not for much longer.
afaerber has quit [Quit: Verlassend]
<Wizzup>
javier__ told us today that he is using mainline with some patches.
<Wizzup>
On his chromebook2
<Wizzup>
And I'm retty sure it should work on the chromebook 1 as well
<si1v3r_>
I wonder what patches are being used.
<WarheadsSE>
I do look forward to moving to mainline on both chromebooks for Arch
<libv>
WarheadsSE: what is stopping you?
<Wizzup>
si1v3r_: I spoke to javier__ and he'll share the info soon:)
<WarheadsSE>
libv: full functionality, some sort of issue with the emmc stability
liquidAcid has joined #linux-exynos
<libv>
WarheadsSE: why not work on fixing such things?
<si1v3r_>
WarheadsSE: what have you got so far? I'd love to tinker with it.
<Wizzup>
si1v3r_: if you're a little patient we'll have a lot more info
<Wizzup>
but, feel free to poke around ;)
<Wizzup>
meanwhile - try the exynos wiki guide, you need do to some special things for it all to work with uboot
<WarheadsSE>
si1v3r_: so far, its all in the github ;)
<Wizzup>
read: try to get chrome-kernel to work first, then try mainline, esp seeing it's a bit iffy atm
<si1v3r_>
yeah, taste of success would be nice.
<Wizzup>
(try the wiki)
<Wizzup>
(otoh, it took us one week initially for the chromebook2)
<si1v3r_>
I'd sure be cool if I was just having issues with console init. heh
* si1v3r_
boots arch to roll back last kernel stillborn
<Wizzup>
this is possible.
<WarheadsSE>
The chromebook on is still on the 3.4 branch, the chromebook 2 is on teh 3.8 branch, of the chromium git
* Wizzup
uses 3.8 on both
<si1v3r_>
cloning 3.8...
liquidAcid has quit [Quit: Leaving]
<Wizzup>
swabbles: I get errors when creating accounts on the wiki
afaerber has joined #linux-exynos
<si1v3r_>
Huh. Lookie that. 3.8 booted.
<chrs_>
now try 3.16-rcN
tfiga has quit [Remote host closed the connection]
tfiga has joined #linux-exynos
<si1v3r_>
chrs_: 3.16 did not work for me
<si1v3r_>
I got it from kernel.org this morning.
<chrs_>
what happened?
<si1v3r_>
Don't have the notes infront of me, but I tried using the redhat chromebook good config and then running make old config, and I also tried exeynosdefconfig. One reboot looped and one seemed to get stuck at a blank screen.
<si1v3r_>
The blank screen one conceivably could be a backlight issue.
<si1v3r_>
Ok looks like the bootloop one was 3.16 with the rh config.
<si1v3r_>
I don't think I used this guy's latest config
liquidAcid has joined #linux-exynos
liquidAcid has quit [Quit: Leaving]
<javier__>
Wizzup: I just read your linux-exynos wiki, that's a nice write up on how to setup chained nv-u-boot booting
<javier__>
Wizzup: to have a close to mainline kernel you can do the following (commands accommodated to be similar to the one on your Linux kernel section)
<javier__>
and use arch/arm/boot/dts/exynos5420-peach-pit.dtb on your kernel.its
<javier__>
or arch/arm/boot/dts/exynos5800-peach-pi.dtb if you have Peach Pi instead
<javier__>
Wizzup: that info + the linux-exynos wiki page should be enough to boot a mainline kernel
<javier__>
Wizzup: I didn't added the mali kconfig option to arch/arm/configs/ccu_exynos.config but cherry-picked from git://github.com/exynos-reference/kernel.git the driver and DTS snippets so should work if the option is enabled
<javier__>
Wizzup: most patches from exynos-reference/kernel.git have already been posted so let me know if you need more info, next week I'll try to put together linux-next + the already posted patches to have a more mainline-ish kernel than that 3.16-rc4
<javier__>
si1v3r_, ^
<si1v3r_>
so is mali working?
<javier__>
si1v3r_: it should, I personally haven't tried using mali but AFAIK a co-workers has
<javier__>
si1v3r_: I'm more interested on what's upstreamable
<si1v3r_>
doubt I'll be of much help for a little while. Happy to test things though.
<si1v3r_>
I'm a poor excuse for a kernel tinkerer
<javier__>
no worries, I'm just sharing this info since I told Wizzup that I would do it
<si1v3r_>
:)
<javier__>
fortunately he already did the hardest part that it's putting together a guide on how to boot using a chained nv-u-boot setup
<javier__>
I just shared the tree I'm using :)
<javier__>
leaving for today, let me know if you need more info
<si1v3r_>
the arch linux guys have good uboot instructions
<si1v3r_>
I used those
<javier__>
nice
<javier__>
bye!
<si1v3r_>
later
tfiga has quit [Remote host closed the connection]
<Wizzup>
javier__: thanks. I will fix the wiki and also get these documents on there
<chrs_>
mali works without binary blobs?
<chrs_>
i thought lima wasn't usable yet
<_anomaly_>
hmm?
<javier__>
chrs_: of course you need a user-space EGL blob that is compatible to what's in your kernel but that is a different story
<javier__>
Wizzup: np, let me know if you need any more info from me
<chrs_>
javier__: the ones released by arm will work?
<javier__>
chrs_: they should AFAIK but as I said I haven't tried so I don't know for sure. I can ping a co-worker on Monday though
<chrs_>
i'm trying to figure out how those blobs are labeled "new"
<javier__>
chrs: I'm more interested in the basic support that it's upstreamable rather than having a usable desktop
<chrs_>
so when you say "mali works" you mean, "i see output in screen"?
<chrs_>
i'm just confused, trying to understand
<chrs_>
mali isn't even being used right after you boot and see kernel messages on the screen, right?
<javier__>
chrs_: I said mali should work since I cherry-picked all the mali support that was in the exynos-reference/kernel.git tree
<chrs_>
ah ok
<javier__>
chrs_: I said that display works (eDP/LVDS and HDMI) which is a totally different thing
<javier__>
or rather that's what I tested
<javier__>
chrs_: right, mali is just the GPU side to do 3D hw rendering
<chrs_>
have you seen any eMMC issues?
<javier__>
chrs_: I'm booting from the uSD so I haven't stressed the eMMC tbh
<javier__>
chrs_: and yes, the mali support is for the GPU (3d hw rendering) but the display controller is independent
<javier__>
there is a KMS/DRM driver in mainline for that already (drivers/gpu/drm/exynos)
<libv>
javier__: which co-worker is that?
<chrs_>
with linux-next + patches (not mainline) can use use the binary mali driver from chromeos?
<chrs_>
one use
<javier__>
libv: there are some doing stuff with exynos5 + mali, at least daniels and gkiagia afaik
<libv>
what are they doing, wayland stuff?
<javier__>
chrs_: it really doesn't matter what kernel version you have, the mali driver is pretty much self contained
<javier__>
libv: I think so but I don't tbh, I'm not a gfx guy
<javier__>
libv: you can ask them to find out, sorry :)
<libv>
well, given that mr stone and his friend abused fd.o root and hacked the repository of one of my projects, just to spite me, i don't think i'd find out much.
<chrs_>
uh-oh
tfiga has joined #linux-exynos
<chrs_>
i'm not sure the current mali kernel driver supports T628