<naobsd>
I'm not sure that I can follow "do not fork community(resource?place?)"
VargaD_ has joined #linux-rockchip
<naobsd>
because I still think there was no community like as linux-sunxi
<naobsd>
I just want new place for new activity
VargaD has quit [Ping timeout: 250 seconds]
VargaD_ is now known as VargaD
<naobsd>
same name, same place. ah, it shouldn't be fork :)
naobsd has quit [Quit: Page closed]
ferric has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd>
I changed my mind a little
<naobsd>
I want to discuss thing like "how to organize linux-rockchip community"
<naobsd>
but most people(include me) don't have so much interest about it
<naobsd>
so, I'll just do(start) what I want to do when I can do
<naobsd>
btw
<naobsd>
I prefer linux-rockchip.org than linux-rockchip.info...
<naobsd>
but probably it really looks like "fork" :(
<naobsd>
comments are welcome, of course
<naobsd>
I just said I don't wait forever :)
naobsd has quit [Quit: Page closed]
hipboi has quit [Ping timeout: 252 seconds]
GriefNorth has joined #linux-rockchip
naobsd has joined #linux-rockchip
hipboi has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.0]
GriefNorth has joined #linux-rockchip
hipboi has quit [Ping timeout: 246 seconds]
hipboi has joined #linux-rockchip
dlezcano has joined #linux-rockchip
Yao_ has quit [Quit: Leaving]
Bludot has quit [Quit: Connection closed for inactivity]
naobsd has quit [Quit: Page closed]
cristian_c has joined #linux-rockchip
<cristian_c>
Hi
<cristian_c>
I'd like to install a linux distro on a micro-sd card
<cristian_c>
Where can I find a how-to/tutorial?
<cristian_c>
Any ideas?
GriefNorth has quit [Quit: WeeChat 1.0]
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
cristian_c has quit [Ping timeout: 245 seconds]
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
hipboi has quit [Quit: Leaving]
cristian_c has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
<cristian_c>
The server has disconnected me
<cristian_c>
Has anyone answered to me?
hipboi has joined #linux-rockchip
akaizen has joined #linux-rockchip
<viric>
no
<cristian_c>
ok
<hipboi>
upgrade_tool sd can switch device from android adb mode to loader mode
Guest73228 is now known as RaYmAn
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
hipboi has quit [Ping timeout: 246 seconds]
hipboi has joined #linux-rockchip
nighty^ has joined #linux-rockchip
cristian_c has quit [Quit: Sto andando via]
rz2k has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.0]
irsol has quit [Ping timeout: 276 seconds]
<karlp>
mmind00: that "preserve important clocks" patch from you and mike turquette, does that not apply to rk3066 as well? I saw changes for 3188 and 3288?
irsol has joined #linux-rockchip
<mmind00>
karlp: the clock trees of rk3188 and rk3066 (and most likely all soc from that series) only differ minimally
<mmind00>
so if you look at drivers/clk/rockchip/clk-rk3188.c you'll see that it also contains the rk3066 specifics
<mmind00>
and the critical clocks are defined for both in the common clock
<karlp>
gack, the naming of things in those files is so confusing :|
<karlp>
rk3188_pll_rates _only_ contains RK3066_PLL_RATE defines and so on :|
<karlp>
I know it's uncool, but would a description in the top of the file indiccating applicability be somewhat useful?
<mmind00>
karlp: yes, the naming is a little unfortunate ... everything should be rk3066 with the rk3188 being the addon, but I also don't think there will be a lot of changes except maybe adding more similar socs in the faaaar future if at all [I don't think anybody has access to the relevant TRMs], so I'm not to worried
<mmind00>
karlp: so if it irks you to much, send a patch to the lists adding your desired comment ;-)
<karlp>
no, I don't understand enough to know what the comments should be :)
<karlp>
just trying to follow along with developments, and the names and changes don't give the indications of how broad they are :)
viric has quit [Ping timeout: 246 seconds]
hipboi has quit [Quit: Leaving]
viric has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd>
is there any official kernel source for rk3288 evb from rockchip?
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
<mmind00>
naobsd: I guess only the rkchrome github repo
<naobsd>
hmm
<naobsd>
mmind00: I see, thanks!
<naobsd>
hmm, rk u-boot for rk3188 seems to be working
<naobsd>
miniall -> uboot.img -> kernel
<naobsd>
everything on nand
<naobsd>
oh well
<naobsd>
rk uboot supports u-boot image format? what I tried is RK kernel(KRNL) image format
<naobsd>
oh
<naobsd>
upgrade_tool di doesn't understand uboot partition
<naobsd>
no one use uboot on NAND as 2nd level loader? ;)
<naobsd>
upgrade_tool wl 0x2000 uboot.img works (upgrade_tool in RK3288 SDK is required)
<ganbold_>
naobsd: u-boot on radxa?
<naobsd>
ganbold: yes
<ganbold_>
naobsd: cool
<ganbold_>
naobsd: does network boot work?
<naobsd>
I cannot enter uboot prompt for now (probably I need to stop autoboot)
<ganbold_>
naobsd: that way it would be even easier to test new kernels
<naobsd>
and probably ethernet is not enabled
<ganbold_>
if ethernet is enabled then that is perfect
<naobsd>
btw, barebox supports (only) ethernet
<naobsd>
I guess
<naobsd>
rk u-boot doesn't support (u-boot generic) mmc
<naobsd>
rk specific mmc (for boot from emmc/sd) should be supported but
<naobsd>
and probably no usb...?
<naobsd>
I guess: rk u-boot can be used as like as rk loader, it can load images from kernel/boot/recovery
<naobsd>
that's all?
<ganbold_>
ethernet support is preferable
<naobsd>
it's u-boot
<naobsd>
we can update/add driver
<naobsd>
if we have time :)
<naobsd>
btw, it's U-Boot 2014.01 based
<naobsd>
u-boot for RK3288 (rkchrome) is newer than u-boot RK3188 (radxa)
akaizen has joined #linux-rockchip
<naobsd>
haha, it seems u-boot in firefly SDK is newer than rkchrome/uboot ;)
<viric>
what is a firefly?
<viric>
in this context
<ganbold_>
rk3288 board
<naobsd>
hmm, there are many diffs between rkchrome/kernel/master and firefly sdk kernel
GriefNorth has joined #linux-rockchip
<naobsd>
probably firefly's kernel is better
<naobsd>
at least it's rbox sdk ;)
<naobsd>
ah
<naobsd>
with u-boot on RR
<naobsd>
3.0 based kernel doesn't boot
<naobsd>
well
<naobsd>
kernel starts, but it reset just after [ 0.441898] DDR Version 1.04 20130830
<naobsd>
mainline based kernel can be booted, probably it doesn't touch DDR configuration
<naobsd>
sleepy
<karlp>
yay, minix has replied somewhat more positively about getting kernel source. might get a bit further soon
ferric has quit [Ping timeout: 264 seconds]
nighty^ has quit [Quit: Disappears in a puff of smoke]
viric has quit [Ping timeout: 268 seconds]
viric has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
FreezingCold has quit [Ping timeout: 240 seconds]
FreezingCold has joined #linux-rockchip
<sonnyrao_>
mmind00: around? Was wondering if you had opinions about suspend/resume on rk3288
<mmind00>
sonnyrao_: only glanced at it shortly this morning ... I guess dianders comments are a good startingpoint
amstan_ has joined #linux-rockchip
<amstan_>
hello
<sonnyrao_>
sonnyrao_: k, I don't know what u-boot is doing, but we're still figuring it out for our firmware.... I think we'd prefer a solution where we don't involve the firmware in suspend/resume
amstan_ is now known as amstan
<sonnyrao_>
oops!
FreezingCold has quit [Ping timeout: 245 seconds]
<sonnyrao_>
mmind00: meant to send that to you.... but sometimes I talk to myself so I got confused :-P
<mmind00>
:-D
FreezingCold has joined #linux-rockchip
<sonnyrao_>
mmind00: is S2R supported on rk3188 or rk3066 ?
<mmind00>
sonnyrao_: in mainline? Currently there is no suspend whatsoever there
FreezingCold has quit [Remote host closed the connection]
<sonnyrao_>
mmind00: yeah, mainline. Ok, so there's no current solution to use as a precedent
<mmind00>
sonnyrao_: correct ... from what I gathered the suspend support is also more complex on the earlier socs ... the rk3288 seems to be able to switch of the ram on its own for example
<mmind00>
s/of/off/
<sonnyrao_>
mmind00: ah ok. So we're blazing new territory here, since we dislike putting things in firmware (harder to update), we may also take Julius's idea of using a firmware blob that is loaded from the filesystem. This is what we are currently doing for tegra based systems
srao has joined #linux-rockchip
srao has quit [Client Quit]
<mmind00>
sonnyrao_: sounds nice ... especially as this blob could then simply be moved into the bootloader later if necessary
<mmind00>
so we could essentially make both worlds happy :-)
<sonnyrao_>
ok so you're okay with that approach.. cool