<ariellea>
hey, can some one help me as I feel like a bit of a newb. I cannot seem to get a working nv_uboot kernel combo working on my Chromebook Arm. I compiled up on the chromebook Linux 4.0 mainline using exynos_defconfig (I'm on debian so used make-kpkg)
<ariellea>
however when ever I boot it from nv_uboot it resets, is there a prebuilt known good one that isn't the chromeos one I can use to at least get the booting part working
D1337d has joined #linux-exynos
aballier_ has quit [Quit: leaving]
aballier has joined #linux-exynos
dlezcano has quit [Ping timeout: 256 seconds]
dlezcano has joined #linux-exynos
ariellea has quit [Quit: Lost terminal]
D1337d has quit [Ping timeout: 264 seconds]
D1337d has joined #linux-exynos
<Wizzup_>
what chromebook?
amitk has quit [Read error: Connection reset by peer]
amitk has joined #linux-exynos
indy has joined #linux-exynos
D1337d has quit [Read error: Connection reset by peer]
libv has quit [Ping timeout: 272 seconds]
libv has joined #linux-exynos
ssvb has joined #linux-exynos
<WarheadsSE>
^
<daniels>
Wizzup_: you can't change the frequency of each core, no, only each set
<daniels>
Wizzup_: apll and kpll are the functional clocks you change; see drivers/clk/samsung/clk-exynos5420.c
<prahal_>
I do not get why size is set to coherent_dma_mask "+ 1" instead of plain coherent_dma_mask since commit 0c79c81c upstream ... It kills kitten as arch/arm/mm/dma-mapping.c checks the size for <= SIZE_MAX
<prahal_>
that is arm_setup_iommu_dma_ops always exits and dma_ops are never iommu ones