naobsd has quit [Remote host closed the connection]
naobsd1 has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
Tony has joined #linux-rockchip
<Tony>
naobsd1, hi, my problem had resolved. ;)
<Tony>
naobsd1, about the lcdc problem. the are four screen after resume.
<Tony>
naobsd1, the real problem is that there are two way to init LCD timmings.
<Tony>
naobsd1, uboot or kernel. If you enable uboot init LCD then kernel won't do init until resume.
<Tony>
naobsd1, then, I disable the uboot, and fix the timming for LCD, the it works fine.
GriefNorth has quit [Quit: Konversation terminated!]
premoboss has quit [Ping timeout: 255 seconds]
nighty^ has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
amstan has quit [Ping timeout: 272 seconds]
amstan has joined #linux-rockchip
amstan has joined #linux-rockchip
wildea01 has joined #linux-rockchip
GGflags has joined #linux-rockchip
<rperier>
mhhh chapter about "Linux memory management" in LDD v3 is... nice... not completly trivial but nice anyway (very well explained), I think that after this chapter I will have some non-contiguous parts of my brain :D
<naobsd1>
Tony: sounds good :)
Tony has quit [Ping timeout: 272 seconds]
Tony has joined #linux-rockchip
sawtooth7 has joined #linux-rockchip
<sawtooth7>
so the RKNanoD will support Linux ? :)
Tony has quit [Quit: Leaving]
sawtooth7 has quit [Remote host closed the connection]
sawtooth7 has joined #linux-rockchip
sawtooth7 has quit [Remote host closed the connection]
sawtooth7 has joined #linux-rockchip
sawtooth7 has quit [Remote host closed the connection]
sawtooth7 has joined #linux-rockchip
naobsd1 has quit [Quit: naobsd1]
sawtooth7 has quit [Ping timeout: 256 seconds]
sawtooth7 has joined #linux-rockchip
markm_ has quit [Ping timeout: 250 seconds]
<rperier>
sawtooth7: it might run uclinux (as the cortex-m3 has no MMU), however, it has few KB of RAM, so I don't think so
premoboss has joined #linux-rockchip
<rperier>
it would be interesting to look at the "tinifycation project" for these kind of targets, imho (I don't know what is the project status...)
<rperier>
well, except if you can add external RAM
<sawtooth7>
i don't think you can according to what i see on the datasheet
markm_ has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
sawtooth7 has quit [Remote host closed the connection]
sawtooth7 has joined #linux-rockchip
<karlp>
it's not super interesting to try running linux on them, just for th sake of it.
<karlp>
there's a few other m4/m0 combo chips around, haven't seen an m3/m3 combo before that I recall though honestly
<sawtooth7>
yeah they mention also FreeRTOS for it, i think it makes much more sense indeed
<sawtooth7>
but seeing cortex m3 running at 300 MHz on a 55nm process is quite cool
<karlp>
I guess they ddin't license m4f
<rperier>
even if I agree with you (because linux is too big to run on these kind of SoCs and has a lot of unrequired features, and also because most of the time a good RTOS for IOT is enough) , that's very frustating. I mean, nowadays linux is able to run on everything except SoCs with very few Kb of RAM
<sawtooth7>
yeah that chip is specifically designed for IOT, so i'm not sure what would be the use of linux here
<sawtooth7>
i'm seeing a big craze about apple watch copies here in SZ
<sawtooth7>
some use just very basic bluetooth IC to do everything (that is, not much)
<sawtooth7>
but some use some cortex-A chips with 512MB ram, etc ... running android
<sawtooth7>
and obviously those are bulky and don't look that great :D
field^Mop has joined #linux-rockchip
<sawtooth7>
those IOT stuff, they often just need an external wifi or BT chip and that's it
<karlp>
rperier: pretty sure linux gave up on small socs. therew was a lkml post not too long ago something along the lines of, "if you want to run on such small hardware, you might be best sticking with linux 2.4.x"
<rperier>
Yeah I know, I was thinking to recent linux kernel, the problem is that even if linux is a general purpose operating system, it is used by a thousand of embedded devices in the world, so try to improve its size would make sense, imho. (however, a lot of people disagree in mainline)
<rperier>
you can also use projects like "uclinux" however, even uclinux is too big
<rperier>
however, for very basic embedded software, an RTOS does the trick most of the time. I mean, if you only need few tasks, with few network communication an RTOS with a "round robin" scheduler algorithm is enough
<rperier>
on the opposed side, if you need a lot of threads or process, with a complex network tasks , a lot of I/O and an huge load, linux is for you
<rperier>
at least, this is my point of view
<sawtooth7>
i agree
<sawtooth7>
and if you need that many threads, it makes sense you want more RAM ...
sawtooth8 has joined #linux-rockchip
sawtooth7 has quit [Ping timeout: 248 seconds]
<karlp>
linux is for when you want netWORKing
Tsou has joined #linux-rockchip
<Tsou>
Hi !
<Tsou>
Did anyone ever use a RK3188-SOM-EVB from Olimex? I'm using it for the first time and have some difficulties to start the board
<sawtooth8>
have you tried #olimex ? ;)
<rperier>
+1, ask on #olimex first and feel free to ask here if they are unable to help you
<Tsou>
Ah, I didn't think about that, I only saw #linux-rockchip, I'll try, thanks :)
amstan has quit [Read error: Connection reset by peer]
amstan has joined #linux-rockchip
amstan has joined #linux-rockchip
field^Mop has quit [Ping timeout: 264 seconds]
field^Mop has joined #linux-rockchip
Bludot has joined #linux-rockchip
field^Mop has quit [Ping timeout: 276 seconds]
sawtooth8 has quit [Quit: .]
jas-hacks has joined #linux-rockchip
field^Mop has joined #linux-rockchip
JohnDoe8 has joined #linux-rockchip
<Tsou>
They seem to be asleep on the #olimex ^^ Did anyone ever use RK3188? I'm trying to install linux on it but the process seems different from raspberry pi/arduino so I've some difficulties