RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Read error: Connection reset by peer]
akaizen 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
<naobsd>
mmm....
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
Soopaman has joined #linux-rockchip
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
benja is now known as benja`
<naobsd>
hmm, usb upload on mask rom mode is working
Astralix1 has joined #linux-rockchip
<naobsd>
but only rk30usbplug.bin can work as a loader :(
Astralix has quit [Ping timeout: 250 seconds]
<naobsd>
u-boot.bin doesn't work(no output)
<naobsd>
I guess initial state is different...
<naobsd>
RK proprietary loader also doesn't run as loader
<naobsd>
only usbplug for now :(
<naobsd>
anyway, better than nothing, I'll push it
GriefNorth has joined #linux-rockchip
npcomp is now known as npcomp|away
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
Soopaman has quit [Quit: Leaving.]
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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 260 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
<rperier>
hi all
<AstralixNB>
hi
nighty-_ has joined #linux-rockchip
<hramrach_>
naobsd: yes, that's what I am saying. rk3288 has only 1 high-speed link. no way to use as NAS or something like that. only client
<hramrach_>
btw you said something about the boot sequences page being incorrect but I do not see any edits
<hramrach_>
what is this maskrom bootloader? it's the botloader you upload over USB? how is it special? on other platforms it is the very same u-boot just with different defualt environment
<hramrach_>
is recovery kernel loaded when normal kernel fails?
<hramrach_>
logical 0 is what? the first block in the medium as mapped by the kernel for userspace/block device?
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
<rperier>
mmind00: hi, did you try linux-next recently ? Everything works fine for next-20140930 , however with next-20141001 I loose serial console output (or the kernel freezes, I don't know yet). The output of dw-apb-uart looks strange http://pastebin.com/yST1kbAa (look at the end of the log)
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
wildea01 has joined #linux-rockchip
<mmind00>
rperier: interesting, especially things like "dw-apb-uart 10126000.serial: ttyS1 at MMIO 0x10126000 (irq = 67, base_baud = 1500000) is a XScale" look strange
<rperier>
yeah, I agree, and try to bisect linux-next will be "fun"
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
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
<naobsd>
hramrach_: sorry, I don't have enough time to do wiki things yet
<naobsd>
hramrach_: mask rom loader is in CPU
<hramrach_>
ok, that makes more sense
<hramrach_>
but then what karlp added to the wiki does not
<naobsd>
hramrach_: kernel is loaded by bootloader, behavior is depend by loader
<karlp>
I'm still just trying to take notes written down here, and collate them
<hramrach_>
only the part in cpu is fixed
<karlp>
I think I added a note that the I was only discussing the stock rk proprietary loader, not the maskrom loader
<karlp>
but indeed, that could/should be clarified
<hramrach_>
it loads the rk loader which then loads the rest from a medium it was configured for
<hramrach_>
to get the rk proprietary loader you need to go through the in-cpu loader
<karlp>
the page likely needs some splitting up, for many usecases of, "I have a kernel and a RFS, where can I put them to get booted" is more interesting, and in those cases, the loader behaviour is "fixed" in that you don't want to change it, but it's not truly fixed indeed, you can put on a new loader
<naobsd>
well, now I'm talking is not answer(?) of wiki, I just read hramrach_ 's IRC message and try to answer without reading wiki
<hramrach_>
also there is probably nothing stopping you from, say burning the leader for mmc (if we had one) into nand. So cpu would load the bootloader fro nand, it would then load the parameters and kernel from mmc because it's what it's configured to do
<hramrach_>
s/leader/loader/
<naobsd>
hramrach_: logical 0 is the first sector mapped _to_ kernel. kernel(open source part) don't know how to access raw NAND
<hramrach_>
yes, it presumably has some blob that converts raw nand into a logical block device
<hramrach_>
so it should be logical sector 0 to make sense
<hramrach_>
thanks
<hramrach_>
also while you cannot get to the raw nand data on a mmc card you can technically get to it on the built-in nand chip. However, the boorloader hides/ignores that fact and only uses the logical block device in both cases
<naobsd>
(ah, I didn't check recent change yet)
<naobsd>
it's not same story
<hramrach_>
it's not. the nand loader needs a copy of the driver that exists in kernel to access the nand as logical block device
<naobsd>
e.g. we can put bootloader on NAND, but it cannot be accessed from kernel. and we can put bootloader on eMMC/SD, it can be accessed kernel.
<naobsd>
no, it's also different story
<hramrach_>
so bootloader in hidden area outside of the logical block device
<naobsd>
we need driver for eMMC/SD too
<hramrach_>
but tha =t diver only deals with logical blocks, at least on SD
<hramrach_>
not sure about eMMC. don't have any device with one that I took apart enough to know
<hramrach_>
I think my notebook has an internal eMMC memory but it's too locked down to replace the loader. You can only chainload or replace loader by hardware means
<naobsd>
for SD/eMMC, we use only logical blocks
<naobsd>
bootloader is in logical blocks
<naobsd>
this is different point to NAND
<hramrach_>
and for nand the situation is same except the laoder is hidden from logical area
<naobsd>
I read latest wiki
<naobsd>
following is about wiki
<naobsd>
well
<naobsd>
again
<naobsd>
what I said NAND situation and SD/eMMC situation is different. please consider about _except_ part you said
<naobsd>
then, about wiki
<naobsd>
about "Boot Sequences"
<naobsd>
it describes about mask rom mode too
<naobsd>
e.g. "the loader in the rom searches for bootloader"
<hramrach_>
indeed, it does and should
<hramrach_>
because the mask rom loader is what gets you to loading the rk loader
<naobsd>
both above and below of "Or, another way:" explains almost same thing...
<hramrach_>
yes, quite useless duplication
<naobsd>
below part seems clean
<hramrach_>
hope I get to summarizing this later
<naobsd>
RK3188 "You may need to short pins on / clear content of your nand." is no
<naobsd>
SD is prior to NAND
<hramrach_>
is it?
<hramrach_>
that's news. all tutorials showed how to replace kernel in nand because there was no way to boot from SD
<hramrach_>
but maybe because lack of laoder rather than the boot sequence being backwards
<naobsd>
no "all", it's just "old"
<hramrach_>
there is no new one I am aware of.
<naobsd>
and
<hramrach_>
maybe should read more of the radxa tutorials
<naobsd>
well
<naobsd>
sd boot is not so news
<naobsd>
and
<hramrach_>
yes, it presumably worked somehow on rk31 and rk29 just not on rk30
<naobsd>
many info on the net are not updated long time
<naobsd>
and I think karlp's description on that page was right
<hramrach_>
so is the boot order known?
<hramrach_>
presumably SD, emmc and SPI comes before nand then
<naobsd>
I'm talking about SD and NAND now
<naobsd>
on RK3188
<naobsd>
dd if=parameter.img <- sorry, this is right one, I fixed my zip
<naobsd>
"in my sdboot img, size of loader are is good for RK proprietary loaders, but too small for u-boot/barebox" this is fixed in my latest zip (which include u-boot) but zip linked from my web page is still old
<hramrach_>
is there any u-boot usable with rk?
<hramrach_>
or barebox or whatever
<naobsd>
well
<naobsd>
it's not news too..
<hramrach_>
there is no u-boot page on the wiki
<hramrach_>
does radxa have an u-boot?
<naobsd>
sorry, monologue: when I explained the fact, why I got reply "really?" so many times...
<naobsd>
at least I don't write wiki yet
<hramrach_>
that's why nobody knows
<naobsd>
it's not so old but not so new
<naobsd>
sigh
<naobsd>
ok, I'm bad guy, thank you.
<hramrach_>
well, let me put it this way. If people are repeatedly surprised by something you tell them here, there is a wiki link in the topic, and the wiki has no info on that
<hramrach_>
it would be practical to make a page in the wiki so people are not surprised so often and you could just paste the link
<hramrach_>
it's not bad to not write stuff down. but don't be surprised people do not know then
<naobsd>
ok, I have responsible for all linux-rockchip things,
<naobsd>
I should keep up-to-date and cover everything
<naobsd>
before I tell something.
<naobsd>
well
<naobsd>
what I said is
<hramrach_>
do not put words into my mouth
<naobsd>
I said "zip (include u-boot)"
<hramrach_>
I am saying that if you not write it you should not be surprised people do not know.
<naobsd>
well
<naobsd>
sigh
<naobsd>
I said there is a zip include u-boot
<naobsd>
you surprised
<naobsd>
if I wrote wiki "there is a (zip include) u-boot"
<naobsd>
are you sure that you will not surprised and ask "really"?
<hramrach_>
yes, I am surprised because there is no info on u-boot
<naobsd>
what is the difference I said here
<naobsd>
you surprised about "it's not in wiki", not about "there is u-boot"?
<hramrach_>
I am surprised there is uboot. I do not know about any so far
<hramrach_>
or last time I asked there was none
<naobsd>
I know
<naobsd>
info should be added to wiki
<naobsd>
but it's impossible to do it before when it's done
<hramrach_>
it actually was there hidden in the middle of rk3188 page
<naobsd>
that 3 links is not u-boot I talked now
<naobsd>
then
<naobsd>
I have to leave here for a while
<naobsd>
later
<hramrach_>
that's the info the wiki has. Probably outdated
<karlp>
this is related to what I was talking about earlier. there's a lot of overlapping information that confuses things.
<karlp>
for people who only want to get a linux kernel+RFS up, all that matters is a description of the behavioru of the RK prop loaders,
<karlp>
but those arne't fixed in any sense,
<hramrach_>
it's the default
<hramrach_>
if you change it it's different but then you know you did
bengal has joined #linux-rockchip
<naobsd>
I realized that I should eliminate whole wiki pages, not marking just OBSOLETE :(
<hramrach_>
those pages marked obsolete should be completely useless
<naobsd>
otherwise I got "really? it's not in wiki" every message on here :(
<hramrach_>
but only administrator can delete pages
<hramrach_>
then the wiki will be empty. it's 100% obsolete and inaccurate
<naobsd>
it's better for me
<naobsd>
at least I will not be blamed everything I post on here
<naobsd>
I know wiki is important but I didn't know it's prior than the fact I post on here
<karlp>
naobsd: no-one's blaming you for anything
<hramrach_>
if you post it on wiki it's there 24/7 and not when you happen to come by here
<karlp>
you can just keep talking here, and I'll keep posting it to the wiki, and every now and again someone else can review it and correct it.
<karlp>
but no-one's blaming you for anything at all.
<naobsd>
I don't say I never write wiki
<naobsd>
but I prefer to make thing sure before writing
<hramrach_>
I don't say you have to
<naobsd>
not copy&paste from random old tuto on the net
<hramrach_>
but then don't blame people for not knowing when there is no place t o find out
<naobsd>
yes, if people don't doubt every new thing
<naobsd>
I have to leave here for a while again
<naobsd>
later
bengal has quit [Ping timeout: 260 seconds]
<dlezcano>
mmind00: naobsd : finally I succeed to boot my own kernel, I would like to use the SD card as rootfs
<dlezcano>
mmind00: naobsd : what is the root=... parameter ? (I have an evb rk3288)
<dlezcano>
mmind00: naobsd: I tried root=/dev/mmcblk1p1, root=/dev/mmcblk0p1 without success
<naobsd>
dlezcano: which initramfs are you using?
<dlezcano>
naobsd: I am not using an initrd (AFAIK)
<naobsd>
dlezcano: then you get no rootfs panic while booting?
<AstralixNB>
hramrach: If you do lots of kernel dev, it might be easier to flash the kernel via flashtool into NAND but configure the commandline in parameter to load the rootfs from SD.
<naobsd>
it's eMMC? SD?
<dlezcano>
The command line is: console=ttyS2,115200 earlyprintk=console=ttyS2,115200 root=/dev/mmcblk1p1 rootwait
<dlezcano>
naobsd: I think mmcblk0 is the emmc
<dlezcano>
but I don't know what is the device for the SD
<naobsd>
dlezcano: I guessed mmc0 is SD and it's in error state
<dlezcano>
naobsd: hmm
<naobsd>
dlezcano: I only have few info about "current" mainline, I have to check how sd/emmc works
<naobsd>
dlezcano: sd controller is at ff0c0000, emmc is at ff0f0000
<AstralixNB>
I do have some small tasks waiting for daytime job, but current mainline / upstream is waiting for beeing compiled this evening for radxa preview boards
<dlezcano>
naobsd: dw_mmc ff0c0000.dwmmc: no vmmc regulator found: -19
<dlezcano>
dw_mmc ff0c0000.dwmmc: Using PIO mode.
<dlezcano>
mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
<dlezcano>
dw_mmc ff0c0000.dwmmc: DW MMC controller at irq 64, 32 bit host data width, 256 deep fifo
<dlezcano>
dw_mmc ff0c0000.dwmmc: Version ID is 270a
<mmind00>
dlezcano: naobsd: just for the record ... the emmc on my evb also has this "unknown partition" table
<naobsd>
"mmc0: card never left busy state" <- I guess this is not good
<naobsd>
yes, I think mmcblk0 at mmc1 (eMMC) is ok
<naobsd>
I don't know what is boot0/boot1 on eMMC, but I just ignored for now ;)
<hramrach_>
AstralixNB: yes, it makes sense to flash to nand if many of your kernels do not boot and you do not have any means to update mmc other than removing the card while flash can be updated over usb
<hramrach_>
if we had u-boot with mmc support loadable over usb you could use that as well
<mmind00>
dlezcano: it should be, but your "card never left busy state" suggests that something isn't right
<hramrach_>
is that regulator error normal?
<dlezcano>
sigh
<mmind00>
dlezcano: :-)
<naobsd>
dlezcano: did you try to remove/reinsert card?
<naobsd>
possibly: bootloader touches SD card and left invalid state
<AstralixNB>
mmind00, to do a rough test on radxa, which branch to switch to? I am currently at topgit/devel
<mmind00>
AstralixNB: devel/workbench (roughly the same intent, but without the merge conflicts :-) )
<naobsd>
dlezcano: what bootloader are you using and where is boot media?
<AstralixNB>
tnx
<dlezcano>
naobsd: yes, I tried to remove and reinsert the card (different cards)
<naobsd>
(sorry, I'm away for a while)
<dlezcano>
mmind00: why is in the file arch/arm/boot/dts/rk3288-evb.dtsi, "vin-supply" commented ?
<mmind00>
"unfinished business" ... but vcc_io (which is the source for this) should be always running because it is supplying a lot more
FightingCat has joined #linux-rockchip
<dlezcano>
mmind00: ok
<dlezcano>
mmind00: there is a difference with your branch #for_broken_bootloader:
<dlezcano>
vcc_sd0: sdmmc-regulator {
<dlezcano>
compatible = "regulator-fixed";
<dlezcano>
regulator-name = "sdmmc-supply";
<dlezcano>
regulator-max-microvolt = <3300000>;
<dlezcano>
regulator-min-microvolt = <3300000>;
<dlezcano>
gpio = <&gpio7 11 GPIO_ACTIVE_LOW>;
<dlezcano>
startup-delay-us = <100000>;
<dlezcano>
/ vin-supply = <&vcc_io>;
<dlezcano>
};
<dlezcano>
Could be related ?
<hramrach_>
that's probably what causes the no vmmc regulator found
<hramrach_>
but if it's on anyway it should not affect mmc operation
<dlezcano>
ok, thanks
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<hramrach_>
if that's different from other branches you can remove the comment if you have nothing else to try but I would not expect it to change much
<mmind00>
dlezcano: whe I disable the two "cap-*" properties in the sdmmc node in rk3288-evb-dtsi, I get the sd card detected at boot at least
<mmind00>
dlezcano: removing and reinserting it again triggers the "card never left busy state" error
<hramrach_>
so there is some issue resetting the card
<hramrach_>
you are using the generic dwmmc driver?
<hramrach_>
maybe some other platforms reset the controller somehow?
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 258 seconds]
<dlezcano>
mmind00: I tried your suggestion but the SD card is not detected and shows "card never left busy state"
<dlezcano>
mmind00: ok, finally, I am using the initrd, so I am no longer stuck with my kernel dev
<dlezcano>
mmind00: another newbie question: I have 1/4 cpus up, it is expected ?
<mmind00>
dlezcano: great ... I hope that we'll get the dw_mmc also sorted eventually ... I'm currently checking if there are some patches pending in this regard
<dlezcano>
mmind00: ok, cool thanks
<mmind00>
dlezcano: missing smp on rk3288 is expected at the moment
<mmind00>
dlezcano: there is pending issue with the architected timer, as its virtual timers are not correctly initialized ...
<dlezcano>
mmind00: ok, thx
<naobsd>
it seems my 3.17.0-rc6 based kernel doesn't have SD card issue
RayFlower has quit [Read error: Connection reset by peer]
<dlezcano>
dumb questions : is rk3288-evb a A17 or A12 based ? (documentation says A17, /proc/cpuinfo shows A12) :s
<naobsd>
I think all we can do is just believe cpuid(cpuinfo) even if it's not A12 ;)
<naobsd>
oh, my kernel rejects BLKDISCARD ioctl...I think it worked on some kernel...maybe 3.10 kernel?
<naobsd>
let's do 0-fill for now...
<naobsd>
ok, loading DDR init and usbplug loader from mask rom mode is working on RK3188 and RK3288
<naobsd>
but
<naobsd>
it's useless without further development ;)
<naobsd>
ah, it seems usbplug has a header... 0x208 bytes
<naobsd>
is u-boot.bin relocatable? ;) let's try...
<naobsd>
0x20c bytes
<naobsd>
mmm... I have to tweak linker script or something else...
<naobsd>
oh, strange, start.S should have necessary info...
<naobsd>
mmm, usbplug header is not special, u-boot.bin have it too... :(
<naobsd>
oh
<naobsd>
well?
<naobsd>
u-boot.bin just booted
<naobsd>
I see
<naobsd>
u-boot.bin for rk3288 can be used for "load DDR init/Loader from mask rom mode"
<naobsd>
but u-boot.bin for rk3188 doesn't work
<naobsd>
maybe u-boot for rk3188 is older than for rk3288
<hramrach_>
naobsd: the point of BLKDISCARD is that the block is freed. 0-fill does not free it so quite pointless
<naobsd>
mmm, exec ram command is not implemented to u-boot for rk3288
<naobsd>
hramrach_: I know
<naobsd>
hramrach_: and not pointless
<hramrach_>
it technically moves your data out of view and wastes some flash blocks
<naobsd>
hramrach_: what I wanted to is erasing bootloader on eMMC, it's possible by discard AND by writing garbage
<hramrach_>
ok, for actually erasing an area you need to 0 it in absence of discard
<naobsd>
hmmmm....
<naobsd>
on rk3288, u-boot can be loaded via usb from mask rom mode
<naobsd>
but currently I have no way to load kernel from u-boot for rk3288 via usb...
<naobsd>
I should try fastboot, or implement my own rkflashtool protocol ;)
<c0d3z3r0>
could anybody send me the full specification for rk3188, please?
<naobsd>
probably fastboot is better, it can contain many information
<naobsd>
anyway
<naobsd>
no need to flash bootloader while developing bootloader
<naobsd>
good :)
<naobsd>
anyone who want to develop bootloader is welcome! ;)
<naobsd>
I'm sleepy
<naobsd>
1. push my code before sleeping (without wiki of course)
<naobsd>
2. keep my code until I'll write wiki
<naobsd>
3. other
FightingCat has quit [Read error: Connection reset by peer]
<naobsd>
3. do nothing, just go to bed
<naobsd>
I think no need to be hurry
<naobsd>
I wanted to try recent mainline, but too sleepy...
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
RayFlower has quit [Read error: Connection reset by peer]
<naobsd>
mmind00: is it ok to use linux-rockchip@infradead for discussion like rk2918 support? we can use ML@google groups too
<naobsd>
(and sorry, too sleepy, good night)
RayFlower has joined #linux-rockchip
<mmind00>
naobsd: I'd think development discussions might be better living on the google-ml
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has joined #linux-rockchip
Soopaman has joined #linux-rockchip
akaizen has quit [Ping timeout: 260 seconds]
<rperier>
do you know a dev board for rk2928 ?
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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 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
<hramrach_>
naobsd: on AW the maskrom protocol is used to load all of bootloader, kernel, initrd, DT and then u-boot just executes kernel from memory
FreezingCold has quit [Ping timeout: 272 seconds]
<hramrach_>
no need for special command or anything so long a s maskrom can load multiple regiaons .. or you can concatenate the loader with kernel, etc
FreezingCold 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
AstralixNB has quit [Ping timeout: 250 seconds]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 245 seconds]
akaizen has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
<Soopaman>
I see in the scroll that 3.17 was released, where can I download it, and which platforms is it supporting?
<Soopaman>
platforms does it support*
npcomp|away is now known as npcomp
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 245 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cristian_c has joined #linux-rockchip
<cristian_c>
Hi
<cristian_c>
I've got a question
<cristian_c>
I've got a wrong resolution in /sys/devices/virtual/display/display0.HDMI/mode
<cristian_c>
cwm recovery
<cristian_c>
1920x1080p-60
<cristian_c>
it's too big for my display
<cristian_c>
How can I change this, exactly?
<cristian_c>
Any ideas?
bengal has joined #linux-rockchip
bengal has joined #linux-rockchip
bengal has quit [Changing host]
cristian_c has quit [Ping timeout: 244 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cristian_c has joined #linux-rockchip
<cristian_c>
The server has disconnected me
<cristian_c>
Has anyone answered?
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<cristian_c>
the server has disconnected me
<cristian_c>
agaiin
<cristian_c>
*again
<cristian_c>
Has anyone answered?
<Astralix1>
cristian_c, I am a bit stunned too, as I was very sure, that there was a auto-discovery of the connected monitor available... once upon a time...
<cristian_c>
Astralix1, yeah
<cristian_c>
I've made a search
<Astralix1>
I'll ask Omega, if he knows, where it has gone, but I am sure Galland was the one who ficed that thing
<cristian_c>
bujt there isn't autoconfig file
<Astralix1>
fixed
<cristian_c>
in my cwm
<cristian_c>
recovery
<Astralix1>
Ah, you'rein Android?
<cristian_c>
rein?
<cristian_c>
are in
<cristian_c>
ok
<cristian_c>
Astralix1, no, in cwm
<cristian_c>
recovery
<Astralix1>
..'re in..
<cristian_c>
yeah, I understand
<Astralix1>
Need to buy extra spaces
<cristian_c>
Astralix1, I get:
<cristian_c>
3dmode connect mode name property subsystem uevent
<cristian_c>
audioinfo enable modes power scale type
<cristian_c>
/sys/devices/virtual/display/display0.HDMI # ls
<cristian_c>
Astralix1, but not autoconfig
<Astralix1>
Hmm... I see.
<Astralix1>
Problem is, that this group is pread arund the world and so... It may take a while, or you check yourself...
<Astralix1>
This should be the entry point of your search
<cristian_c>
rhanks
<Astralix1>
I'll ping him once in a while... But the monitor detection needs to be fixed anyway, as I want to use radxa with Linux and a non-HDMI monitor
<Astralix1>
But in Android there may be much more hard linked things regarding monitor resolution as in Linux
<cristian_c>
I'm looking at that
markm 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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 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
bengal has quit [Quit: Leaving]
FreezingCold has quit [Ping timeout: 258 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
cristian_c has quit [Quit: Sto andando via]
Soopaman has quit [Quit: Leaving.]
nighty-_ has quit [Quit: Disappears in a puff of smoke]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
PaowZ_ has quit [Ping timeout: 246 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd>
here is the person who made CWM for RK images, I don't think other old links are good starting point...