ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hramrach_ has quit [Remote host closed the connection]
hramrach_ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hipboi has quit [Ping timeout: 260 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cyrozap has quit [Ping timeout: 260 seconds]
cyrozap has joined #linux-rockchip
hipboi has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hipboi has quit [Ping timeout: 245 seconds]
naobsd has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hipboi has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
hipboi has quit [Ping timeout: 272 seconds]
RayFlower has joined #linux-rockchip
hipboi has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
GriefNorth has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
benja is now known as benja`
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 260 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 260 seconds]
wildea01 has joined #linux-rockchip
arokux has joined #linux-rockchip
nighty^ has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
bengal has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
RayFlower has joined #linux-rockchip
<hramrach_> hello
naobsd has joined #linux-rockchip
<hramrach_> looks like somebody is vandalizing the wiki. Like removing all the links to useful information from the main page
<hramrach_> hmm, it's naobsd by the logs
<naobsd> hramrach_: yes
<hramrach_> the wiki sure could use more organizing but you do not organize things by moving everything around and breaking all links in the process
<hramrach_> it just creates more chaos
<naobsd> breaking all links?
<hramrach_> like when something referred to [[rkutils]] and now it's OBSOLETE/rkutils or whatever
<naobsd> _all_ links?
<karlp> hramrach_: pull the actually still relevant and useful stuff back to the main page as appropriate
<naobsd> and for example, do you think rkutils page contain useful information?
<karlp> (he possibly went a bit far for the first step)
<hramrach_> naobsd: I did not check thoroughly. however, this page http://linux-rockchip.info/mw/index.php?title=Installing_new_kernel_image has link to rkutil at the bottom which is broken ad looking at the logs that page has been moved
<hramrach_> I do not know if the information is useful but now the link is lost
<hramrach_> naobsd: it has just a link to your undocumented rkutils in the hope that some day somebody who has need to use them figures out how they work and documents them
<karlp> no, it's not lost, what page are you seeing with a broken link?
<hramrach_> if you follow the broken red link it gives you a page that tells you the page has been moved. So it is not lost but since the link appears broken it's not likely a reader will follow it
<naobsd> "someone" can write rkutils page
<hramrach_> yes, probably
<hramrach_> I read most of the wiki at some point
<hramrach_> it describes rkcrc which is 1/5 of those tools. but sure an improvement
<naobsd> what's the problem? link to rkutils is available on that page with some useful information
<naobsd> (link to rkutils on github)
<hramrach_> and another page with some usful information is now not reachable from the main page and has a broken link to rkutils
bengal has quit [Ping timeout: 240 seconds]
<naobsd> is link to unuseful page useful?
<hramrach_> naobsd: the point was that the rkutils page had a software tag so it would show up in list of rk relevant software even if it had no information about the software
<hramrach_> and organizing the wiki happens not by moving wholesale everything to OBSOLETE namespace but by picking that bit of rkutil information in the building kernel page and either moving it to the rkutil page or linking to the relevant section of building kernel pabe from rkutil page
<naobsd> I never said that I finished wiki things :(
<naobsd> anyway, I understand
RayFlower has quit [Read error: Connection reset by peer]
<naobsd> make all pages perfect at once, otherwise keep incomplete page and don't make them halfway
RayFlower has joined #linux-rockchip
<hramrach_> and the first does not happen
<naobsd> oh, then, only incomplete pages are available
<hramrach_> the pages are never perfect
<hramrach_> there is always more information to be found and recorded in the wiki
<naobsd> I'll restore all pages I marked OBSOLETE
<hramrach_> thanks
<naobsd> someone will make them perfect at once
<naobsd> I just wait
<hramrach_> as said there is no such thing as perfect page
<naobsd> oh sorry, "make them better" than missing link to incomplete page
<naobsd> please organize linux-rockchip community well
<hramrach_> naobsd: it is not in the power of single person to organize a wiki, even this small wiki
<karlp> naobsd: it's ok, we'll get there, don't get so stressed about it :)
<hramrach_> unless you want to take a week or two off at work and do nothing besides page editing
<hramrach_> that's why it is a wiki
<hramrach_> when you see something out of place or missing you can move or add it a piece at a time
<naobsd> I'm not a first person "let's revive community"
<naobsd> who said "let's..."
<hramrach_> you can achieve much revival by editing the main page to give it a new fresh look ;-)
<naobsd> I'll transfer owner rights to...who?
<hramrach_> owner rights of what?
<karlp> naobsd: relax
<karlp> no-ones asking to take over
<karlp> you just moved a lot of pages to obsolete without anything coming back, people are starting to get more active, we're getting better, it's imrpoving.
<karlp> hramrach is going to do a littl ebit now, more will get done, it's all ok.
<naobsd> I'm sorry, but I read pages I marked OBSOLETE and I really thought it's not useful at all
<hramrach_> when it's the only page that has the information it sure is useful
<naobsd> I want to ignore(delete) then, and I want to refine remaining pages
<hramrach_> look like the person writing about boot sequence knows nothing but all is already recorded in the obsolete pages
<karlp> hramrach_: that's me, I've tried to start by making a page that others can then fix,
<hramrach_> that was the same with the rkutil page long time ago
<naobsd> anyway
<naobsd> I'll become just a member
<naobsd> I will not care if community things will be going to dead again (hopefully not)
<hramrach_> naobsd: you become leader by becoming active in the community. your activity then attracts more people.
<naobsd> fortunately at lease I'm active now, anyone who can care about community resources such as IRC, google groups etc can talk to me
<naobsd> I just wait & see
<hramrach_> however, trying to manage things too much tends to pan out poorly. If you move all current pages to obsolete section it suggests that they are not completely worthless (not deleted) but should be rewritten. But who does the rewrite when you yourself do not?
<naobsd> only useless(I thought) pages were marked as OBSOLETE
<naobsd> not all
<naobsd> and I never said wiki refresh was finished
<hramrach_> the refresh takes time. in that time the wiki should still be usable
<naobsd> I really wanted to obsolete old pages
<naobsd> well
<naobsd> I really wanted to obsolete old pages (not all pages)
<naobsd> and old pages not marked OBSOLETE is still alive
<hramrach_> note that wikipedia which has more experience in that area starts by *flagging* the pages as obsolete and/or otherwise non-well
<hramrach_> which does not break the structure but makes the pages stand out
<naobsd> I didn't break any structure except OBSOLETE-ed page
<naobsd> anyway
<naobsd> I don't have enough experience
<naobsd> please do it, I never said "don't update it"
<naobsd> (I will restore OBSOLETE pages)
<hramrach_> now you see that moving away many pages is disruptive to wiki content so you have more experience ;-)
<naobsd> terrible, I have to approve join request on google groups :(
<hramrach_> probably group setting
<naobsd> I didn't disrupt
<hramrach_> but I don't run any google group so I would not know how it's set
<naobsd> OBSOLETE-ed pages were disrupted long time
<naobsd> I had to use some time to learn about google groups
<naobsd> but I'll not care about it anymore
<naobsd> then, who cares google groups?
<hramrach_> naobsd: the obsoleted were untouched and incomplete for a long time. By moving them you you make them incomplete and harder to find so it adds problems.
<naobsd> I wanted to delete them soon
<naobsd> then it's not problem
<naobsd> same as "a page which is not created yet"
<hramrach_> then it's even worse problem because the information in them is lost
<naobsd> is there any useful information?
<naobsd> I don't want to use more time to think "is this still correct? useful? (etc)" for those pages
<hramrach_> then flag them as pages of dubious value.
<naobsd> sorry, I don't know how to do it
<hramrach_> but you see that the boot sequence page which happened after your main page remodelling has problem re-collecting the information already collected in the obsoleted pages
<naobsd> please specify which page contains it
<hramrach_> naobsd: I added links tot he page
<hramrach_> naobsd: flagging is simply achieved by adding pages to a category and putting a big fat notice in the page text
<hramrach_> there are other ways for sure, this is an example that works reasonably well for many wikis
<hramrach_> naobsd: but the obsoleted main page had a list of rk SoCs with boot capability
<naobsd> http://linux-rockchip.info/mw/index.php?title=OBSOLETE/Main_Page#List_of_Rockchip_SoC.27s is surely OBSOLETE-ed but
<karlp> hramrach_: which bits were on other pages? I've tried to collect the othter stuff, and externals
<karlp> I was talking abotu boot sequences, not just a list of "nand, emmc, sd, usb"
<hramrach_> this is a prime example. if you think that is not information to put on main page which is fine create a page for list of SoCs and move that bit
<hramrach_> karlp: in that page you can see that some chips like 3066 cannot boot off mmc at all. in the installing kernel page you have the sequence
<naobsd> karlp tried(are trying) to add/confirm more than few words in the table
<karlp> ^^^
<hramrach_> yes, the table is from datasheets and is not tested
ganbold__ has quit [Ping timeout: 245 seconds]
<hramrach_> I don't know who wrote the installing kernel page and what source was used for it
<hramrach_> but with that you have something to verify, you don't start from zero
<naobsd> unfortunately
<naobsd> in rockchip users' community
<naobsd> there are a lot of "wrong but believed as true" information
<hramrach_> if you can disprove it then correct it
<naobsd> (I don't say all info on our wiki is it)
<hramrach_> if you cannot then you do not know it's wrong
<naobsd> but some(many?) of such information is just a someone's random idea
<naobsd> I don't want to confirm such information
<naobsd> recently
<hramrach_> then it's not important
<naobsd> someone asked "you(naobsd) should have secret patch to use gen2 loader in JB rom, please open it"
<naobsd> it doesn't exist
<naobsd> I had to use some time to confirm "it just work, no secret"
<hramrach_> then post on wiki or your blog or whereever how to make it work if you care about such rumours
<naobsd> I'm sorry
<naobsd> I must be wrong
<hramrach_> you are not oblidged to document your software
<naobsd> but I don't want to care about someone's random idea
<naobsd> oh, I want to write about _my_ idea
<naobsd> but I'm feeling something strange
<naobsd> everytime I answered someone's question
<hramrach_> but if you do not document it enough for others to replicate your success it can give rise to such rumour easily
<naobsd> everyone said "write wiki, it is the open community"
<naobsd> no one (except karlp) said "ok, I understand it, let's write wiki!"
<naobsd> sorry
<naobsd> I shouldn't talk anything for now
<naobsd> I should take a rest
<hramrach_> I wrote in the wiki everything I gathered from this channel and seemed important enough that somebody else might want to know
<hramrach_> I don't care about Android, much less about JB but some people do. And if you managed to build a ROM and the other people do not they might think you have a secret code patch
<naobsd> (of course I know "everyone/no one" is inaccurate)
<hramrach_> of course, the 'patch' might be in the way you built your rom. some configuration options, the exact compiler, exact kernel source, and whatnot
<naobsd> I don't want to talk about _us_ for now
<hramrach_> event that is important
<naobsd> what I said is, it just work, document exists.
<naobsd> some people,
<hramrach_> ok, I did not try that so I would not know
<naobsd> who couldn't do something,
<naobsd> he think "I must not be wrong, there must be something/someone in secret"
<naobsd> they don't think "I have to learn more myself"
<naobsd> and some people called "developer" do such a thing
<naobsd> when they meet something not work well, they don't think "we're wrong". they think "it's impossible by nature"
<naobsd> and if they found someone who could do (something), they think/say "he must have secret thing, he is not open"
<hramrach_> yes, sometimes clueless people give rise to such rumour. or the instructions are slightly flawed in a way obvious to some but followed to the letter do not work
<hramrach_> then you can only blame the community size. if there were more people doing android work sure there would be somebody smart enough to build a rom
<naobsd> in rockchip users' community on the internet, it's not rare, it's popular :(
<hramrach_> s/in rockchip users' community//
<naobsd> "smart enough to build a rom" = unpack, exchange files and add random lines to build.prop, then repack
<naobsd> it's religious
<naobsd> not technical/logical :(
<hramrach_> that's many steps that can go subtly wrong and without knowing what to look for you are lost if it does not work on first try
<naobsd> different topic,
<naobsd> I sometimes asked "how did you find it?"
<naobsd> "I tried, before asking answer"
<naobsd> many people just ask answer, and just believe without confirmation
<hramrach_> yes, I sometimes wondered how people could find such things. but if many try, fail and try to think of the root cause eventually they are right. It helps much if they can think analytically and only try to explain the cause in logical ways
<naobsd> sorry, I should take a rest
<hramrach_> thanks for making the tools and weeding out the spam from the wiki
<hramrach_> and enjoy your rest
<hramrach_> was just browsing a page reselling odd Japanese products, including stress-relief ones. Sure the Japanese industry is inventive :D
mrcan has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 272 seconds]
cristian_c has joined #linux-rockchip
<cristian_c> Hi
<hramrach_> hello
<cristian_c> I've tried to unpack recovery.img
<cristian_c> extracted from RK30GENERIC_CWM.zip
<cristian_c> but I always get error
<cristian_c> Any ideas?
<hramrach_> what error where when?
<cristian_c> usually I get
<cristian_c> android magic not found
<cristian_c> either File recovery.img not a plain boot image, seeking for embedded image... not found
<cristian_c> hramrach_, with unpackbootimg, rkunpack and others
<hramrach_> the recovery.img is supposedly something that is flashed as recovery image, not a standard Android image. You can probably follow any random guide you find on the net on how to flash a recovery image. I have no idea how it's done or if rk tablets are in some ways pecific
<hramrach_> +s
<cristian_c> hramrach_, ehm, I should unpack this .img file
<cristian_c> hramrach_, it's the generic rockchip img
RayFlower has quit [Read error: Connection reset by peer]
<cristian_c> hramrach_, what do you refer to, exactly?
<hramrach_> in those steps the recovery.img is not unpacked
<hramrach_> but some extra file is installed before installing recovery_img
<cristian_c> ok
<hramrach_> I have no idea if that works. never tried it
<cristian_c> hramrach_, what package do you refer to, exactly?
<hramrach_> apparently there the .zip is part of some Android app that installs it
<cristian_c> hramrach_, ah, I tried
<cristian_c> arctools doesn't work
<naobsd> sigh
<cristian_c> it has many bugs
<mrcan> hi i installed linaro based ubuntu image, it comes with 1920x1080px resolution. tried to change resolution in sys/class, no result, also have 1 mode. tried to add mode, no result. someone said me resolution changed in kernel src. i tried to find where is located, no result again :) can someone help me about where is located its resolution data in kernel src
<naobsd> cristian_c: run rkunpack recovery.img
<cristian_c> naobsd, I try again
<naobsd> cristian_c: then you'll get cpio+gz file
<cristian_c> ok
<cristian_c> I remember I tried rkunpack but I'll try again and I'll paste the results
<cristian_c> :)
RayFlower has joined #linux-rockchip
<hramrach_> cristian_c: where do you get the RK30GENERIC_CWM.zip?
<naobsd> it never says "android magic not found"
<cristian_c> hramrach_, from androtab.info
<naobsd> if you're talking about framebuffer size, not about HDMI mode.
<mrcan> in hdmi mode
<mrcan> 01:57 <hipboi_> mrcan, you need to compile the kernel to change the resolution
<mrcan> said me this, but didnt find where is located resolution data
<hramrach_> mrcan: did you try fbset?
ganbold_ has joined #linux-rockchip
<mrcan> no i didnt, i will try it
<hramrach_> cristian_c: did you try the update.zip installation?
<cristian_c> hramrach_, yes
<hramrach_> and adb installation?
<cristian_c> hramrach_, recovery installation from adb?
<cristian_c> naobsd, 'unpacked'
<cristian_c> :O
<naobsd> hramrach_: cristian_c asked about how to unpack, not install
<cristian_c> naobsd, downloading rkunpack by https://github.com/naobsd/rkutils, it has worked
<hramrach_> where did you get rkunpack before?
<naobsd> hramrach_: do you restore radxa pages? (of course I can do it if it's ok now)
<cristian_c> I think previously I had tried rkunpack from rkflashtool package and from other sites (about rockchip, anyway)
<hramrach_> naobsd: good point about unpack vs install
<hramrach_> naobsd: I think that radxa rock is a rk device and should have at least a device page on the wiki
<hramrach_> other than the android build page the rest is useless
<naobsd> ah
<cristian_c> recovery.img-raw :O
<cristian_c> good, it's a gzip archive
<naobsd> that rkunpack is probably forked from my very old rkunpack...?
<naobsd> hramrach_: what I asked is it's ok to rename it now, anyway I'll do it now
<hramrach_> naobsd: I moved it back, didn't I?
<cristian_c> hramrach_, no, I didn't try to install cwm recovery by 'from root shell' with adb
<hramrach_> well, if you wanted to install it there is step by step guide how to do it that way
<cristian_c> rkflashtool works too :)
<naobsd> ah, it seems rkunsign is the tool to "unpack" individual image...
<naobsd> hramrach_: ah, sorry, it seems they are empty
<naobsd> hramrach_: http://linux-rockchip.info/mw/index.php?title=OBSOLETE/Radxa_rock/Android_Build this is not yet
<hramrach_> naobsd: yes, that's probably replicated somewhere on radxa pages
<hramrach_> do we have any other android build guide?
<hramrach_> naobsd: also did you save the community section of your new main page before moving the old one back?
<naobsd> I thought all radxa pages were old and not good to keep them
FreezingCold has quit [Ping timeout: 260 seconds]
<hramrach_> naobsd: yes, they are old. do you have any newer guide for building android?
<naobsd> hramrach_: no, links to other resources are available in old(restored) main
<hramrach_> I see, it's at the bottom on the old page
<naobsd> hramrach_: I don't have any other guide for now
<hramrach_> so it has some value, presumably
<naobsd> hramrach_: I said OBSOLETE-ed was useless
<naobsd> http://linux-rockchip.info/mw/index.php?title=OBSOLETE/Radxa_rock/Android_Build#Get_the_source_code <- this is not right
<naobsd> we'll get questions that "I follow wiki, but it doesn't work, please help!"
<naobsd> I'm not sure it's really better than "I cannot find guide, please help!"
<naobsd> I think "better than nothing", but sometimes I think "nothing is better than worse"
<hramrach_> if it's not right then it's useless
<naobsd> I don't want to repeat
<naobsd> I already restored all OBSOLETE-ed pages
<naobsd> (except android build page)
<naobsd> I still think (at least some of) them are useless
<naobsd> but I don't want to repeat, at least now
cyrozap has quit [Ping timeout: 244 seconds]
cyrozap has joined #linux-rockchip
<cristian_c> ok, I've typed: gunzip -c ../recovery.img-raw | cpio -i
<cristian_c> and may files appeared in the new folder
<cristian_c> *many
FreezingCold has joined #linux-rockchip
<naobsd> btw 2 "rkunpack" makes confusion :(
<naobsd> my ver. has no doc, not prior
<naobsd> btw
<naobsd> when I wrote rkcrc etc
<naobsd> many people think .c is useless, .exe is important ;)
VargaD_ has joined #linux-rockchip
<naobsd> and later, some people made/copied .exe a lot
<naobsd> then, I saw things like "it's exe, useless, we love open source"
VargaD has quit [Ping timeout: 260 seconds]
VargaD_ is now known as VargaD
<naobsd> probably I was wrong, I didn't promote so much ;)
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<cristian_c> ok
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<hramrach_> naobsd: main page shortening done. now it fits on 1 page in my browser (except for the other links section)
<naobsd> hramrach_: thank you
<hramrach_> feel free to delete these pages: http://linux-rockchip.info/mw/index.php?title=Category:Obsolete
<karlp> hrmm, one tick
<karlp> hold that thought
<karlp> han gon, how does this page work? http://linux-rockchip.info/mw/index.php?title=Category:Rk3066_Hardware
<hramrach_> it does not anymore.
<karlp> ahh, nvmd, was getting confused with http://linux-rockchip.info/mw/index.php?title=Category:Rk3066_Devices
<hramrach_> yes, I renamed it
<karlp> wow, that front page is prtty gross now :)
<hramrach_> because people started tagging random stuff with hardware
<hramrach_> if you can thing of improvement go ahead and edit it ;-)
<karlp> I will, just at work at the moment
<karlp> did you mean to make it three wide columns for hardware/software/howtos?
<hramrach_> something like that. The lines are short so placing them next to each other makes the page more compact
<hramrach_> I guess you need cellpadding but don't know how to do that with current css or wikimedia styles from the top of my head
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
<hramrach_> hmm, removing borders seems better but for some reason the middle column is now lower than the ones on sides
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<hramrach_> karlp: http://linux-rockchip.info/mw/index.php?title=Category:Rk3066_Devices is filled with http://linux-rockchip.info/mw/index.php?title=Template:Infobox_Board which is basically black magic
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<hramrach_> so if you do not include an infobox your device does not pop up in that category
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 260 seconds]
benja` is now known as benja
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
FreezingCold has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cyrozap has quit [Ping timeout: 260 seconds]
cyrozap has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
amstan_ is now known as amstan
RayFlower has joined #linux-rockchip
cyrozap has quit [Ping timeout: 272 seconds]
amstan has quit [Quit: ZNC - http://znc.in]
amstan has joined #linux-rockchip
cyrozap has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
bengal has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Client Quit]
bengal has quit [Ping timeout: 272 seconds]
bengal has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
akaizen_ has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
bengal has quit [Quit: Leaving]
cyrozap has quit [Ping timeout: 260 seconds]
cyrozap has joined #linux-rockchip
cyrozap has quit [Ping timeout: 246 seconds]
cyrozap has joined #linux-rockchip
<karlp> hrm, trying to probe vcc rmii is proving tedious. seems to connect to many places on the tsp659102
benja is now known as benja`
<karlp> nope, got it :)
<karlp> it's on what the marsboard calls VCC_IO, pins 6,12,14,16, and 23, not vcc_rmii like the marsboard uses
cristian_c has quit [Quit: Sto andando via]