RayFlower has quit [Read error: Connection reset by peer]
levd1 has joined #linux-rockchip
RayFlower has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
hramrach_ has quit [Ping timeout: 250 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 265 seconds]
atomic_bat has quit [Quit: AtomicIRC: The nuclear option.]
atomic_bat has joined #linux-rockchip
hramrach_ has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd>
Tony__: no idea. I guess it depends how your board is wired and how rk616 driver is coded.
atomic_bat has quit [Read error: Connection reset by peer]
atomic_bat has joined #linux-rockchip
atomic_bat has quit [Client Quit]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
<Tony__>
<naobsd>, I'm sure that my board is wired, but I don't know if the rk616 driver is coded.
<Tony__>
I used the RK official Solutions. about hardware and driver.
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<Tony__>
hi naobsd, can you tell me the stock kernel support DDC ?
<naobsd>
Tony__: I don't have any device with rk616. you don't have any source tree with rk616 driver?
<Tony__>
I have source tree with rk616.
<naobsd>
Tony__: then please check it...
<Tony__>
naobsd, I think it's very complex. so I asked at first. :)
<Tony__>
rk616 is a mutilfunction device.
<naobsd>
if you have a board with rk616, you can try driver. if it doesn't work well, then it doesn't work well. without real hardware, all I can get is "driver file is available" (or not)
<Tony__>
I have a board with rk616, It can works normally fine.(video can put to TV). but I can't get any DDC signor , that's the point that I'm confused. so I asked, I know that there is maybe a answer in driver code. I think that there are some one who has same case with me.
levd has joined #linux-rockchip
<naobsd>
sorry, for now I don't have any device and experience about rk616
<Tony__>
If there no anyone who has the same case with me, maybe I have to RTFC. :_
levd1 has quit [Ping timeout: 264 seconds]
<Tony__>
*RTFSC. Read the fucking Source code. :P
<Tony__>
naobsd, can you tell me which HDMI IC you used ?
<naobsd>
it66121 on RR
<Tony__>
Its DDC can works fine.
<Tony__>
and how about CEC ?
GriefNorth has joined #linux-rockchip
eebrah has quit [Remote host closed the connection]
eebrah_ has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 255 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower 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: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 256 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
antoinemaillard_ has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 258 seconds]
antoinemaillard_ is now known as antoinemaillard
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
lautriv has quit [Ping timeout: 245 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 250 seconds]
nighty-_ has joined #linux-rockchip
lautriv has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
mrcan_ has joined #linux-rockchip
mrcan has quit [Ping timeout: 255 seconds]
ZZambia has joined #linux-rockchip
strontium has joined #linux-rockchip
<strontium>
hi all. i have pipo m9 pro on rk3188 and o loader 2.10 i unable to apply changes to mount options in ramdisk, any ideas ?
<strontium>
on loader 1 all is ok
strontium_ has joined #linux-rockchip
strontium has quit [Ping timeout: 246 seconds]
strontium_ has quit [Ping timeout: 246 seconds]
<Tony__>
strontium, what are you talking about ?
<Tony__>
ramdisk ?
eebrah_ is now known as eebrah
eebrah is now known as Guest21131
Guest21131 is now known as eebrah_
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 272 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
wildea01 has joined #linux-rockchip
<rperier>
hi
Tony__ has quit [Remote host closed the connection]
AstralixNB has quit [Ping timeout: 250 seconds]
AstralixNB has joined #linux-rockchip
levd has quit [Quit: levd]
levd has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
AstralixNB1 has joined #linux-rockchip
AstralixNB has quit [Quit: Leaving.]
AstralixNB has joined #linux-rockchip
AstralixNB1 has quit [Ping timeout: 250 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
<AstralixNB>
hello everyone
<AstralixNB>
naobsd, are you there?
<AstralixNB>
Hi lautriv
RayFlower has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
<naobsd>
well
<naobsd>
AstralixNB: I'll leave soon...
<AstralixNB>
I just would like to clear the general process of how to generate a sd card boot image for Android.
<AstralixNB>
It is no problem to use the image and the tool for radxa but I'd likt to understand the process and how to build for a different hardware
<AstralixNB>
I read, used and sucessfully tested the explanations in the wiki, but I am missing all the details how to build the initial image, that is then copied to the sd.
<AstralixNB>
Furthermore I miss the details which driver has to be installed instead of rknand.ko. Cause there is a gsnand or something similar used to build mtd block devices in the non-partitioned area of the SD.
<AstralixNB>
And last not least, why is there again an special driver involved instead of using ext4 partitions that are supported without any further drivers?
<AstralixNB>
... So if you have to leave soon... This will not work out right now :)
<naobsd>
well
<naobsd>
what is the special?
<naobsd>
how to build android image is not special, you'll get kernel/boot/recovery/system images
<naobsd>
how to flash header/ddr blob/loader to SD card is known
<AstralixNB>
yes
<AstralixNB>
but the wiki is incomplete
<naobsd>
how/where to flash parameter and images are also known
<naobsd>
are you talking just about Radxa's wiki completeness?
<AstralixNB>
yes
<AstralixNB>
do you have a different one?
<AstralixNB>
You should create a normal upgrade.img and then the mysterious windows tool magically forms a working sd card from it...
<AstralixNB>
That is not as much information as I would like to see... And I would prefer a non-windows way
<naobsd>
and I(my page) explain what is done by that magic tool
<AstralixNB>
we really should try ot clean up this a bit
<hipboi>
AstralixNB, alternatively you can use dd to make the sd card android image
RayFlower has quit [Read error: Connection reset by peer]
<AstralixNB>
yes, but...
<hipboi>
AstralixNB, i mean dd system.img, recovery.img to sdcard one by one
<naobsd>
yes and no, I commented some for that wiki page
<AstralixNB>
I understand that you can treat a sd card like an eMMC. But to use an un-partitioned area as an MTD device there is a special RK driver involved that is not mentioned anywhere.
RayFlower has joined #linux-rockchip
<AstralixNB>
So if you like your android to boot from sd, you probavly need to exchange the rknand.ko with this driver.
eebrah_ is now known as eebrah
<AstralixNB>
*probably
<naobsd>
AstralixNB: if you want to use partitions defined in parameter, just use rknand.ko as like as boot from NAND
<hipboi>
AstralixNB, the same nand.ko supports both nand flash and sdcard
<AstralixNB>
Ok!
<naobsd>
if you want to use partitions defined by MBR, just make partitions on MBR
<naobsd>
^ want to use partitions by MBR without rknand.ko
<AstralixNB>
That will lead to the next question...
<AstralixNB>
The loader can decide into which image it boots: recovery or boot
<AstralixNB>
It can boot into both systems in any case, so combined with kernel or kernel extra.
<AstralixNB>
With a kernel included you cannot give a partition...
<naobsd>
?
<AstralixNB>
so how to set parameter that the loader starts boot or recovery if these are real ext4 partitions and there is only one kernel as binary at 0x2000?
<naobsd>
well
<AstralixNB>
AFAIK the Loader checks: recovery or boot? Then it checks has recovery/boot a kernel included? If yes, boot the corresponding kernel with the partition as root. If not, boot the general kernel with the given partition as root
<naobsd>
AstralixNB: about boot from NAND, what happen if you don't flash parameter to NAND
<naobsd>
AstralixNB: do you think it really can boot?
<AstralixNB>
The loader yells at me, giving me bad namens
<naobsd>
AstralixNB: how to find kerne/boot/recovery w/o parameter?
<AstralixNB>
no, I don't want to skip the parameter
<naobsd>
AstralixNB: then, please don't skip parameter for "boot from SD" too
<naobsd>
AstralixNB: loader reads parameter, it has partition info, then loader can find kernel/boot/recovery partition
<AstralixNB>
I never wanted to skip it
<naobsd>
<AstralixNB> With a kernel included you cannot give a partition...
<naobsd>
<AstralixNB> so how to set parameter that the loader starts boot or recovery if these are real ext4 partitions and there is only one kernel as binary at 0x2000?
<naobsd>
I cannot understand these messages
<AstralixNB>
Ok, you can boot linux via sd with parameter but with only give the kernel start address, but no fürther MTD partitions
<AstralixNB>
-ü+u
<naobsd>
flash parameter at 0x2000, then flash kernel/boot/recovery/system/whatever you want to 0x2000+offset on SD
<naobsd>
"but with only give the kernel start address, but no fürther MTD partitions" <- I cannot understand this
<AstralixNB>
You flash kernel and give kernels address to parameter
<AstralixNB>
but then the kernel command line only uses sd-card partitions to inform the kernel, where he finds /
<naobsd>
"You flash kernel and give kernels address to parameter" I don't flash anything for you
<AstralixNB>
root=/dev/mmcblk0p1
<hipboi>
AstralixNB, it will conflicts
<AstralixNB>
my idea was:
<AstralixNB>
flash kernel as binary like usual on nand and sd
<AstralixNB>
flash minimal parameter for the loader to work and boot a kernel
<hipboi>
AstralixNB, if nand.ko was inserted, you need to disable mmc0 driver
<AstralixNB>
flash boot, system, user, cache and userdata as normal partitions using ext4
<AstralixNB>
I wanted to throw out rknand completely as it is not involved in such a standard linux model
<naobsd>
AstralixNB: then, disable rknand.ko and enable mmc driver in kernel, make partitions in MBR, write fstab as like as PC Linux
<hipboi>
AstralixNB, i think that is possible
<naobsd>
you may use GPT if kernel supports it
<hipboi>
AstralixNB, you need to modify the android mounting
<AstralixNB>
I tried this at the weekend and hit some limitations as you cannot create countless partitions
<AstralixNB>
and yes, I guess I need to use a more linux way of mounting. but I thought the partitions are decoded from "fstab.rk30sdk" in boot
<naobsd>
there is extended partition for MBR, and GPT can make more partitions
<AstralixNB>
So I just modified this fstab from /dev/mtd/mtdbyname/.... to /dev/mmcblk0p3 and such
<AstralixNB>
naobsd: yes, that is right
<AstralixNB>
I have not decided which partition layout would be the best.
<AstralixNB>
what I like of the automated way the fake-MTD system does, is the automatic adaption to the size of the used SD card
<AstralixNB>
So even my solution would be the most linux like way, the user experience of the fake-mtd will be higher+
<naobsd>
rknand.ko gives fake mtd partitions
<naobsd>
sorry, I cannot miss train
<naobsd>
bye
<AstralixNB>
bye
naobsd has quit [Quit: Page closed]
mrcan__ has joined #linux-rockchip
<AstralixNB>
If you're a Android developer and just like to exchange a single file, a boot / recovery / system as plain ext4 image on an sd card will give many benefits+
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
mrcan_ has quit [Ping timeout: 258 seconds]
naobsd has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 265 seconds]
antoinemaillard has joined #linux-rockchip
mrcan__ is now known as mrcan
RayFlower has quit [Quit: RayFlower]
naobsd has quit [Quit: Page closed]
AstralixNB1 has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
AstralixNB1 has quit [Client Quit]
<lautriv>
Hi Astralix1 , wasn't ignoring you, just came back ;)
<rperier>
I am not sure that we will have support to poweroff marsboard and radxa for the next release :D (Mark wants more reviews, he's totally right, I understand his point of view but people who were ranting about the previous series don't care about this one... so it might take a long time and the previous property might go into the Linus's tree)
<rperier>
but that's the game
AstralixNB has joined #linux-rockchip
<mmind00>
rperier: there are still about 3 weeks of time till the merge window
AstralixNB has quit [Read error: Connection reset by peer]
<rperier>
yeah I know, and we have 2 rc. that's just I proposed the original changes around -rc1. A lot of people complained for nothing and now that everything is finished and seems to be fine (at least according to what Grant said), I have no feedbacks from these people. But it's okay :)
<rperier>
it would be annoying and not cool to see the old and ugly serie into the Linus's tree, which is the blocking part for me
<AstralixNB>
had to rebooot the notebook... lost track...
<AstralixNB>
Thanks to google I can see that traffic jam is building up... So I better get home now. Be back later in here. lautriv: naobsd and I agree that with 95% the DRAM of your stick has a problem.
AstralixNB has quit [Ping timeout: 250 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
ganbold_ has quit [Ping timeout: 255 seconds]
antoinemaillard has quit [Ping timeout: 264 seconds]
cosm has quit [Ping timeout: 265 seconds]
cosm has joined #linux-rockchip
ZZambia has quit [Read error: Connection reset by peer]
ZZambia has joined #linux-rockchip
cosm has quit [Ping timeout: 264 seconds]
AstralixNB has joined #linux-rockchip
Valduare has quit [Quit: Valduare]
ZZambia has quit [Quit: No Ping reply in 180 seconds.]
ZZambia has joined #linux-rockchip
ZZambia has quit [Quit: No Ping reply in 180 seconds.]
ZZambia has joined #linux-rockchip
cosm has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
bengal has joined #linux-rockchip
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
<hramrach_>
AstralixNB: I suspect to use the rk bootloader you need the parameters and stuff. and afaik there is no other bootlaoder for rk
<hramrach_>
but there is nothing stopping you from making the filesystems normal partitions
<Astralix1>
There is some open source uboot trials
<hramrach_>
ok
<Astralix1>
I bet, but first I'd like to go abd test the official way
<Astralix1>
then expand
<Astralix1>
I have a fresh baken aosp 5.0 for my iron tablet for testing on sd... just transferring the image parts...
<hramrach_>
but for compatibility with rk you probably want parameter/kernel/recovery/boot the rk way and a mbr/gpt for the rest crafted so that something covers the rk partitions
<hramrach_>
how did you get a kernel source for your tablet?
<Astralix1>
Hmm... lots of work :)
<hramrach_>
work getting kernel?
<Astralix1>
We do have a working kernel for Odys Iron
<hramrach_>
I have a tablet for which there is no kernel
<Astralix1>
How do I create the parameter.img for the loader?