<Astralix>
if you don't feel familiar with udev, just take my way and start the adb server part as root (sudo)
<Astralix>
or you add the udev to group dialout and then you add yourself as user to the same group. In that case you don't have to open the channel for everyone (0666) but only members of the group. (0660)
<Astralix>
In that case your equipment is safe if your litte brother/sister can access the same computer
<tonikasch>
does anybody know in kernel 3.0.8 which #defined variable would adjust to GPIO 359? I'm trying hard but I only find it would be either FPGA_PIO2_15 (not probable) or something else related to TCA6424_XXX or WM831X_XXX.
<tonikasch>
Since I don0t have handy the specs for MK808B I cannot remember if this device has TCA6424 and/or WM831X
<tonikasch>
I guess there are missing gpios #definitions
JochenKauz has joined #linux-rockchip
<tonikasch>
hi, JochenKauz
<tonikasch>
leowt asked me where you got crewrktablets rk3066 code from, since it has important files necessary to build for rk3168
<JochenKauz>
Hi tonikasch
<JochenKauz>
Thats not easy to explain, cause it is a merge from different sources
<tonikasch>
well, the fact is that it has clock-rk3066b.c or some file similar that was missing in aloksinha's, galland's, etc
<JochenKauz>
I kknow
<JochenKauz>
I told it a few days before
<JochenKauz>
that we have this files
<tonikasch>
:D
<JochenKauz>
this files are leaked from a manufacturer our crew know
<tonikasch>
aha
<JochenKauz>
and I think that could be a little problematic
<JochenKauz>
so use it as you like
<JochenKauz>
we've got clock.c, vpu_service.c and some other very interesting files, that were in the past only available as .uu
<tonikasch>
:D
<tonikasch>
problematic? well...
<JochenKauz>
let's say... it was a mistake from RK that these sources were offered and I don't think that RK wanted that
<tonikasch>
well... that's up to them, now it's public
<JochenKauz>
yes and that's good for the community
<JochenKauz>
but I think you can understand that I can not say from what company the files were given to us, that could be problematic
<tonikasch>
ahhh, no problem ;)
<JochenKauz>
so we could be happy to have them, and perhaps we could get something more in the near future
<JochenKauz>
but the biggest thing right now, is too merge all sources to get it to a complete generic kernel source
<JochenKauz>
we got a 3.0.36 kernel from rk31, this has fragments of rk30 and rk29
<tonikasch>
a 3.0.36 different from the one that can be extracted from the leaked mk908 sdk?
<JochenKauz>
yes
<JochenKauz>
you can find it at our git
<JochenKauz>
it were basically a BQ Curie source
<tonikasch>
oh, I though it was the same
<JochenKauz>
no
<tonikasch>
(I didn't inspect it)
<JochenKauz>
its older than the last sources
<JochenKauz>
and has modifications from us to get it working on other tablets
<JochenKauz>
but not finished yet
<JochenKauz>
we've made first changes for rk30 already
<tonikasch>
:D
<JochenKauz>
you can also find at our repo changes for ubuntu touch kernels
<JochenKauz>
this were made in the rk29 kernels, but the changes could be transfered to the 3.0.36 kernel without problem
<JochenKauz>
but time is a limit
<JochenKauz>
so we would be happy if we could get help to make the kernel more complete
<JochenKauz>
as I said, the 3.0.36 kernel is able to be generic for all RK platforms
<JochenKauz>
but there have to be done additions to get it complete
<tonikasch>
yes, I have seen a 3.0.36 kernel that can already be built, for example, for mk808 (rk3066) device
<JochenKauz>
arch/arm/rk29 is missing at this time
<JochenKauz>
yes, but it is a stick kernel, so very important things for tablets are missing
<tonikasch>
lcd1 and touch screen support?
akaizen has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
<JochenKauz>
yes LCD, Touch and gsensor
<JochenKauz>
hdmi another point, the sticks only give the picture thru hdmi, rk30/31 tablets can use both video ports, framebuffer is another problem
<JochenKauz>
with this tablet config you need a bigger framebuffer, or to be precise more framebuffer
<tonikasch>
ahms
<JochenKauz>
all LCDx have their own framebuffers
<JochenKauz>
on sticks this is not needed
<tonikasch>
well, i'm not a great developer, indeed i'm starting to learn by looking at code, i haven't yet commited any change nor made any fork, but...
<tonikasch>
now i'm stuck with giving rk903 support by dumping gpio values, the next is to try changes and perhaps propose changes to code
<tonikasch>
if there is some way i can help with framebuffers or something else...
<JochenKauz>
do you have a rk30/rk31 tablet?
<JochenKauz>
the last thing we were working on were get the framebuffer working on rk30
<tonikasch>
no, sorry, not yet, perhaps i'll be buying a bq this christmas
<JochenKauz>
I have a RK30, but unfortunately I was not able to get the LCD working, it's a LCD I have never met before, and I have no configs for that device
<JochenKauz>
the manufacturer has released wrong sources and do not react on the notice
<tonikasch>
:(
<JochenKauz>
so I'm not able to test more on that rk base
<tonikasch>
what a pity
<JochenKauz>
I'm really frustrated on that device
<tonikasch>
have you managed to get hdmi working for that device?
<JochenKauz>
no
<tonikasch>
:S
<JochenKauz>
or to be precise
<JochenKauz>
it was not booting at that point to make the necessary changes our ROM's need
<tonikasch>
what about opening it and adding a serial console?
<JochenKauz>
our ROM's need some scripts to be run after first boot to CWM
<tonikasch>
ahh, I see
<JochenKauz>
yes, could be a way
<tonikasch>
a tricky way, but...
<JochenKauz>
but I need to format the nand flash befor it boots
<Astralix1>
I have opened the Xelio10pro and cannot identify the LCD, and I added serial console but that doesn't help to find correct PWM-DC/DC settings or LCD identification
<tonikasch>
mmmm, I read usumfabricae has been able to load rknand .ko (forcing the load) under linux, so perhaps could be a way...
<JochenKauz>
thats a real problem if unknown hardware is buildin
<JochenKauz>
that was another idea
<JochenKauz>
is it possible to boot a standard linux kernel? Never tried something before
<tonikasch>
well... I don't know if it is possible for tablets, but Galland's 3.0.36 kernel has been successfully booted on sticks
<tonikasch>
if you combine the idea of the serial console and the linux booting plus forcing rknand.ko loading... perhaps you could format it
<tonikasch>
just in case you don't manage to get a lcd or hdmi with linux
<tonikasch>
actually there are two 3.0.36 kernels at Galland's github, Linux3188 is the one that has been reported to boot on both rk31 and rk30
<JochenKauz>
ahh okay.. I think I have to diff it to our repo
<tonikasch>
:)
<tonikasch>
usumfabricae said somewhere... "I also forced rk30xxnand_ko (default 3.0.8+) load and I can also access NAND memory."
<tonikasch>
:)
<JochenKauz>
yes..
<JochenKauz>
It would be easier if we would all work together, instead all working on our own
<JochenKauz>
but I think that is to difficult
<tonikasch>
well, I know, perhaps we should promote this channel, I think it's a good place to co-work
<JochenKauz>
yes, it is a dream that we all could work together like the kernel devs for standard linux
<tonikasch>
well, otherwise, let's set up a mailing list or something like that
Topgun100 has joined #linux-rockchip
<JochenKauz>
I think it could be a possibility to form a unified repo at github
<JochenKauz>
and the make branches
<JochenKauz>
then
<JochenKauz>
but I think that this is to complicated for all the different interests the developers have
<tonikasch>
it will have to happen, sooner or later
<tonikasch>
in fact, omegamoon, galland and aloksinha2001 are already working as a group
<JochenKauz>
yes.. but they are working on sticks
<JochenKauz>
we are working on tablets
<JochenKauz>
I know that Astralix is in closer contact to omegamoon
<tonikasch>
but I think there are more things that are shared between sticks and tablets than those that are different
<JochenKauz>
yes, but we have different main focuses
<tonikasch>
mmm, I don't know if I understand...
<tonikasch>
definitely I don't know which is the difference
<JochenKauz>
okay... let's try to explain
zoobab has quit [Ping timeout: 269 seconds]
zoobab_ has joined #linux-rockchip
<JochenKauz>
what are the differences between rk sticks and rk tablets, or even rk phones?
<tonikasch>
well... perhaps usage?
akaizen_ has joined #linux-rockchip
akaizen has quit [Read error: Connection reset by peer]
<JochenKauz>
no, the components that are build in, or not
<tonikasch>
that's it, but the main components are the same... rk3066/rk3168/rk3188 proccessor, pmus, clocks, even wifi
<JochenKauz>
yes and no
<tonikasch>
I know that it's not as usual as on sticks to have connected usb devices to the tablets, but...
<tonikasch>
why not?
<JochenKauz>
does sticks have a battery?
<tonikasch>
aha
<JochenKauz>
battery controller... no
<JochenKauz>
something very important
<JochenKauz>
no charge control
<JochenKauz>
and very special point.. HDMI only needs no special init sequence
<JochenKauz>
unfortunately you can not identify the parameters from kernel logs or seral
<JochenKauz>
so if you want a TV stick, you can ignore all the things that are important for tablets
<tonikasch>
:(
<tonikasch>
so how do you manage to debug video output settings for tablets?
<JochenKauz>
thats the problem... trial and error
<JochenKauz>
for most of my tablets there is a generic display driver
<Astralix1>
In my case the display uses a video mode that doesn't even exist...
<tonikasch>
:o
<JochenKauz>
yepp
<JochenKauz>
I have a Archos Gamepad, no way to get it working
<Astralix1>
in that case a good disassembler is your very best friend
<Astralix1>
btw: Jochen do you have lcd working on genio?
<Astralix1>
I lost track, where we where when holidays started
<JochenKauz>
yes lcd is working on genio
<JochenKauz>
but to be precise, that was last message of Oma
<Astralix1>
I remember that I was catching the parameters out of a disassembled kernel
<Astralix1>
Ah, yes, it works, just audio and touch where missing
<JochenKauz>
yes
<JochenKauz>
analog audio
<Astralix1>
So status for this night: Xelio10pro boots with 3.0.36+ kernel till access of nand partitions. LCD is missing, Touch could not be tested
<JochenKauz>
yes
<Astralix1>
And it is one of the latest kernels that supposed to be based on 3.0.66 and can be compiled with out optimized toolchains
<JochenKauz>
so... same problems as every time with the tablets
<Astralix1>
Yes, but coming that far is not bad for a single evening
<JochenKauz>
must be compiled without optimzed toolchain, or am I'm wrong?
<Astralix1>
mope, mine boots with 4.7.2hf
<Astralix1>
[ 0.000000] Linux version 3.0.36+ (astralix@BigBox) (gcc version 4.7.3 20121106 (prerelease) (OSELAS.Toolchain-2012.12.1 linaro-4.7-2012.11) ) #12 SMP PREEMPT Thu Aug 29 00:22:03 CEST 2013
<JochenKauz>
Xelio10Pro? Into JB?
<Astralix1>
I don't know how far it would get if it could access cache partition...
<JochenKauz>
I think that this could be the problem
<JochenKauz>
you use a hf kernel, trying to load .ko's compiled with non hf
<JochenKauz>
I don't think that this will work
<tonikasch>
ummm, I'm also using hf kernel now... perhaps I won't be able to use rknandxx30.ko under it :(
<Astralix1>
hhahaha.... I reflashed xelio original kernel and saw a boot animation....
<tonikasch>
well, nice talk, I have enjoyed, I would like to serve as a bridge between these two worlds, will keep coming and telling, and talking with Omagamoon too :)
<tonikasch>
bye!
<Astralix1>
bye, bit I am talking with omegamoon too :)
<tonikasch>
:)
<tonikasch>
ciao
tonikasch has quit [Quit: lalallalalalalalallalalalallalalalalala good night!]