<bashintosh>
amstan: are there also missing patches on that tree? Got a few missing functions declarations. I am using the arm-eabi-4.6 toolchain to build - also have 4.7 available.
levd has joined #linux-rockchip
nighty-_ has quit [Quit: Disappears in a puff of smoke]
levd1 has quit [Ping timeout: 250 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 248 seconds]
ssvb has quit [Ping timeout: 252 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 246 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 248 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
robogoat has quit [Ping timeout: 264 seconds]
naobsd has joined #linux-rockchip
levd has quit [Remote host closed the connection]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
robogoat has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
levd has quit [Ping timeout: 256 seconds]
<steev>
bashintosh: use 4.7 if it's gnueabi
<steev>
gnueabihf*
<steev>
sounds to me though like you're attempting to use the android compiler
markm has quit [Ping timeout: 256 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 256 seconds]
<bashintosh>
steev: I am using the prebuilts shipped with Android 4.4 - there's also arm-linux-androideabi-4.6 and 4.7. I will try using gcc-4.7-arm-linux-gnueabi
<steev>
uh, yeah, don't use the android cross compilers
<steev>
unless you're running android on it
<steev>
go download a linaro cross compiler
<bashintosh>
yes I am targeting Android with the 3.14 kernel for the Chromebook, for RK3288 hardware
<steev>
heh
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 has quit [Ping timeout: 250 seconds]
levd1 has joined #linux-rockchip
ssvb has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 256 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
<bashintosh>
steev: same business with the linaro toolchain 4.8 arm-none-eabi: complains with https://paste.fedoraproject.org/244063/ about undeclared functions which this patch https://lkml.org/lkml/2013/12/6/1044 seem to address at least by having the functions prototypes in kernel.h - interesting that it doesn't compile with a defconfig which I assume is quite common for Chromebooks (cm_x2xx_defconfig) - I
<bashintosh>
wonder if I am using the right make target? Just using 'make -j8' for now..
<steev>
bashintosh: well if you're using an android compiler, it follows some different code paths. The only thing Chrome devs care about and typically touch are Linux. I can't remember how to explain it exactly.
<steev>
And no, the only config that is "common" for the Chromebook is what comes out of ./chromeos/scripts/prepareconfig <flavor>
<steev>
Where flavor is what's in chromeos/configs/armel (for arm)
<steev>
Something like prepareconfig rockchip
<steev>
chromeos-rockchip or some such
<steev>
So that would get you the config they ship with, then you just add your Android modifications with a make config. And be sure you're passing ARCH=arm
<steev>
To your make statements otherwise the kernel will try to build for the arch you're on.
levd has joined #linux-rockchip
<bashintosh>
thanks, yes I have ARCH=arm - that's how I get all the ARM defconfigs if I invoke 'make help' (from arch/arm/configs) - what's interesting is that I get exactly the same errors by running the Android compiler or Linaro. I'll take a look around if I find more info about the prepareconfig you mentioned
<steev>
I have no idea what the cm_x2xx is
<steev>
For dealing with chromimos stuff, their wiki is pretty good
<bashintosh>
steev: aah good tip!
levd1 has quit [Ping timeout: 248 seconds]
<steev>
I dunno that there is any veyron info up there but they have a great kernel section that's fairly generix
levd1 has quit [Remote host closed the connection]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 256 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
markm has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
field^Mop has joined #linux-rockchip
levd1 has joined #linux-rockchip
lerc has quit [Read error: Connection reset by peer]
leming has quit [Ping timeout: 255 seconds]
levd has quit [Ping timeout: 264 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 265 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
ssvb has quit [Quit: Leaving]
premoboss has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 265 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
sunilmohan_ has joined #linux-rockchip
levd has joined #linux-rockchip
lerc has joined #linux-rockchip
levd1 has quit [Ping timeout: 248 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
levd1 has joined #linux-rockchip
wildea01 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 248 seconds]
<rperier>
ahh!... I think that I found my issue
c0d3z3r0 has quit [Ping timeout: 244 seconds]
<rperier>
I build the "linux-veyron" package from archlinuxarm (in AUR with makepkg -s)
<rperier>
the 4 patches are just not applied at all
<rperier>
in the src dir... I have not... drivers/soc/rockchip for example
<rperier>
ROCKCHIP_USB_UART=y is only found in .config.old...
c0d3z3r0 has joined #linux-rockchip
<rperier>
:/
<rperier>
(probably because the entry in kconfig is not found , if the patch failed)
premoboss has quit [Ping timeout: 265 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
premoboss has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 250 seconds]
markm has quit [Ping timeout: 256 seconds]
markm has joined #linux-rockchip
markm has quit [Ping timeout: 244 seconds]
levd has quit [Ping timeout: 240 seconds]
<rperier>
amstan, mmind00: it works like a charm now :D
<rperier>
hehe :D
<rperier>
(it works better when the required driver is built :p)
<mmind00>
:-D
<mmind00>
rperier: yesterday I've also pieced together the rk3188 part for it
<rperier>
nice
<rperier>
mmind00: btw, it would be useful to replace the "pr_debug" in rockchip_init_usb_uart by a pr_info, because it is very helpful to see that the driver has switched the uart mux
<rperier>
for people who are not sure that the driver is working for example
<mmind00>
rperier: that doesn't really make sense ;-) ... if you need the usb-uart, you don't have a serial console, so you don't see anything
<mmind00>
rperier: and people actually working on that piece of code can enable debugging for this
<rperier>
(this is exactly the problem I had, and I appreciated that there is a pr_info in the patch backported in the archlinux kernel)
<rperier>
or something more understandable saying that the "switch" is on
<mmind00>
rperier: simply do a "define #DEBUG" at the top of the file and debug messages are supposed to be emitted
<mmind00>
rperier: i.e. the kernel log is supposed to not spam and this information is only valuable for people currently working on that driver, so in my book it should be a pr_debug ;-)
<rperier>
it does make sense... if you have an hdmi output or a separated screen... like on a chromebook... you can also enable debug.... yes...
<rperier>
anyway, nice feature
rperier has quit [Quit: No Ping reply in 180 seconds.]
rperier has joined #linux-rockchip
rperier has quit [Changing host]
rperier has joined #linux-rockchip
leming has joined #linux-rockchip
sunilmohan_ has quit [Ping timeout: 264 seconds]
cosm has joined #linux-rockchip
sunilmohan_ has joined #linux-rockchip
cosm has quit [Quit: Leaving]
osopolis has joined #linux-rockchip
<osopolis>
hi all
<osopolis>
I have a K-R42 and would love to use a dvb-s2 usb stick with and linux. Is this doable with this device? Any hel is apreciated
sunilmohan_ has quit [Ping timeout: 252 seconds]
<osopolis>
elp :)
nighty-_ has joined #linux-rockchip
lerc has quit [Ping timeout: 264 seconds]
lerc_ has joined #linux-rockchip
<karlp>
the dvb-s2 stick just depends on general linux support fot the stick.
<osopolis>
There are a few models which run the driver in Userland. I am looking the whole day for a linux that works for that box
<osopolis>
and a dl link
<osopolis>
and a little how to if possible :-)
field^Mop has quit [Ping timeout: 248 seconds]
<karlp>
nto sure what any of that would hav eto do with rockchip then...
<osopolis>
rockchip != k-r42 ?I think it uses that chip
<osopolis>
or am i compeltely wrong
<karlp>
if you're after support getting a dvb-s2 stick running, then it has nothing to do with rockchip.
<karlp>
if you're having problems with bringing up usb on a rockchip board, then you can maybe get some help here, but you're going to have to be running something close to a mainline build of linux on your board.
markm has joined #linux-rockchip
<osopolis>
i c
<osopolis>
It would be a big help if someone is abe to tell me if I can install linux on my k-r42 at all. And what "name" that distro" has. I dunno if that is related to this channel
<ant_thomas>
cristian_c: I think they'll give me a good starting point. If I'm right I should just need to flash the rootfs image to an sd card and go from there. I would have preferred a totally blank server install, but this should do
<cristian_c>
ant_thomas: I've read on the linux-rockchip.info that rk3066 doesb't support boot from sdcard
<cristian_c>
so, it's needed flash kernel+rootfs in recovery partition
<ant_thomas>
I remember a few years ago flashing something to the mk808b stick and writing a separate image to the sd. Whatever the way the picuntu method was
<cristian_c>
ant_thomas: the main issue is if you know or ypu don't know what bootloader you are exactly using on your device
<cristian_c>
usually there is a proprietary bootloader
<cristian_c>
ant_thomas: usually I flash kernel+a basic rootfs in recovery partition
<cristian_c>
and I install ubuntu (or other system) via debootstrap/chroot into sdcard from my computer
<cristian_c>
for booting from sdcard is needed reboot in recovery
<cristian_c>
*to
sunilmohan_ has quit [Quit: Leaving]
wildea01 has quit [Quit: leaving]
<amstan>
bashintosh: we use a patched 4.8, archlinux uses gcc 5.1 to compile it and it works just fine
<amstan>
mmind00: so what's the next step for those dts patches? let them cook for a while?
<mmind00>
amstan: one or two days more and then a pull request for the armsoc people
<cristian_c>
question
<cristian_c>
I've tried gpiodump. I loaded the kernel module and I've checked all the pins, in three modes but I'd like to know what to do in order to make things working. Any ideas?
<karlp>
is rk3066 no boot from sd confirmed? I thought it was just untested...
tizbac_ has joined #linux-rockchip
cristian__c has joined #linux-rockchip
cristian_c has quit [*.net *.split]
tizbac has quit [*.net *.split]
arnd has quit [*.net *.split]
architekt has quit [*.net *.split]
sjoerd has quit [*.net *.split]
tizbac_ is now known as tizbac
cristian__c has quit [Remote host closed the connection]
<bashintosh>
amstan: well CONFIG_TRACING is dependent on ARM arch for what I could find by digging in - by default TRACING is set as enabled in the kernel config - if I try to disable it Kconfig will revert the change when building (with silentoldconfig). But basically using a default config (chromiumos-rockchip) the build fails complaining about missing declarations for trace_clock_gettime() and
<bashintosh>
trace_clock_getres() which according to the issue should be in include/linux/kernel.h
<amstan>
what do you mean by default config?
<amstan>
did you run the script to generate a config?
<amstan>
chromeos tree is a little weird like that
<bashintosh>
yes I used './chromeos/scripts/kernelconfig oldconfig' then './chromeos/scripts/prepareconfig chromiumos-rockchip' which resulted in a .config apparently complete
<amstan>
weird, not sure
<amstan>
maybe there's some more magic in our ebuild
<amstan>
you could always use the archlinux config too
<bashintosh>
I use bare 'make' with no target - I tried 'make zImage' too but fails with the same error. I am gonna try the archlinux toolchain, let's see what happens..
<steev>
the open source kernel drivers part doens't help much as it's still missing the ddk bits
<steev>
which only a partner can get :(
<amstan>
steev: mali in upstream you mean? yeah...
<amstan>
from what i heard from folk like mmind i don't think it'll happen
<steev>
correct
<steev>
tegra is our only hope for a mainline gpu
<steev>
nouveau already works with the jetson k1, i'm probably going to play with it a bit over the next couple days, see if i can't get it working on the chromebook
<amstan>
or.. amd?
<steev>
uh
<steev>
do they use radeon with juno?
<amstan>
idk, i heard that they were going to expand into arm but keep their gfx ip on the chips
<amstan>
so that would be cool
<steev>
maybe... i mean, as long as it's decent... they did kick all their ati mobile devs to the curb (aka to qualcomm)
<amstan>
ati mobile? that was a thing?
<steev>
i put in a request for a price on a juno, haven't heard back