libv_ has joined #linux-exynos
libv has quit [Ping timeout: 268 seconds]
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-exynos
zombah has quit [Ping timeout: 246 seconds]
zombah has joined #linux-exynos
amitk has joined #linux-exynos
paulk-leonov has joined #linux-exynos
libv_ is now known as libv
paulk-leonov has quit [Quit: Quitte]
afaerber has quit [Quit: Ex-Chat]
afaerber has joined #linux-exynos
Tenkawa has joined #linux-exynos
<Tenkawa> Any of you still running recent kernels on a chromebook 1? xe303c12 model. I'm trying to determine if getting internal audio working is feasible ideally with the 4.5 kernel
<Wizzup> I don't think there are changes in audio.
<Tenkawa> so is that a yes or no though?
<Tenkawa> I
<Wizzup> 'no', I think.
<Tenkawa> 've never gotten internal sound to work
<Tenkawa> darn
<Tenkawa> bummer
<Tenkawa> this machine runs great otherwise
<Wizzup> That is because it is known to be buggy stil
<Wizzup> s/stil/still/
<Tenkawa> ah
<Tenkawa> guess I'll still use my iphone for music
<Tenkawa> however this box has become my main workstation for dev/work again
<Tenkawa> running really nicely
<Tenkawa> even for being so sold
<Tenkawa> er old
<Tenkawa> guess I could hook up my usb soundcard
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<Tenkawa> yay i have audio again
<Tenkawa> not optimal however sufficient
<Tenkawa> much better having easily accessed music heehee
<Tenkawa> Wizzup: does the bt on the box work yet in linux by chance? kinda want to use my bt mouse
Vasco_O is now known as Vasco
<Wizzup> I have not tested BT
<Tenkawa> ahh
<Tenkawa> this usb sound card is working great though
<Wizzup> Yep, I also use a USB sound card
<Tenkawa> i have an altec lansing one that i really like
<Tenkawa> I'm just glad to be able to keep using this box
<Tenkawa> its a great little workstation
<Tenkawa> and since 90% of my machines are arm (rpi, olimex,etc) it helps having native tools
<Wizzup> yep, same here
<Tenkawa> i keep putting off getting a cb2
<Tenkawa> still cant see a "need" for it
<Wizzup> I use peach-pi mostly, snow not so much
<Tenkawa> which one is peach-pit? 2?
<Tenkawa> i use snow only
<sjoerd> peach is 2
<Tenkawa> ahhh
<Tenkawa> nowhere to really get the small one around here
* Tenkawa checks microcenter again
<Wizzup> I find peach-pi comfortable in size
<Wizzup> It doesn't feel "large"
<Tenkawa> I'm just weird
<Tenkawa> I really like the small boxes
<Tenkawa> I use 7 and 8 " tablets
<Tenkawa> microcenter here only selling the 13.3" xe503c32
<Tenkawa> and out of stock
<Tenkawa> oh well
<Tenkawa> i just really wish i could use the internal sound card
<Wizzup> you can try to debug it
<Tenkawa> I am highly thinking about it
<Tenkawa> need to figure out if theres even a devicetree node allocated for it
<Tenkawa> seems to be very low interest out there in getting this working
<Wizzup> Tenkawa: there is some interest, there are some mails about it
<Wizzup> it is not a DT problem
<Wizzup> there is some sound, but it is buggy and runs too fast.
<Tenkawa> oh.. well thats good
<Tenkawa> hmmm
<Tenkawa> anyone submitted a good .config to start with?
<Wizzup> defconfig
<Tenkawa> hmm
<Tenkawa> it wasnt showing up for me
<Tenkawa> ahh haa
<Tenkawa> think i know wht
<Tenkawa> er why
<Tenkawa> at least for my problem
<Tenkawa> I was missing a component
<Tenkawa> compiling now
<Wizzup> (as I said, it still will not work satisfactory)
<Tenkawa> true but i can have something to debug
<Tenkawa> i had no starting point before
<Wizzup> Please see the channel logs for prior discussions and emails
<Tenkawa> ok
<javier__> Tenkawa: feel free to fix the issue :)
<javier__> I spent a couple of days trying and didn't succeed
<javier__> now I'm very busy on media land so I don't have anymore to give another try
<Tenkawa> javier__: not my strength but i have a fair amount of time and want to get thisworking
paulk-collins has joined #linux-exynos
<Tenkawa> javier__: now if it were an actual hardware debug issue i'd be much more likely to figure it out
<javier__> Tenkawa: cool, I'll also be very happy if you fix that since I'll be able to remove from my TODO list
<javier__> an item that has been there for a year...
<Tenkawa> heheheheh
<Tenkawa> brb... rebooting to the first kernel with debug and the codec turned back on
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<Tenkawa> well.. it is at least acknowledging now its "trying" to probe it
<Tenkawa> failing miserably
<Tenkawa> but at least its aware its there
<Tenkawa> it fails the probe
<Tenkawa> javier__: is that what it does for you?
<javier__> Tenkawa: no, it probes correctly but fails on playback
<javier__> maybe there is another problem on Snow? I haven't tested Snow on a while and only Peach Pi
<Tenkawa> ahh
<Tenkawa> let me dig into that rev of the dts
<Tenkawa> see if theres anything that sticks out
<Wizzup> How does it fail to probe?
<Tenkawa> thats just what the kernel is reporting in dmesg
<Tenkawa> [ 0.617117] max98090 7-0010: Failed to reset codec: -6
<Tenkawa> [ 0.617304] max98090 7-0010: Failed to read device revision: -1
<Tenkawa> [ 0.617308] max98090 7-0010: ASoC: failed to probe component -1
<Tenkawa> and if the wiki docs the 98090 is the one it "should" be probing
<Tenkawa> er wiki docs are up to date
<Tenkawa> I see something "interesting" I'm going to try
masta has quit [Ping timeout: 248 seconds]
<Tenkawa> how do you determine which rev snow board is in here anyway?
<Tenkawa> brb... trying yet another experiment
Tenkawa has quit [Quit: leaving]
<steev> 98090 is rev5, 98095 is not?
masta has joined #linux-exynos
amitk has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
LiquidAcid has joined #linux-exynos
afaerber has quit [Quit: Ex-Chat]
<steev> hm, what's the secret to video output on peach with 4.5 and multi_v7_defconfig ?
<steev> by video output, i mean, something showing up on the lcd
<javier__> steev: for v4.5 you need a SPI core fix
<Wizzup> I can only say it works OK on 4.2 and 4.4
<steev> javier__: not the same as the 4.6 fix ?
<javier__> steev: oh, sorry I meant mainline/master, v4.5 should boot and display working
<steev> all i did was make multi_v7_defconfig and install it
<steev> is it possible the module isn't being loaded automatically?
<javier__> steev: hmm, interesting. Now that you mention I remember testing v4.5 with exynos_defconfig but no with multi_v7
<javier__> let me try here
<javier__> steev: building now, I'll let you know how it goes
<javier__> sorry for the confusion, too many bugs,fixes and configs :)
<steev> i'm looking at the differences between exynos and multi
afaerber has joined #linux-exynos
<steev> +CONFIG_EXYNOS_VIDEO=y
<steev> +CONFIG_EXYNOS_MIPI_DSI=y
<steev> multi doesn't turn those on
<LiquidAcid> where is EXYNOS_VIDEO from?
<steev> framebuffer devices
<LiquidAcid> ah, shouldn't you use the drm instead?
<javier__> yeah, I was wondering the same. Shouldn't be needed with drm fb emulation...
<steev> well drm is turned on (module); and the screen "flashes" but that's about it
<steev> saw something similar happen on tegra before
<steev> and it had to do with the fact that it was probing for edid before the screen was ready
<LiquidAcid> steev, and you tried to get a log from the system?
<LiquidAcid> steev, preferably with drm.debug=0xff or something
<steev> LiquidAcid: "nothing logged yet"
<steev> it was a fresh install
<LiquidAcid> steev, and concerning these options you named, multi_v7 shouldn't turn them on since they would clash with the drm driver
<steev> so it wasn't even booting
<steev> LiquidAcid: like i said, i was just going through looking to see what the differences are between exynos and multi
<LiquidAcid> steev, then i would get it to boot first, and then tackle the display problem
<steev> ...
<steev> or get display working to see why it isn't booting
<steev> actually
<LiquidAcid> no, actually i mean the other way round
<steev> i do know why
<steev> i wasn't paying attention and made it btrfs which is still not a default filesystem enabled in the kernel
<LiquidAcid> it's going to be much easier if you can get debug output from the drm
<steev> LiquidAcid: indeed; but if it can't mount root, it can't load a module
<steev> so, rebuilding
<LiquidAcid> steev, initrd?
<steev> javier__: sorry for wasting your time
<steev> LiquidAcid: initrd won't matter when btrfs isn't enabled at all
<LiquidAcid> steev, i think initrd comes from rootfs mounting
<LiquidAcid> *before
<steev> yeah, thought of that, and maybe so, but i'm using stock bootloader
<steev> better to just stop being a failure and enable the filesystems i use
<LiquidAcid> sure
<steev> suppose i could build the initrd into the kernel; but that makes it huge
<steev> the only reason i use btrfs is because i use docker, and docker thrashes sdcards when using ext4
<LiquidAcid> i use btrfs on all my rootfs for quite a while now, haven't had a single problem yet
<LiquidAcid> and also for portage
<javier__> steev: no worries, glad that you found the issue
<steev> LiquidAcid: yeah; i just wanted to multi_v7 and go; shoulda told it ext4 from the start, i forget that it's not enabled by default
<steev> javier__: no guarantees, but we shall see
<javier__> steev: Ok
<javier__> BTW, you should propose a patch to enable CONFIG_BTRFS_FS in multi_v7, I guess nowadays should be quite popular along ext4
<javier__> have to leave for today, have a nice evening all!
<steev> javier__: hm, i'm not sure whether i have a good reason to, aside from "it's a popular fs"
zombah_ has joined #linux-exynos
<steev> javier__: yep, that was it, definitely sorry for wasting your time :)
<LiquidAcid> steev, and your display works again as well?
Vasco is now known as Vasco_O
<steev> LiquidAcid: yeah
<steev> can't load the module if it can't load the filesystem it's on
<LiquidAcid> you already said that
<steev> now to see how the wifi performance is, last time it was rather shakey and would drop randomly
<LiquidAcid> good luck with that
<steev> ikr
<steev> to be fair, that happens to me even with the chromeos kernel (but not while IN chromeos)
<Wizzup> wifi seems more stable now for me, as in, no drops
<Wizzup> but it will just get OOMs in the firmware at some point
<Wizzup> I am not sure if I am using the firmware from sys-kernel/linux-firmware, though
LiquidAcid has quit [Quit: Leaving]
<steev> seems fairly stable, but i haven't left it on overnight
paulk-collins has quit [Remote host closed the connection]