Re: samsung chromebook
Hi, I'm interested in helping with getting the arm chromebook supported in Debian. I currently have Debian running with the Ubuntu Chromebook kernel. I tried to enable exynos support on the Debian arm multi-platform kernel but 3.10-rc5 doesn't have exynos multi-platform enabled yet. Can someone point me to the patches to enable it? arm-soc/testing/exynos-multiplatform doesn't apply cleanly. Thanks Philipp On Jun 12, 2013 7:40 AM, Marcin Juszkiewicz marcin.juszkiew...@canonical.com wrote: W dniu 11.06.2013 23:34, Konstantinos Margaritis pisze: On Tue, 11 Jun 2013 21:14:00 +0200 Marcin Juszkiewicz marcin.juszkiew...@canonical.com wrote: So I will be able to help but would be nice to get someone else as well. I'm using the chromebook as my main Debian system right now (though on an external USB3 SSD disk, and am really pleased with it. I'm already working on getting d-i working on it, though at a slow pace admittedly, but if there is a proper upstream kernel working that would make things much much easier. When you say a patched version of u-boot, do you have any details of the changes required? Olof Johansson wrote a post about 3.10-rc on Chromebook: https://plus.google.com/u/0/109993695638569781190/posts/bQpzEGG15G8 which points to https://sites.google.com/a/chromium.org/dev/chromium-os/u-boot-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook?pli=1 with u-boot instructions. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b809b9.5000...@canonical.com
Re: samsung chromebook
Philipp Hug phil...@hug.cx writes:
Hi,
Hi,
I'm interested in helping with getting the arm chromebook supported in
Debian.
I currently have Debian running with the Ubuntu Chromebook kernel.
I tried to enable exynos support on the Debian arm multi-platform kernel
but 3.10-rc5 doesn't have exynos multi-platform enabled yet.
Can someone point me to the patches to enable it?
arm-soc/testing/exynos-multiplatform doesn't apply cleanly.
Multiplatform for exynos is atm disabled since commit
4923ee444a39c8b75027ed01a7812e940194dbec so it'll have to wait that
upstream sort that out.
That doesn't mean there's nothing to do. For instance:
- the ucm file doesn't work with alsaucm (solved/workarounded here, see
attached doc. I might send it upstream later) but it remains the issue
of having something enabling or disabling the headphone output when
plugging headphones.
- keyboard mapping stuff so that one can get pg up/down, like what I did
here: http://packages.rtp-net.org/debian/pool/main/x/xkeyboard-config/
but I admit that my change suits probably only my use case... it
doesn't solve the problem when not running Xorg.
- check if there's something to be able to adjust the brightness
according to the light sensor (there's a device supported by the
isl29018 driver)
There are probably other things to do and I guess that other people on
this list will be able to list them too.
Arnaud
SectionVerb {
EnableSequence [
cdev hw:DAISYI2S
cset name='Left Speaker Mixer Left DAC1 Switch' on
cset name='Right Speaker Mixer Right DAC1 Switch' on
cset name='Left Headphone Mixer Left DAC1 Switch' off
cset name='Right Headphone Mixer Right DAC1 Switch' off
cset name='DMIC1 Left Capture Switch' on
cset name='DMIC1 Right Capture Switch' on
cset name='MIC2 External Mic Switch' on
cset name='Left ADC Mixer MIC2 Switch' on
cset name='Right ADC Mixer MIC2 Switch' on
cset name='EQ1 Mode' Default
cset name='DAI1 Filter Mode' Music
]
DisableSequence [
]
Value {
PlaybackPCM hw:0
CapturePCM hw:0
}
}
SectionDevice.Headphone.0 {
Comment Headphone
Value {
JackName DAISY-I2S Headphone Jack
}
EnableSequence [
cdev hw:DAISYI2S
cset name='EQ1 Switch' off
cset name='Left Headphone Mixer Left DAC1 Switch' on
cset name='Right Headphone Mixer Right DAC1 Switch' on
cset name='Left Speaker Mixer Left DAC1 Switch' off
cset name='Right Speaker Mixer Right DAC1 Switch' off
]
DisableSequence [
cdev hw:DAISYI2S
cset name='EQ1 Mode' Default
cset name='EQ1 Switch' on
cset name='Left Speaker Mixer Left DAC1 Switch' on
cset name='Right Speaker Mixer Right DAC1 Switch' on
cset name='Left Headphone Mixer Left DAC1 Switch' off
cset name='Right Headphone Mixer Right DAC1 Switch' off
]
}
SectionDevice.Mic.0 {
comment Microphone
Value {
JackName DAISY-I2S Mic Jack
CaptureControl MIC2
}
EnableSequence [
cdev hw:DAISYI2S
cset name='DMIC1 Left Capture Switch' off
cset name='DMIC1 Right Capture Switch' off
cset name='Left ADC Mixer MIC2 Switch' on
cset name='Right ADC Mixer MIC2 Switch' on
]
DisableSequence [
cdev hw:DAISYI2S
cset name='Left ADC Mixer MIC2 Switch' off
cset name='Right ADC Mixer MIC2 Switch' off
cset name='DMIC1 Left Capture Switch' on
cset name='DMIC1 Right Capture Switch' on
]
}
Re: samsung chromebook
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 W dniu 11.06.2013 17:47, Joey Hess pisze: It seems all necessary patches to use the arm chromebook have recently landed in the upstream kernel. A few backports may be needed from linux-next to get eg audio working well. The only hardware not working at all is the USB3 port. There are a few wacky things like needing to disable dpms screen blanking, since the backlight can't be turned back on. A patched version of u-boot is also needed. Additional work would be needed to get kvm working too. I'm in contact with the Fedora developer working on this. Is anyone interested in working on getting it well supported in Debian? My Chromebook is in repair right now but once it get back I plan to take a look at 3.10 kernel and it's state on this device. So I will be able to help but would be nice to get someone else as well. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJRt3b0AAoJECbKqQEReiUe/u4QALIhXZcDRTJJ5E7Ro+J2AmwT O/cbaR9ZHxqcxltRZttfdOZ5hYhpXSjtWago5lNY3dWQk+9G01PkNlMi1wnpe9kB 9SPNQWeRdpg1MbmGSWE4jQV/0OSM5gff1Psfunh+GkFvI4EoqFZhi/qkULr4UH11 8qjFNyb5cNuACMsTOFlS+tIFrgrcGB3LaBzSSdKWjgsETweMTCBBsU0+Z01YOqqY Dcntbg+9CcSkCQsXHnnXOkp2goLhOME3IGPsWoTDIjIgOHjdhVWLp6T6aMoG/ci2 uvxAyNDekclxoL3c+TauldY+wxZJpNqOOA4CJsWpfK1PgqaJcG1Hdaf3fLyVR0gT IoTfAKMrf8TSc+cLzmhm72fa5csUjcVpQ9hB7K54JVr1TIKbcpfPhN34gwfwOahr QPp01Yt82mxdT1feQjxQtCrqefw2w5jrh5ygZ2wecR2qnWUqb4VwxlmujAbPW2rJ mcl0qu9bkQbWH7WXx+TdT8PCe3Gu7h99LfJp5j1pnrXTJg8GdfgB2cxkwCaYMGmC VlLU5NscBPZr3MCn3sUKquaBbyWOI7IR7xJt2AxWqcbbNiVvhXzvjdLrdF8x+QZP 6PTsgZTYrp+dQeLAlsOvKm0uE7jrQpvXx6VtMN2KwtNUd6BgQ0l76cE9+McmupAp 1KuKvlTEEqr1jmKX+aRN =RQrO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b776f8.5020...@canonical.com
Re: samsung chromebook
W dniu 11.06.2013 23:34, Konstantinos Margaritis pisze: On Tue, 11 Jun 2013 21:14:00 +0200 Marcin Juszkiewicz marcin.juszkiew...@canonical.com wrote: So I will be able to help but would be nice to get someone else as well. I'm using the chromebook as my main Debian system right now (though on an external USB3 SSD disk, and am really pleased with it. I'm already working on getting d-i working on it, though at a slow pace admittedly, but if there is a proper upstream kernel working that would make things much much easier. When you say a patched version of u-boot, do you have any details of the changes required? Olof Johansson wrote a post about 3.10-rc on Chromebook: https://plus.google.com/u/0/109993695638569781190/posts/bQpzEGG15G8 which points to https://sites.google.com/a/chromium.org/dev/chromium-os/u-boot-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook?pli=1 with u-boot instructions. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b809b9.5000...@canonical.com
