<naobsd>
rk3036 only 4K size SRAM for SPL, so only support
<naobsd>
timer, uart, sdram driver in SPL stage, when finish
<naobsd>
initial sdram, back to bootrom.
<naobsd>
"back to bootrom" :)
<naobsd>
r1-r14 are saved
<naobsd>
I hope it works with all supported RK socs
hipboi has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
Sadneophyte has quit [Quit: Leaving]
markm has quit [Ping timeout: 272 seconds]
naobsd has quit [Quit: naobsd]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi_ has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
hipboi_ has quit [Read error: Connection reset by peer]
naobsd has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
dowu has joined #linux-rockchip
<dowu>
Hi you all.
<dowu>
question on building rootfs.
<dowu>
After chroot /mnt/ws1
<dowu>
I can not execute "apt-get install ssh vim emacs usbutils wpasupplicant wireless-tools
<dowu>
At this time, apt-get tried to search a site near my place to get package. But the error message is kind of " ... site can not be accessed"
premoboss has joined #linux-rockchip
premoboss has quit [Ping timeout: 240 seconds]
<sjoerd>
nashpa: oh oh oh
<sjoerd>
woops
<sjoerd>
that was for naobsd
<sjoerd>
oh wow it's the rockchip guys themselves doing upstream work
* sjoerd
amazed
<dowu>
right I am working on rockchip
<sjoerd>
dowu: that message is unrelated to rockchip specifically though
<sjoerd>
dowu: can you do LC_ALL=C apt-get ... and pastebin the output of that somewhere
<dowu>
Yes, next time I will post the error message. Thank you.
AstralixNB has joined #linux-rockchip
premoboss has joined #linux-rockchip
<sjoerd>
mmind00: \o/
<sjoerd>
> Is this way of going back to be bootrom generic for other Rockchip SOCs as well?
<sjoerd>
yes
<sjoerd>
From Eddie Cai on the rockchip list
<mmind00>
great ... thankfull soc vendors don't change their way often ;-)
<sjoerd>
Nod
<sjoerd>
I love hardware engineers being just as lazy as software ones
sunilmohan_w has quit [Ping timeout: 252 seconds]
AstralixNB has quit [Remote host closed the connection]
markm has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
masked has quit [Read error: Connection reset by peer]
masked has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 246 seconds]
masked has quit [Read error: Connection reset by peer]
masked has joined #linux-rockchip
masked has quit [Read error: No route to host]
masked has joined #linux-rockchip
pietrushnic has quit [Ping timeout: 240 seconds]
pietrushnic has joined #linux-rockchip
premoboss has quit [Read error: No route to host]
naobsd has joined #linux-rockchip
masked has quit [Read error: Connection reset by peer]
masked has joined #linux-rockchip
<naobsd>
\o/
premoboss has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
naobsd has quit [Quit: naobsd]
pietrushnic has quit [Ping timeout: 265 seconds]
pietrushnic has joined #linux-rockchip
naobsd has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
markm has quit [Quit: Leaving]
amstan_ has joined #linux-rockchip
amstan_ has joined #linux-rockchip
amstan has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
dack has joined #linux-rockchip
dack has quit [Remote host closed the connection]
<naobsd>
oh
<naobsd>
rk3368bl32_v0.1.bin is OP-TEE 0.3.0 based?
AstralixNB has quit [Remote host closed the connection]
premoboss has quit [Ping timeout: 244 seconds]
premoboss has joined #linux-rockchip
<mmind00>
naobsd: possible, but what got you that thought? ... any interesting patch somewhere?
<naobsd>
strings(1) is my friend... I found vendor/rockchip/common/security/optee/ in RK Android 5.1 SDK, and I remembered something named "trust" in u-boot for RK3368
<mmind00>
:-D
<mmind00>
naobsd: does that directory contain sources or just a binary?
<naobsd>
only binaries ;)
<naobsd>
hm, it seems rk3368bl31 bin contains ARM ATF bl31 code
<naobsd>
rk3368bl30 seems to be something for MCU (but I don't know anything about MCU in rk3368)
<naobsd>
everything for "trust" things for RK are binary only...
<naobsd>
my knowledge about secure/hyp things on ARM is very very poor ;)
<naobsd>
if u-boot for rk3368 is configured as CONFIG_SECOND_LEVEL_BOOTLOADER, miniloader does some things for mcu and secure world, then run u-boot
<naobsd>
if it's primary loader (w/o miniloader), everything is done (or not) by u-boot
<naobsd>
probably psci is provided by bl31
<chris2>
naobsd: which hw are you hacking on?
<naobsd>
chris2: I have many boards with Rockchip SoCs
<naobsd>
chris2: about RK3368, I have Tronsmart Orion R68 Meta
<chris2>
can you recommend anything with runs a mostly-vanilla kernel, has ethernet preferably gbit and costs <120€?
<naobsd>
chris2: with RK3368?
<chris2>
with any arm64
<chris2>
that r68 meta sounds good
<chris2>
how hard is it to flash a custom linux?
<naobsd>
flashing is not hard with rk3368. rkflashtool works, SD boot is possible
<chris2>
ah, cool
<chris2>
so i can put kernel and initrd on sd, and somehow enter uboot or something and it will work?
dowu has quit [Ping timeout: 246 seconds]
<naobsd>
u-boot for RK3368 functionality is limited, it loads kernel, dtb, and ramdisk from specific location of flash memory
<naobsd>
but you can put kernel/dtb/ramdisk freely
<chris2>
are there any docs on this?
<chris2>
ok
<naobsd>
if you use on-board flash, just run "rkflashtool w (partition name) < (image)"
<chris2>
onboard flash is the 16gb emmc?
<naobsd>
yes for orion r68 meta
<chris2>
ok
<chris2>
so when i buy such a thing with android preloaded, how do i get to flash it?
<naobsd>
what you want to do is developing aarch64 linux, right?
<chris2>
yes
<chris2>
and server hw is too expensive
<chris2>
i'd just buy a chromebook, but i'm tired of waiting
<naobsd>
4 holes of upper-left corner of eMMC(FORESEE) is the switch which enforces mask rom mode (which might be needed if you flashed non-working bootloader)
<naobsd>
good cheap board for development ;)
<chris2>
yeah, sounds good
<naobsd>
but there is no schematic etc
<chris2>
is this the same hw as beelink btw?
<naobsd>
generally yes, but I'm not sure beelink i68 _GbE verison_ is available
<chris2>
ok
<chris2>
the ones i see on ebay only have 100mbit according to description
<naobsd>
board is made by netxeon
<naobsd>
there might be some other products which uses same board
<naobsd>
but, some parts such as ethernet, wifi, flash memory, might be different
<chris2>
yeah
<naobsd>
I bought it from geekbuying
<chris2>
i need shipping to germany
<chris2>
geekbuying page is broken :P
jas-hacks has joined #linux-rockchip
gb_master has joined #linux-rockchip
gb_master has quit [Quit: Leaving]
Apocx_ is now known as Apocx
cristian_c has joined #linux-rockchip
markm has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
jas-hacks has left #linux-rockchip [#linux-rockchip]
cristian_c has joined #linux-rockchip
nashpa has quit [Ping timeout: 240 seconds]
nashpa has joined #linux-rockchip
Sadneophyte has joined #linux-rockchip
<Sadneophyte>
Hey I was wondering if anyone has gotten the bluetooth stack to work on an rk3288 machine. I am on the asus c201p. From the chromeos I can get .hcd firmware, but getting brcm_patchram_plus working is a little difficult...
<amstan_>
Sadneophyte: +1, i would like to know that too
<amstan_>
i was missing my bluetooth speakers yesterday
<Sadneophyte>
lolllol! I spend the last 30 minutes reading the sillyness on his site and thinking about emailing him...
<amstan>
Sadneophyte: he was in this channel a few times too
<amstan>
greggypoo i think
<Sadneophyte>
here is a test too... try to get them to work with the chrome-crap. bluetoothctl registers the hci0 stuff, but it cannot pair with my phone for instance. I however have no chrome-foo
<amstan>
i didn't even get a device
<Sadneophyte>
on chrome?
<amstan>
my bluetooth manager said no devices found
<amstan>
what chrome?
<Sadneophyte>
I think we should be able to find out how chrome is doing it. the chrome side has a bunch of .hcd firmwares in the /lib/firmware directory, apparently for the brcmmac. also greg was using the 3.8 wireless kernel modules from what I gleaned on his post
<Sadneophyte>
chromeos should have the bluetooth running
<Sadneophyte>
brb
<amstan>
Sadneophyte: arch uses 3.8 too
<amstan>
yes, chromeos does have bluetooth running
<Sadneophyte>
I also have no hci device on my arch...
<Sadneophyte>
amstan I had offtopic arch stuff to tell you too, but maybe we should do that in the arch linux arm channel...
<Sadneophyte>
amstan did you have any luck installing debian on the rk3288 I saw a post on reddit from you...
<Sadneophyte>
although you were trying to help another gentleman...
<amstan>
i didn't personally install debian, it should be pretty trivial though
<Sadneophyte>
the search is google:veyron patchram 4354 bluetooth
* amstan
thanks steev
<amstan>
that's a very specific search, lol
<amstan>
if it wasn't for steev you wouldn't have found it
<Sadneophyte>
line 2306
<steev>
amstan: to be fair, I just took the upstart script and modified the udev rule to run the command
<Sadneophyte>
amstan the firmware is special for the patchram, you can find it on the chromeos partition
<amstan>
arch doesn't come with it? it does with the wifi driver
<Sadneophyte>
steev, thank you. How come all of you guy can linux!
<Sadneophyte>
all I can is google!
<steev>
experience
<Sadneophyte>
there is a question about the sdio_id
<Sadneophyte>
here it is 02D0:4354
cristian_c has quit [Quit: Bye]
<Sadneophyte>
and the port description port /dev/ttyS0 could not be opened, error 2
<Sadneophyte>
amstel, but I am confused, I already have a "/usr/lib/udev/rules.d/99-veyron-brcm.rules"
<Sadneophyte>
so that rule and the rule from steev are the same, now the question is does it work... because I can't tell... it just writes and rewrites...