This is an old revision of the document!
I2C about I2C
Gallery example gallery
gallery and upload with some pictures have bug, im try fix it …
FIXED please check for any files must works
[[ys>vim4]]
- youtube search vim4
Khadas github links example
[[kg>utils]]
Flash tool for Ubuntu is on Khadas GitHub utils.
test2 **NO BOLD** - no wiki markup inside
test
ls -l1 sd
- inline code ls -l1 sd **no bold**
- inline safe codeacronyms test SPDIF GPIO LED PWM 1W 1w IRQ pin CPU SBC 2 3
😐
😉
header links example: Header 2
sniplet source code example …sniplet source code example …sniplet source code example …sniplet source code example …sniplet source code example … DELETEME
conf/lang/en/lang.php
<?php /** * Customization of the english language file * Copy only the strings that needs to be modified */ $lang['js']['nosmblinks'] = '';
same but in color
<?php echo "hello world!"; ?>
just colored syntax
<?php echo "hello world!"; ?>
Which system do you use? Android, Ubuntu, OOWOW or others? Formatting Syntax
Ubuntu https://ubuntu.com Which version of system do you use? Khadas official images, self built images, or others?
Self-built Please describe your issue below:
Will images built for VIM3 with fenix run on VIM4? If not, will the fenix repo on github be updated to support VIM4 boards? I’d like to build custom images based on Ubuntu 20.04 that run on this platform
DokuWiki supports a simple syntax to create tables.
Heading 1 | Heading 2 | Heading 33 | head 4 |
---|---|---|---|
asd | asd | ||
123 | 123 | asd | |
Row 1 Col 1 | Row 1 Col 2 | Row 1 Col 3 | |
Row 2 Col 1 | asd asda | asd | |
asd | asd | asd | |
Row 3 Col 1 | asd | Row 3 Col 3 |
— artem 2022/06/13 20:58
monospace area
# SPDX-License-Identifier: GPL-2.0 VERSION = 5 PATCHLEVEL = 4 SUBLEVEL = 125 EXTRAVERSION = NAME = Kleptomaniac Octopus # *DOCUMENTATION* # To see a list of typical targets execute "make help" # More info can be located in ./README # Comments in this file are targeted only to the developer, do not # expect to learn how to build the kernel reading this file. # That's our default target when none is given on the command line PHONY := _all _all: # We are using a recursive build, so we need to do a little thinking # to get the ordering right. # # Most importantly: sub-Makefiles should only ever modify files in # their own directory. If in some directory we have a dependency on # a file in another dir (which doesn't happen often, but it's often # unavoidable when linking the built-in.a targets which finally # turn into vmlinux), we will call a sub make in that other dir, and # after that we are sure that everything which is in that other dir # is now up to date. # # The only cases where we need to modify files which have global # effects are thus separated out and done before the recursive # descending is started. They are now explicitly listed as the # prepare rule. ifneq ($(sub_make_done),1) # Do not use make's built-in rules and variables # (this increases performance and avoids hard-to-debug behaviour) MAKEFLAGS += -rR # Avoid funny character set dependencies unexport LC_ALL LC_COLLATE=C LC_NUMERIC=C export LC_COLLATE LC_NUMERIC # Avoid interference with shell env settings unexport GREP_OPTIONS # Beautify output # --------------------------------------------------------------------------- # # Normally, we echo the whole command before executing it. By making # that echo $($(quiet)$(cmd)), we now have the possibility to set # $(quiet) to choose other forms of output instead, e.g. # # quiet_cmd_cc_o_c = Compiling $(RELDIR)/$@ # cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $< # # If $(quiet) is empty, the whole command will be printed. # If it is set to "quiet_", only the short version will be printed. # If it is set to "silent_", nothing will be printed at all, since # the variable $(silent_cmd_cc_o_c) doesn't exist.