Tido

I am on the road. So just out of my mind, wouldn't it make more sense with a shunt. Measure it with A20 or Arduino?

Wow, bascially no mistakes in the spec sheet - I was impressed. Did SinoVoip finally care about becoming better ? Well, I thought I wait for TK's first comment before I comment

What about temperature,if only one core is benchmarked? Does the Temperature read out differ if core 1, 2, 3 or 4 is benchmarked.

It works on my mobile phone with this navbar, but it does hover with a distance from the top (Firefox mobile).

Will you add this to: Process_Contribute.md ?

I agree with you, that there are to many 'little' topics in the first order. This was my suggestion - the order is not defined, just the Main-Topics (8) Introduction, FAQ, Board specific, SoC specific, Basic, Advanced, Developer, Text for image.zip If these are the basis for permalinks this would be good enough for me - so that the document can grow how the future wants it. Why shall an FAQ be frozen, shouldn't it reflect the state of the latest version - to keep it easy ?

So you have a device, that comes with zero (0) storage /memory option and you ask "how to reset". This is funny, right ?

a comment of TK on another thread: We simply (still) fail to point our users to the relevant portions of documentation. Why is this necessary? Doesn't a TOC and good structure do the job? We are not RPi with 8years olds in the forum.

will save u time to read 10 min http://docs.armbian.com/user-manual/

it is recommended to start with SSH (Putty, on Windows) to configure the System. Then switch to HDMI ;-)

I went to "allwinner H3" section and I found two threads about camera, on the first page: http://forum.armbian.com/index.php/topic/957-orange-pi-c%C3%A2mera-gc2035-works-fine-with-v4l2-applications/ http://forum.armbian.com/index.php/topic/1213-ov5640-camera-with-orange-pi/

Here I have currently wildly collected most of the information and put in 4 topics suggestion. Everybody who has the link can edit the document, if you are logged in on Gmail you can see who did what.

Is this different to Igor's approach in this posting? I think one document is not enough. You have to have documents per 'task', i.e. I like Wildcat_P suggestion. Furthermore, Igor mentioned this also already, I gave some ideas to it. What we are currently suffering is a document to collect the ideas we already agreed on. Now all this information is spread over these 2 pages of this thread. I could start to collect this in a Google-Doc and I can give you edit access. I think this would be much more effective - in the office I cannot access Google-Docs so I could start tonight.

Editing only the Wiki, I suppose ? if changes can be reversed, like with any other Wiki, then the risk is not that big to open it to everyone ? Well at least like on sunxi or others you need a login on GitHub to edit the Wiki, right?

Edit my previous posting: Change some Text to bold, so that TK also recognizes it (more structure, logical order) -> as I said to you in the past, think about what I want express and not what you are thinking. in Post no. 30 I wrote: By the way, in the manual should be a small section "how to commit suggestion" or "help to improve this manual" and a couple words and links. I guess this fits to your second paragraph. So where you are, I was already 3 posts ago And as I am not the owner of this GitHub, nor has a dedicated GitHub been created - this belongs to the owner of the GitHub to discuss. I already know that you wont stop

First to your last line: A "link" dear Thomas, is a connection, a bridge, a guiding light through your darkest night - it doesn't make sense to maintain text on two places and no - I didn't study how Igor this combined - I simply asked. I read it, every time - because it will save me time if some changes have been done that influence my way of working. I do agree with you, that we need more structure in the documentation. Performance tweaks /tmp & /log = RAM, ramlog app saves logs to disk daily and on shut-down (Wheezy and Jessie w/o systemd) automatic IO scheduler. (check /etc/init.d/armhwinfo) journal data writeback enabled. (/etc/fstab) commit=600 to flush data to the disk every 10 minutes (/etc/fstab) optimized CPU frequency scaling 480-1010Mhz (392-996Mhz @Freescale, 600-2000Mhz @Exynos & S905) with interactive governor (/etc/init.d/cpufrequtils) eth0 interrupts are using dedicated core (Allwinner based boards) To me they are not in a logical order i.e. my order (First Memory, than CPU): /tmp & /log = RAM, ramlog app saves logs to disk daily and on shut-down (Wheezy and Jessie w/o systemd) journal data writeback enabled. (/etc/fstab) commit=600 to flush data to the disk every 10 minutes (/etc/fstab) automatic IO scheduler. (check /etc/init.d/armhwinfo) optimized CPU frequency scaling 480-1010Mhz (392-996Mhz @Freescale, 600-2000Mhz @Exynos & S905) with interactive governor (/etc/init.d/cpufrequtils) eth0 interrupts are using dedicated core (Allwinner based boards) Another idea coming from your inspiration above, if you hit the download link, it will take you down to the respective section i.e. Vanilla Kernel and the real download button is at the end of its section One more In the FAQ: dd bs=1M if=filename.raw of=/dev/sdx I would add at the end: && sync dd bs=1M if=filename.raw of=/dev/sdx && sync So after command 1 (dd finished and only then), it will run a sync and flush all the RAM to the disc's. Edit: Change some Text to bold, so that TK also recognizes it (more structure, logical order)

Awesome Igor - I like it. But I guess it is not linked yet to: http://www.armbian.com/documentation/ ? By the way, in the manual should be a small section "how to commit suggestion" or "help to improve this manual" and a couple words and links. This sounds to me like a standard FAQ section ? -> that could link to sections in the manual or just have some answers

If documentation is a GitHub Repo, then everybody can send a pull request /or leave a comment. Wouldn't this improve the documentation ? This would offer the possibility of a nice structured HTML manual I wrote this already above: To create one: Go to the repository, there is a settings link (in the same line as it says <>code), within those settings you can click it: GitHub Wikis is a simple way to let others contribute content. Any GitHub user can create and edit pages to use for documentation, examples, support, or anything you wish. So it looks to me it is a Wiki per Repository. This can be linked out of the HTML manual if requested. I am sorry, I don't understant the idea /intention - maybe it's just me

I can take a look at it. @tk, guide the user to the manual /wiki before answer it in the forum. Kind if easy, but u must be follow such a 'rule' Edit Tido: Kind of easy, but u must follow such a 'rule' @WP, thanks for edit - bloody cell phone :-)

Exactly, it should work out of box. 235KB for 36 pages is a good result, one font style (DejaVu) even with some SDcard pictures. The long "Release history" should be at the end and I miss a "table of contents" like you can see in this Wiki or like mentioned above at C.H.I.P.

@telindus To which Connector did you attach the LCD to the SBC? Did you read in the A20 manual how to address this /your output first?

Do I understand you correct that: Your LCD capacitive touchscreen works - you can control the device (A20 SBC) from the screen? What you would like to have on the LCD is a Logo /Animation while booting and again on shutdown of the SBC?

Ahh exactly, I knew it was an M :-) And Markdown can export to PDF, now I don't know about the possibilities of the GitHub Wiki. To create one: Go to the repository, there is a settings link (in the same line as it says <>code), within those settings you can click it: GitHub Wikis is a simple way to let others contribute content. Any GitHub user can create and edit pages to use for documentation, examples, support, or anything you wish. So it looks to me it is a Wiki per Repository.

Is this maybe (fswebcam update for OPI (H3 only) in relation to your question ?

I like it the way C.H.I.P does it http://docs.getchip.com/chip.html I cannot remember which markup language they are using ... something with M ? Ah, and it should be possible to export article or pages to PDF. Licence like: Creative Commons