<javier__>
Wizzup: for wifi on snow you can avoid the last patch that adds the DTS snippets in the peach pit
<javier__>
but yes, you need the other 5 patches
<javier__>
Wizzup: si1v3r: for audio, there are some clocks missing in mainline that are not enabled by the asound driver that are used in the chromiumos driver
<javier__>
if I boot with clk_ignore_unused I've sound but only with the headphone audio jack, not with the speakers
<Wizzup>
That's useful info for sure :)
<Wizzup>
And about the touchpad? I'm sorry if I am asking a question that's asked before
<Wizzup>
(for snow)
<Wizzup>
I saw a touchpad branch
<Wizzup>
( wip/exynos/exynos-touchpad
<javier__>
the touchpad is only for the peach pi because the multi-touch protocol used in the atmel chip of the peach pi is not supported in mainline
<javier__>
*the touchpad branch
<Wizzup>
ack
<Wizzup>
(I have no touchpad in snow though)
<Wizzup>
at least not according to xinput and I think dmesg too
<javier__>
did you test with evtest?
<Wizzup>
before I do that: it doesn't show up in xinput list
<Wizzup>
There is no pointer other than the virtual XTEST one
<Wizzup>
[also no /dev/input/eventX for touchpad]
<javier__>
I thought touchpad was working on snow...
* Wizzup
looks around
<Wizzup>
Would you like a dmesg log?
<Wizzup>
(or after the weekend ;)
<Wizzup>
libv: For tamil, what devices have you been working with?
<javier__>
Wizzup: it seems to be an user-space / udev thing on your rootfs because I've the touchpad working on my snow
<Wizzup>
Got a config name handy so I can zgrep my /proc/config.gz?
<Wizzup>
Although I used exynos_defconfig
<javier__>
hrmm [ 2.850478] cyapa 1-0067: set active power failed, -6
<Wizzup>
me was searching for touch and not track (grmh)
<javier__>
I don't have that error, although tbh I just tested with 3.19-rc3 on my snow
<Wizzup>
Without any patches?
<javier__>
yeah, the touchpad had been working for a long time on snow iirc
<Wizzup>
I am using your dp-integ
<Wizzup>
I can try a full power off / power on. But I don't think my chromebook has any hw failures
<Wizzup>
It worked this morning with chromeos kernel at least
<Wizzup>
$ zgrep -i cyapa /proc/config.gz
<Wizzup>
CONFIG_MOUSE_CYAPA=y
<javier__>
Wizzup: yeah, if you didn't have support for the driver enabled, then the compatible string in the DT wouldn't be matched against the driver and the probe function wouldn't be called
<javier__>
ret = cyapa_set_power_mode(cyapa, PWR_MODE_FULL_ACTIVE);
<javier__>
that's the function call that is failing for you
<javier__>
I'll build the dp-integ branch and boot on my snow to see if I see the same issue
<Wizzup>
that would be kind
<Wizzup>
I just have the defconfig enabled, plus some crypto and btrfs
<javier__>
Wizzup: # uname -r
<javier__>
3.18.0-rc5-00024-g2c426c2b4e32
<javier__>
# dmesg | grep cyapa
<javier__>
[ 2.192536] input: Cypress APA Trackpad (cyapa) as /devices/12c70000.i2c/i2c-1/1-0067/input/input0
<javier__>
# evtest /dev/input/event0
<javier__>
Input driver version is 1.0.1
<javier__>
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x1
<javier__>
Input device name: "Cypress APA Trackpad (cyapa)"
<Wizzup>
Hmmmmmmmm
<Wizzup>
$ uname -r
<Wizzup>
3.18.0-rc5-181619-g2c426c2
<Wizzup>
highly irregular
<Wizzup>
One silly thought. I made a zImage, appended dtb, created uImage, and called it vmlinux.uimg because that was what was being loaded by my current u-boot setup
<Wizzup>
Perhaps the current u-boot setup has a poor loadaddr? I guess that's nonsense, but still
<Wizzup>
nah, I guess there's some check on the dtb consistency
<javier__>
Wizzup: the exynos_defconfig has CONFIG_LOCALVERSION_AUTO=y so that's why ./scripts/setlocalversion is called
<javier__>
$ ./scripts/setlocalversion
<javier__>
-00024-g2c426c2b4e32
<Wizzup>
Ah, I wasn't talking about the fact that my uname was slightly different :)
<Wizzup>
I just meant that I was annoyed that it did work for you
<Wizzup>
I'll reboot and see
<javier__>
ok
<Wizzup>
works.
<Wizzup>
That's very odd.
<Wizzup>
I'm sorry for wasting your time, I guess. Hmmmmmmmmm