<libv>
Wizzup: hrm, no changes to the wiki in 30d?
<Wizzup>
No :( I've been planning to pick it up and all the exciting recent stuff
<Wizzup>
but my student-priorities (exams and deadlines) kept coming up
<Wizzup>
in january I will have much more time however
<libv>
well, i just got an xu3
<libv>
so i'll be documenting that
<Wizzup>
cool!
<Wizzup>
actually, after coming friday I'll be available to pick up a lot of issues / stuff in general
<libv>
well, my rant of last fosdem and your valiant response to it was kind of hoping for more people working the wiki and gathering all the knowledge neatly
<libv>
sadly, it seems mostly you doing the work :(
<libv>
90d ago :(
<Wizzup>
Well, there are a lot of people active within this channel that are doing much more work than me
<Wizzup>
It's partially a problem of not pushing people well enough and not enough guidelines, structure I think
<Wizzup>
and there are some people documenting stuff, but only on a distro specific wiki
<Wizzup>
so it's still quite fragmented
<libv>
right, you need a proper wiki nazi like the one guy who does that for sunxi
<libv>
(me.)
<Wizzup>
I guess so, yeah
<Wizzup>
but I have an odroid u2,chromebook1, chromebook2 so I can document those -further- relatively soon
<Wizzup>
I've at least been failing to be a proper wiki nazi :)
<libv>
hrm, bugger. i forgot to order another uart module
<libv>
i have the chromebook1, odroid-x2 and now the xu3
* libv
blows the dust of his x2, it's been a year :(
<Wizzup>
oh, I should also have another U3 somewhere
<Wizzup>
but they're basically the same as the U2
<Wizzup>
Swabbles did some nice work on the wiki trying to unify the setup for the chromebooks at least
<Wizzup>
It scared me away a bit, because it took some times to get used to, but it seems nice
<Wizzup>
but it is in desperate need of updating
<Wizzup>
I think I'll have to contact the sunxi guy once more and poke him about the anti-spam plugins
<Wizzup>
so we can have reg -free- again, instead of limited (this is largely my fault)
<libv>
Turl, or mnemoc?
* Wizzup
doesn't know
<Wizzup>
regardless -- in a few days from now I should have time
<Swabbles>
libv: I've mostly been busy with some IRL stuff, so I haven't had the time yet.
<Swabbles>
I've been fiddling around with the Acer Chromebook CB5, though.
<Wizzup>
which is not exynos ;)
<libv>
Swabbles: you've strayed :p
<libv>
(says the sunxi wiki nazi in the exynos channel)
<Wizzup>
everyone is equally welcome ;)
<libv>
:)
<Swabbles>
Well, the thing is, I now have some idea of how to set up a common guideline.
<Swabbles>
Mostly because the Acer Chromebook uses Coreboot instead of U-Boot (so I had to deal with that).
<libv>
a bit like the new device howto on sunxi?
<Swabbles>
Well, only for the Chromebooks (because there is a common way to do things for the ARM Chromebooks, but not outside that).
<libv>
ah, ok
<Swabbles>
Because everyone else uses u-boot instead of vboot.
<libv>
Wizzup: is there any reason why there are no pictures anywhere?
<libv>
Wizzup: or is it simply because noone has bothered with them yet?
<Wizzup>
definitely the latter I think
<libv>
do you guys want me to move things slightly more to how i do it on sunxi?
<libv>
with a template page which lists things in a logical order
<libv>
as opposed to just a random smattering of howtos in any old order
<libv>
which works well when there are only few devices and few howtos
<Wizzup>
Sounds like a good plan, I think
<libv>
let me (in time) do it for XU3, and then impose it on chromebook1
<libv>
sadly i have no android mobile devices to see how things would fit there
* libv
should actually get some
<Wizzup>
What mobile android devices are exynos?
<Wizzup>
I guess most samsung ones
<Swabbles>
Several devices from Samsung.
<Swabbles>
Well not most.
<libv>
samsung galaxies (tablets and phones), then there are a few tablets and phones which use the exynos but are not from samsung
<libv>
lenovo has one, some chinese manufacturers also have some
<Swabbles>
Samsung Galaxy Tab and such tend to be somewhat partitioned, though, some are Exynos, some are Qualcomm, some are TI.
<Wizzup>
I can give you an account, reg. is limited because of spam
<Armnold>
It should be DRAM4 GiB DDR3L
<Wizzup>
[done]
<ukki>
Wizzup: you could also append "And that's about it." to the arndale octa 3.17 kernel comment.
Armnold has quit [Ping timeout: 246 seconds]
<Wizzup>
ukki: I don't think I wrote the arndale page
<Wizzup>
At least, I don't have one :)
ukki_ has joined #linux-exynos
amitk has quit [Quit: leaving]
dlan_ has joined #linux-exynos
dlan_ has quit [Changing host]
dlan_ has joined #linux-exynos
afaerber_ has joined #linux-exynos
dlan has quit [*.net *.split]
ukki has quit [*.net *.split]
daniels has quit [*.net *.split]
afaerber has quit [Ping timeout: 258 seconds]
daniels has joined #linux-exynos
WarheadsSE has quit [Quit: WeeChat 1.0.1]
WarheadsSE has joined #linux-exynos
afaerber_ is now known as afaerber
<afaerber>
Wizzup, I have an Arndale Octa. What's up?
<Wizzup>
afaerber: I don't know why ukki_ mentioned the arndale, but I have no questions about it
<afaerber>
ok
<Wizzup>
thanks for asking though
<afaerber>
it's a bit fragile, things keep breaking on -next, and MCPM is one of the things on the checklist to disable first ;)
<Wizzup>
heh
<javier__>
afaerber: btw, I got wifi working on snow so you may be interested for spring as well
<afaerber>
javier__, cool. what was your workaround?
<Wizzup>
javier__: cool
<javier__>
afaerber: it uses some infrastructure patches from chromiumos to allow the chip power-on sequencing to happen (enable and reset GPIO lines) and keep the reference clock enabled
<javier__>
afaerber: those patches have been nacked by mainline and I don't know what will be the proper way to handle mmc/sdio devices power-on but it maybe interesting for you to have wifi with mainline
<afaerber>
javier__, working in the sense that the patches are now officially in linux-next? or did you succeed in rebasing them yourself?
<javier__>
afaerber: I did rebase his patches since those were for 3.18 iirc and didn't apply cleanly on linux-next
* afaerber
does have a working branch too, just an older one I've been stuck with...
<javier__>
afaerber: working in the sense that I had display :)
<afaerber>
yeah, I have that for something like 20141124 or so
<javier__>
afaerber: yeah, better to wait for him to repost, tomi and laurent said that they agreed with his latest DT binding so hopefully it will make it to 3.20
<afaerber>
apparently the probing fixes were applied differently(?) and something with HDMI shuffled around causing conflicts
<javier__>
afaerber: the probing fix was fwd ported by gustavo padovan and that is working correctly
<javier__>
afaerber: what is missing is vivek's "arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy" patch
<javier__>
afaerber: HDMI is broken in mainline since it needs iommu to work but that is not supported in mainline yet
<javier__>
I pinged kukjin several times about vivek's patch but he did not answer :(
<afaerber>
possibly, I was just mentioning that code changes there cause conflicts when rebasing Ajay's queue
<afaerber>
a recurring pattern ;)
<javier__>
afaerber: oh, yes. I remember having conflicts when rebasing...
<afaerber>
I also need to ping Kukjin about my ODROID-XU DT patches
<javier__>
afaerber: ooi, what other peripheral is missing in spring besides display, HDMI and wifi?
<javier__>
does it have a built-in USB webcam like snow and peach?
<afaerber>
javier__, yes, it does and it's not coming up yet. no clue why, possibly the missing tps65090
<afaerber>
for audio I have patches that I need to send out, but my ucm-profile files broke and I no longer have any audio output...
<javier__>
afaerber: right, I've audio coming from the headphone jack output but no the speakers
<afaerber>
patches should be good though, quite trivial, just a different codec
<javier__>
wonder if is just an alsa config issue or the audio has to be routed or...?
<javier__>
afaerber: cool, will take a look to those
<javier__>
afaerber: fyi, the webcam in peach pit is coming once the tps65090 fet5 regulator (camout) is always-on so I guess that's what is missing in spring
<javier__>
unfortunately the EC does not support normal i2c so adding that support won't be trivial...
<afaerber>
since in my case it worked at some point, it seems to be an alsa ucm config issue - or something random, like the display at boot sometimes being black until either nv U-Boot or kernel drm init
<javier__>
afaerber: I see, I've to admit that I'm very ignorant about ucm/alsa/audio in general
<afaerber>
heh, me too... and the files taken from ChromeOS don't work out-of-the-box since somes names or whatever changed
<javier__>
nod
<afaerber>
for Snow there should be files upstream, but whether they work I don't know
<javier__>
afaerber: in any case, the delta is keeping shorter and shorter so hopefully we should be able to have all peripherals working with mainline exynos chromebooks soon :)
<javier__>
afaerber: cool, thanks for the pointer. I'll add it to my TODO to take a look
<afaerber>
yeah, really appreciate your work, just needed to step a little shorter for other projects and events
<javier__>
thanks, I appreciate your work and help as well ;)
<afaerber>
javier__, re alsa, not at my Chromebook atm, but from what I remember the directory name needs to match the DT-configured name without dashes, limited to 8 chars or so... only then do they get picked up