ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at | Logs at | ML at
<naobsd> Astralix: there is Android firmware from firefly too
<Astralix> And with the master / pad version it was my fault! I did not recover the text correctly!
<naobsd> Astralix: you can extract parameter from that firmware
<naobsd> Astralix: but I think there is no reason that you must use same parameter which firefly used for their firmware
<Astralix> Why? Everytime you think it is getting better... Something is missing :)
<naobsd> sorry?
<Astralix> So my error was, that you should not download the initial ZIP file from before some date in december, but you should use the newer one!
<Astralix> WARNING: If you have downloaded the SDK before Dec 11, 2014, please download again from the cloud drive and make it uptodate.
<Astralix> We (some crew members and I) tried that for four days and it broke, regardless what mirror we tried
<Astralix> So we cloned the nl mirror
<naobsd> ???
<Astralix> But you are right, you can use the master and the pad version
<Astralix> You should not clone the git, but download the initial image first and clone only the latest changes
<naobsd> nl mirror also has both branch (but little old for now)
<Astralix> THis is what is written there
<Astralix> So I cloned nl git and after that I modified remote to be bitbucket
<naobsd> Astralix: yes because that repo is too big for bitbucket's free account
<Astralix> After that I fetched and pulled again wht brought me up to the latest version
<naobsd> Astralix: and repo history was changed at Dec 11, this is the reason that they replaced repo zip
<Astralix> yes, I think so
<naobsd> what's the problem? they described "please download again"
<Astralix> We tried from different locations and different providers, the google mirror breaks after 1.x GB with Network Error
<naobsd> nl mirror is mirror of bitbucket, I know well about it, I made it, I pushed firefly repo to there from bitbucket
<naobsd> Astralix: what's google mirror?
<Astralix> That was a good idea, as that one worked
<Astralix> Google Drive
<naobsd> Astralix: I see. such kind of drive service sometimes dead due to transfer limit
<naobsd> Astralix: this is one of the reason I made mirror, but my mirror also has transfer limit
<Astralix> My Baidu download limit is reached long time ago
<Astralix> I have a request pening at the sponsor of our server
<Astralix> but he is in xmas holidays too, I guess
<Astralix> However we chould add a working parameter file to that SDK
<naobsd> anyway, as far as I know, firefly team did/are doing their work well. I think it's not perfect, but seems good for me
<naobsd> in pad branch, RKTools/windows/AndroidTool/AndroidTool_Release_v2.33/rockdev/rk3288-3.10-uboot-data1G.parameter.txt
<Astralix> ok, I searched by -- find . -name "parameter"
<Astralix> As in older SDKs it was available with that name
<Astralix> This should be added to the wiki
<naobsd> in master branch, there is RKTools/rk3288-3.10-uboot-data1G.parameter.txt too
<naobsd> it's just default/sample
<naobsd> it may not be "optimized" for your image
<naobsd> if you need "firefly" version (made by firefly team), there are firmware image
<naobsd> but they will be "optimized" for their firmware image
<naobsd> Astralix: I'm not firefly person, please write any request to their forum
<Astralix> yes, after I succeeded to extract or create a working version
<Astralix> So, then let's boot
<Astralix> That parameter doesn't work...
field^Mop has quit [Ping timeout: 264 seconds]
<Astralix> And with this parameter installed, that I extracted from the Android 4.4 image, uboot doesn't start normal
<Astralix> So upgrade_tool doesn't accept it anymore
<Astralix> hmm... upgrade_tool RD doesn't work, but you have to reboot by power-cycle and all works fine again!
<Astralix> Ok, jas-hacks: I can say that pad version of Android 4.4.4 is working here
<Astralix> naobsd, the behaviour of the system was quite strange on the first trial of reset, however, with the extracted parameter file it works.
<naobsd> jmcneill: oh I didn't have idea that usging decrement timer with ~
<naobsd> jmcneill: I guess clocklander() can be run while reattach/init a9tmr, is it safe?
markm_ has quit [Ping timeout: 244 seconds]
<naobsd> jmcneill: probably I'm wrong, need to understand more about timer things...
<naobsd> jmcneill: on boot, a9tmr_init_cpu_clock() is not called on other APs, right? then, if it's called on all cores after freq update, will it generates x4 interrupt?
<naobsd> sorry, I have to go out today
<naobsd> jmcneill: I'll try latest code later
naobsd has quit [Quit: Page closed]
cnxsoft has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 250 seconds]
FreezingCold has joined #linux-rockchip
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
cnxsoft has quit [Ping timeout: 240 seconds]
cnxsoft1 has joined #linux-rockchip
<FergusL> cnxsoft1: any chance you heard about a Bay Trail development board to come out anytime soon ?
GriefNorth has joined #linux-rockchip
<cnxsoft1> Not yet, but looking into it
ganbold_ has joined #linux-rockchip
<cnxsoft1> Actually MinnowBoard MAX is a bay trail development board.
<cnxsoft1> But using an Industrial SoCs, instead of a tablet SoCs
cnxsoft1 has quit [Quit: cnxsoft1]
cnxsoft has joined #linux-rockchip
naobsd has joined #linux-rockchip
faddat_ has joined #linux-rockchip
faddat has quit [Ping timeout: 240 seconds]
<naobsd> jmcneill: I see about per-cpu init, thanks
<naobsd> jmcneill: sorry for bothering you
gb_master has joined #linux-rockchip
gb_master has quit [Client Quit]
<rperier> hi all
jas-hacks has joined #linux-rockchip
<jas-hacks> naobsd: I suggest setting @5, @6, @7,@11 to always-on for the act8846. I looked at the vga driver in android they seem to be setting the regulators when probed. The regulators remain on until the driver is unloaded. @5 & @11 seem to be used by HDMI.
<naobsd> jas-hacks: any video-output related unit are not exist in rk3288-firefly.dts for mainline _yet_.
<jas-hacks> naobsd: ah, ok.
<naobsd> jas-hacks: it will be used when consumer is added
<jas-hacks> mmind00_: I can see that drm edid is reading edid from my monitor so that part seems to be working.
<jas-hacks> naobsd: yes
<naobsd> jas-hacks: do you have your own repo on public space?
<jas-hacks> naobsd: only local at the moment but plan to do that a some point
<naobsd> jas-hacks: I see. if you want, please let me know
<jas-hacks> naobsd: thx
<naobsd> I cloned chromiumos repo on my build machine, but disk space is almost full, only 30-40GB are free...
<naobsd> (it's enough for kernel work, but I wanted to build chromium os ;)
<jas-hacks> jas-hacks: Not sure if its worth building the whole tree (chromium os) as I don't think it work out of the box
<jas-hacks> s/it/it will
<jas-hacks> naobsd: any 'rockchip people' on this chat?
<naobsd> jas-hacks: I heard it should work (on some supported board which I don't have)
<naobsd> jas-hacks: I think no on here now
<jmcneill> morning
<naobsd> jmcneill: morning
<naobsd> jmcneill: I want easy-to-access rockchip_is_chip() (cached) result
<naobsd> jmcneill: is global variable ok?
<Astralix1> naobsd: diid you get my message? Android 4.4.4 pad version runs fine on the firfly.
<Astralix1> And I posted the proposales for some wiki improvement on their forum as promised
<naobsd> Astralix1: I saw that, thanks
<Astralix1> The pad version is scanning for a touch screen device
<Astralix1> [41146.694502] test_i2c-394: Enter
<Astralix1> [41146.696068] gsl_ts_read set data address fail! ret=-11-0xfffffff5
<Astralix1> Probably the LCD you can optionally buy does have this chip
<Astralix1> However this doesn't interfere with a normal pointing device like a mouse.
<naobsd> jmcneill: does it read register every time?
<jmcneill> no
<naobsd> ah!
<naobsd> static ;)
<naobsd> I see
<jmcneill> act8846pm0: DCDC4: [3.000V] [ON]
<jmcneill> that is too low for mmc0
<jmcneill> no wonder 50MHz mode doesn't work
mrueg has quit [Ping timeout: 250 seconds]
mrueg has joined #linux-rockchip
<Astralix1> jmcneill, >50MHz and DDR modes work with 1.8V
<jmcneill> this card is in high speed mode not uhs
<Astralix1> Card or eMMC?
<jmcneill> this card
<Astralix1> 3V ist for compatibility mode for cards and 8is allowed for init process of eMMC
<Astralix1> Ah, ok, so you need to have 3.3V
<jmcneill> that's what i'm saying
<Astralix1> I didn't see if you're on Card or eMMC. For eMMC 3V is too high
<jmcneill> mmc0 is not emmc is it?
<Astralix1> firefly?
<jmcneill> no
<jmcneill> rk3188
<Astralix1> which board?
<jmcneill> minix neo x7
<Astralix1> you can connect eMMC or SD to both of the SD/MMC slots
<jmcneill> the datasheet specifically calls one mmc0 and one emmc
<Astralix1> most systems use eMMC on mmc0 and wifi chip as sdio on mmc1
<Astralix1> If no eMMC but NAND is used, SD is most times on mmc0
<Astralix1> and mmc1 is sdio for wifi/bt
<naobsd> Astralix1: jmcneill knows what he inserts to SD slot
<Astralix1> so you'd have good chance that mmc0 is SD if your system has NAND
<naobsd> jmcneill: sdmmc seems to be unstable for me
<Astralix1> hmm... yes. With 3188 only 3.3V is needed as the IP of this dwmmc doesn't support LV and UHX modes
<naobsd> btw now I can read CRU description and clk-rk3188.c...
<naobsd> read -> understand
<naobsd> jmcneill: time to try cpu freq on rk3066/px2 ;)
<Astralix1> Does someone know the *_defconfig for the RK3288 evaluation kit?
<jmcneill> i don't have a px2 board, sorry :)
<jmcneill> lets try 3.3V see if it helps mmc0
<Astralix1> is setting of drive strength implemented now for the GPIOs of RK3188?
<Astralix1> It has been a while since I talked about that with mmind00, but at that time it wasn't
<jmcneill> if you're feeling brave naobsd,
<Astralix1> So you might still discover problems communicating to SD/MMC even voltage is 3.3V now.
<naobsd> jmcneill: sorry, I said about my time :)
<jmcneill> oops DCDC4 not LDO4
<Astralix1> If you want ot step over 10..12MHz on data bus, termination gets critical and if the GPIOs are not set correctly, the problems increase with speed
<jmcneill> 3.3V seems to have done the trick
<jmcneill> ld0: 4-bit width, bus clock 48.000 MHz
<Astralix1> congrats
mrueg has quit [Ping timeout: 250 seconds]
mrueg has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]
cnxsoft has quit [Quit: cnxsoft]
GriefNorth has quit [Quit: WeeChat 1.0.1]
GriefNorth has joined #linux-rockchip
bengal has joined #linux-rockchip
curlymo has joined #linux-rockchip
<curlymo> any os dev's here?
<jmcneill> depends what you mean by that
<curlymo> i want to be able to run a custom compiled kernel and initramfs from my SD card
<curlymo> thereby bypassing the NAND as much as possible
<jmcneill> i'm doing that with netbsd on my rk3188 board
<jmcneill> uboot + kernel + rootfs on sd
<curlymo> i'm using a radxa rock pro, but can't get it to work
<curlymo> can you maybe guide me through it if it is rk3188 compatible?
<jmcneill> sure
<jmcneill> can't be much help with linux but i can walk you through the process i did for netbsd
<curlymo> as long as i can boot a custom kernel + os i'm fine
<jmcneill> README_sdcard.txt pretty much describes what you need to do
<curlymo> already tried but i keep ending up in the NAND kernel + OS
<jmcneill> you have to write idb_sector_0.enc, idb_sector_1, FlashData.bin, FlashBoot.bin, parameter.img to the correct spots
<jmcneill> then based on orig/parameter you have to write your kernel and initrd
<jmcneill> kernel needs to be run through "rkcrc" app from here:
<curlymo> yep, tried it
<jmcneill> two offsets need to be written, kernel and initrd
<jmcneill> for netbsd case i don't have an initrd, but naobsd says they both have to be valid, so i just wrote the kernel to both locations to appease the bootloader
<curlymo> let me try now
<curlymo> just a sec
<jmcneill> ./rkcrc -k /home/jmcneill/netbsd/src/sys/arch/evbarm/compile/obj/ROCKCHIP/netbsd.bin kernel.img
<jmcneill> dd if=kernel.img of=/dev/sdd conv=sync,fsync seek=$((0x2000+0x6000))
<jmcneill> #dd if=kernel.img of=/dev/sdd conv=sync,fsync seek=$((0x2000+0xe000))
<jmcneill> that's my script to copy a kernel -- first offset is kernel, second for initrd
<naobsd> curlymo: if you really want to get help from others, you need to explain more than "I tried it, it didn't work"
<curlymo> ofc
<curlymo> i followed these guides:
<curlymo> first one was invalid ;)
<curlymo> can i download a working kernel from someone to to be sure that's not the issue? Maybe the netbsd one?
<jmcneill> sure, no guarantees it'll work on your board though
<jmcneill> (but it should at least start to boot)
<naobsd> working kernel for RR pro is provided by radxa
<naobsd> why first one was invalid?
<curlymo> because it was your link
<curlymo> not the guide i meant
<naobsd> last one is invalid, it's not for RR pro
<jmcneill> that has already been run through rkcrc
<jmcneill> my rrlite is in the country now, yay
<curlymo> First the README_sdcard.txt
<naobsd> linux-rockchip wiki page has a lot of errors for now, it shouldn't be used for now
<curlymo> i noticed :)
<naobsd> what you need is README_sdcard.txt and serial console output
<curlymo> their kernel doesn't even boot with the default config
<curlymo> i've followed those steps
<jmcneill> oh yeah i should have specified, no hdmi support in netbsd kernel yet, definitely need serial console
<curlymo> do i need to null write the SD to be sure?
<curlymo> i have serial
<curlymo> left over kernel and stuff?
<naobsd> even if kernel supports video out, serial console is required to see what happen around "sd boot" thing
<jmcneill> well video out would tell you which kernel booted :)
<curlymo> so, just following the README_sdcard.txt should work as a first step?
<jmcneill> README_sdcard.txt isn't clear on where you need to write kernel and initrd
<curlymo> that's why i ended up here :)
<jmcneill> > dd if=kernel.img of=/dev/sdd conv=sync,fsync seek=$((0x2000+0x6000))
<jmcneill> > #dd if=kernel.img of=/dev/sdd conv=sync,fsync seek=$((0x2000+0xe000))
<jmcneill> those are the two spots
<curlymo> why is the second commented?
<jmcneill> i don't use initrd for netbsd
<jmcneill> but something valid has to be there
<curlymo> so just write the kernel again
<jmcneill> when i update the kernel (first line) i don't bother writing both, just takes longer
<jmcneill> yeah i wrote it twice, naobsd should probably fix uboot :)
<curlymo> ok wrote the kernel
<naobsd> if you don't flash kernel on SD, and if SD boot is working(this is what we're talking now), it will stop in the middle of boot sequence
<curlymo> ready to boot now?
<naobsd> kernel availability is not so important
<jmcneill> you wrote parameters file too?
<jmcneill> commented out in README_sdcard.txt but also required
<curlymo> no
<curlymo> ok
<curlymo> just following exact steps of you guys because i've been trying for two days now :)
<curlymo> just the dd right?
<jmcneill> yeah
<curlymo> ready to reboot?
<curlymo> just to be sure
<curlymo> these were all steps with the u-boot zip and your kernel:
<curlymo> dd if=idb_sector_0.enc of=/dev/sda conv=sync,fsync seek=64
<curlymo> dd if=idb_sector_1 of=/dev/sda conv=sync,fsync seek=65
<curlymo> dd if=FlashData.bin of=/dev/sda conv=sync,fsync seek=68
<curlymo> dd if=FlashBoot.bin of=/dev/sda conv=sync,fsync seek=100
<curlymo> dd if=parameter.img of=/dev/sda conv=sync,fsync seek=$((0x2000+0x0))
<curlymo> dd if=kernel.img of=/dev/sda conv=sync,fsync seek=$((0x2000+0x6000))
<curlymo> dd if=kernel.img of=/dev/sda conv=sync,fsync seek=$((0x2000+0xe000))
markm_ has joined #linux-rockchip
<jmcneill> sda is your sd card?
<jmcneill> (stupid question i know)
<curlymo> yes
<curlymo> ofc
<jmcneill> i think that's everything
<curlymo> we'll see
<curlymo> finally
<curlymo> next step
<curlymo> did you guys also got a (custom) linux kernel to run?
<naobsd> finally?
<curlymo> it worked
<curlymo> have tried 1000 combinations
<curlymo> let's now see if i can get this to work with my own scripts
<naobsd> I see
<curlymo> first custom compiled but default kernel
<curlymo> for the kernel i need rkrcr -k right?
<jmcneill> yep
<naobsd> curlymo: for (z)Image, yes
<jmcneill> and don't feed it elf or uimage, but raw binary
<curlymo> yep
<curlymo> noticed, but the default compilation OOPSES :s
<curlymo> but well, that's not the point for now
<curlymo> if i want to run a initramfs. How can i load that?
<curlymo> and does it work with the netbsd kernel?
<jmcneill> netbsd does ramdisks differently
<jmcneill> fs image embedded into the kernel itself
<curlymo> no option like in linux kernel to have it separate?
<jmcneill> i guess you could, i just haven't written it yet. i did add support for that on x86 some years ago.
<jmcneill> but that is using netbsd stage 2 loader, not uboot
<curlymo> for now i would just need a /init that would just do a "echo Hello World"
<jmcneill> what board is it? curious to see if the netbsd image i posted earlier works
<curlymo> just kernel, not image
<jmcneill> rrpro right?
<curlymo> Radxa Rock Pro
<jmcneill> the board i'm working on is very similar
<curlymo> i finally want to port XBian
<curlymo> already running on a Raspberry Pi, Hummingboard and Cubox-i
<curlymo> i also compiled u-boot myself. Do you know if i should use or RK3188Loader_miniall.bin?
<naobsd> curlymo: for SD? then u-boot.bin. please see
<curlymo> yep just sd, will try
<naobsd> jmcneill: int error = act8846_set_voltage(ctrl, 3300, 3300); <- error is unused
<curlymo> i'm now at the point i can generate the idb_sector_0.enc idb_sector_1, FlashData.bin (from hex) and FlashBoot.bin (custom compiled) on the fly
<curlymo> next step will be a customized parameters.img
<curlymo> parameters is rkcrc -p right?
<naobsd> curlymo: please see
<curlymo> just want to know if that information is correct
<curlymo> as i said, tried everything at least ones, but not in the correct combination
<curlymo> about the parameters, the CMDLINE is just plain kernel cmdline parameters right? If so, why do we need the initrd and mtdparts in there?
<curlymo> and the KERNEL_IMG should always point to 0x60408000?
<naobsd> I don't know what you tried, but there is no "combination". just work
<curlymo> (i tried the custom kernel i generated with the steps from the radxa website and that didn't work, so the rest also didn't. I just couldn't be sure what the exact issue what)
<curlymo> what = was
<naobsd> curlymo: if you need initrd, you need initrd in CMDLINE. if you need mtdparts, you need mtdparts in CMDLNE
<naobsd> curlymo: you can change address in KERNEL_IMG if you really need
<curlymo> is there good documentation about the parameters file?
<naobsd> there is doc in Android SDK, but I'm not sure it's "good"
<curlymo> as long as it contains correct info
<curlymo> back to the initramfs? Does it has to be inside the kernel? Because the second kernel dd is kernel+initramfs image?
<naobsd> curlymo: it depends how kernel works
<naobsd> curlymo: at first please specify "kernel" you're talking
<curlymo> load mmc 0:1 ${loadaddr} zImage and load mmc 0:1 0x19000000 initramfs.gz
<naobsd> curlymo: "hello world" can be kernel, it will not use initramfs
<curlymo> first need a working linux kernel for the RK3188
<curlymo> the radxa source oopses
<naobsd> curlymo: if you really want to get help from others, you have to explain more than "oopses"
<curlymo> i know
<naobsd> radxa kernel source should work if you configured/flashed properly
<curlymo> just running the netbsd kernel for now
<jmcneill> can you put dmesg somewhere? i'm curious
<curlymo> will do in a second
<curlymo> had to do with hdmi_unregister function
<jmcneill> i meant netbsd, idgaf about linux kernel
<curlymo> netbsd kernel works
<jmcneill> > can you put dmesg somewhere? i'm curious
<naobsd> jmcneill: DCDC4 should be VCC_IO, it's required everywhere, it must be 3.3V very early
<jmcneill> naobsd: uboot should do it if it's that important
<naobsd> sure
<curlymo> ok, doesn't boot w/o initrd and mtdparts
<jmcneill> i find it odd that uboot doesn't restore pmic to sane defaults
<curlymo> just experimenting a bit
<naobsd> it may be a reason that sd boot is unstable ;)
<jmcneill> i'm able to do 48MHz with the proper voltage setting
<jmcneill> awesome, thanks
<jmcneill> looks like an mmc problem there
<jmcneill> ld0: 1-bit width, bus clock 1.338 MHz
<jmcneill> that's clearly wrong
<naobsd> jmcneill: u-boot for rk3288 (based on u-boot 2014.10) does some for pmic, u-boot for rk3188 is old and not maintained...
<curlymo> in my case?
<jmcneill> in your case
<jmcneill> my board is technically a rk3188+, probably some clock reg differences
<jmcneill> thanks for that
<naobsd> I got ld0: 1-bit width, bus clock 3.570 MHz
<jmcneill> when did that start?
<jmcneill> it worked at one point for you right?
bengal has quit [Ping timeout: 244 seconds]
<curlymo> in your kernel, does the CMDLINE determine the root=... or the kernel itself?
<naobsd> ld0c: error reading fsbn 0 (ld0 bn 0; cn 0 tn 0 sn 0)
<naobsd> jmcneill: sdmmc was unstable for me. sometimes it reads partition table etc, sometimes not. I thought it depends SD card
bengal has joined #linux-rockchip
<curlymo> any ideas for a working RR-pro kernel source?
<jmcneill> of course not stable with that bus clock value :p
<naobsd> jmcneill: I changed rockchip_apb_get_rate/rockchip_ahb_get_rate to see CRU_CLKSEL_CON10_PERI_PLL_SEL
field^Mop has joined #linux-rockchip
<naobsd> CPLL: 57129088 Hz AHB: 3570568 Hz APB: 2380378 Hz
<jmcneill> strange
<naobsd> my local change may be wrong
<jmcneill> hm still some power problems i think
<jmcneill> just before urtwn attaches, hdmi gets an unplug event
<jmcneill> ld0: 4-bit width, bus clock 48.000 MHz
<jmcneill> uhub2 at uhub1 port 1: SMSC USB 2.0 4-Port Hub, class 9/0, rev 2.00/b.b3, addr 2
<jmcneill> uhub2: multiple transaction translators
<jmcneill> ithdmi0: display disconnected
<jmcneill> urtwn0 at uhub2 port 3
<jmcneill> urtwn0: Realtek 802.11n WLAN Adapter, rev 2.00/2.00, addr 3
<jmcneill> oh i get that even without urtwn plugged in, huh
<naobsd> curlymo: working kernel source is provided from radxa
<jmcneill> i suppose the port is still powered up
<naobsd> jmcneill: ah, sorry, I remembered that I removed CRU_CLKSEL_CON11_MMC0_PLL_SEL(_MASK)
<jmcneill> hm radxarock.dts sets vdd_hdmi to 2.5V
<jmcneill> lets try that
<naobsd> I think clk src should be selected by CRU_CLKSEL_CON10_PERI_PLL_SEL
<naobsd> and I forgot to do it...
<naobsd> lets try
<jmcneill> nope still disconnect event
<curlymo> ok one more, in the parameters file, the KERNEL_IMG is defined as 0x6040800. Is that because the kernel.img is placed in 0x2000+0x6000 (0x8000)?
<naobsd> curlymo: no, KERNEL_IMG is entry address on ram
<curlymo> so the addresses match by accident?
<jmcneill> how do they match?
<curlymo> the 0x60400000 could be a base_addr with the 0x2000+0x6000 as the respective address from that base
<jmcneill> you said load addr was 0x6040800
<curlymo> that missed a trailing 0
<jmcneill> i see, well i suppose if there are other partitions to load, and you load them in order, and they are fixed sizes, it might make sense to load them at the same offsets
<naobsd> see mtdparts for dd offset
<jmcneill> i plan on eventually using 0x80000000 for netbsd load addr
<jmcneill> (related to 2GB support, don't ask..)
<curlymo> so if i want to change the load address i change the mtdparts
<naobsd> curlymo: no
<curlymo> but i indeed see the addresses match
<naobsd> curlymo: mtdparts is layout for flash storage, KERNEL_IMG is ram address
<curlymo> i understood
<curlymo> but if i want to flash kernel at 0x2000+0x2000 i need to change the mtdparts to 0x00008000@0x00002000
<curlymo> confirmed by testing it
<curlymo> now i at least understand why i need mdtparts :)
jmcneill has quit [Quit: Leaving]
bengal has quit [Ping timeout: 244 seconds]
<curlymo> just wondering, at what location does your first partition start @netbsd
<curlymo> i tried creating a ext2 partition @81920 but it seems to overwrite my sdcard layout we made before
nighty^ has joined #linux-rockchip
curlymo has quit [Quit: HydraIRC -> <- Organize your IRC]
FreezingCold has quit [Ping timeout: 264 seconds]
<FergusL> we'll soon need #linux-intelz3xxx ! and #android-intelz3xxx !
mrueg has quit [Quit: No Ping reply in 180 seconds.]
mrueg has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 245 seconds]
<Astralix1> FergusL, go you have a reference? Since when is the coopoeration a takeover?
<FergusL> sorry Astralix1 ? was just kidding :)
<Astralix1> Ah, it has happened in the past... if you can't beat them... buy them :)
npcomp has quit [Ping timeout: 245 seconds]
<Astralix1> Ok, master branch of firefly works fine too. Had to copy over a parameter too, but after that it works fine.
<Astralix1> A rough walk-throug with Kodi and SPMC show pretty smooth video on 1080p