<libv>
i am not there yet, i am currently quite appalled at the state of the documentation and trying to figure out the first steps to take
<npl_>
I have the board since over a year, just don't have much time for playing with it
<npl_>
First thing I did, was getting the propietary loader removed, too much hidden magic
<libv>
i feel like it's 2012 again, when i started out with sunxi, i do not plan to rewrite a whole wiki here myself, again
<libv>
i am happy i got the original android on the mmc to boot, and still figuring out what to do to get SD booting going
<libv>
and i think i have owned this hw since january 2015
<libv>
which incidentally seems about the right age for the information out there
<libv>
which is just appalling.
<lkcl>
libv: i'll have an EOMA68-RK3288 first prototype probably in 3-4 weeks time so will help do some research
<npl_>
Afar, you have to remove the misc partition to boot from sd
<lkcl>
libv: i thought 2 years would be enough time to get.. _something_ out there, too!
<npl_>
As saud. Hidden magic
<npl_>
But atleast the mainline kernel support is quite good
<lkcl>
libv: there's a guy (chinese) who's just started working for rockchip, known as ayaka on here during weekends and as stdint when he's at work
<lkcl>
libv: he's helping out a _lot_
<libv>
i do not want to wait weeks and spend days asking people what to do
<libv>
i had expected a popular device like the firefly or the c201 to have a halfway useful wiki page, which points to some halfway useful bootloader/u-boot and kernel pages
<libv>
and there just is nothing.
<lkcl>
libv: give me a few weeks. i'll get something sorted out. i have to get a dev-kit anyway
<libv>
lkcl: to me it is very important to have a good SoC wide community
<npl_>
Hmm, would be willing to help out with what I could scrap together
<libv>
with a solid SoC wide wiki
<npl_>
Just don't know where
<lkcl>
npl_: cool.
<libv>
and not to have halfarsed info at bpi.org, opi.org, nextthingco.org
<lkcl>
libv: tell me about it :) there's rockchip.fr as well, don't forget that!
<libv>
like what seems to be where sunxi is heading now that i have had to spend that much time with a customer before
<lkcl>
libv, npl_ : i'll track stuff down, i'm committing at least $2k to get the EOMA68-RK3288 made so i have some serious motivation to get good solid info out there
<lkcl>
does anyone know of a good RK3288 board that's reasonably low-cost?
<lkcl>
npl_: are you using the firefly as well?
<npl_>
Yes
<lkcl>
npl_: ok, makes sense for me to get one then. work for you, libv?
<npl_>
Ran Debian + Linux 4.8 on it, trying now to unmess what I did
matthias_bgg has joined #linux-rockchip
<libv>
and now that i need my firefly for a bit, i find that i am back where i started in the summer of 2012, when the only info out there was written together on lkcls site :)
<libv>
npl: ok, i need to get some rugby stuff for my girlfriend on a usb stick, but i will add some structure to the firefly page after that
<libv>
konversation went down well with the (clueless) automotive guys i worked for the last 1.5ys
<lkcl>
npl_: http://rhombus-tech.net... it's an ikiwiki i threw together 5 years ago, which is turning out to be reeeal handy now i'm in china a lot, and the internet access is 10-15k PER SECOND
<libv>
so that is a low hurdle
<libv>
lkcl: sorry, imho the info should go to the mediawiki in the /topic.
<libv>
SoC communities go much much further and have the ability to have much more relevant and up-to-date information than device specific communities.
<lkcl>
libv: yeah can do.. i do however need some EOMA68-specific boot-up info
<libv>
that's what i swear by and i've been with sunxi since it moved itself out of #arm-netbook
<libv>
lkcl: in that case, it's up to you, but being able to link to SoC specific but device generic bootloader/kernel/otherthingies pages makes life a lot easier, as software changes all the time
<lkcl>
yeah that's the plan... but i just have to see if the internet access is completely f****d or not when i'm in zhuhai
<lkcl>
alright, back to sleep for me
<libv>
'night!
premoboss has joined #linux-rockchip
npl_ has quit [Ping timeout: 260 seconds]
dlezcano has quit [Ping timeout: 260 seconds]
<libv>
oh yeah, -reload definitely has to be the same wiki page...
<libv>
*rolls eyes*
nasuga has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 258 seconds]
premoboss has quit [Quit: Sto andando via]
<npl>
libv: I am trying to remember how I got my board in this state, to write the steps down. Funny enough the references I find often come up with stuff that wouldn`t work for me
<npl>
probably depending on the 2 year old linux installations the board shipped with, they refernce the eMMC with /dev/mmcblk0 while its /dev/mmcblk2 for me