| /OK3568_Linux_fs/yocto/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 14 now, as you are starting your own project, it isn't exactly straightforward what
19 that will be part of your project**.
21 things, and adding them to your configuration. (See #3)
23 #. **Set up your board support**.
26 architecture as your custom hardware. Knowing the board already has a
30 #. **Find and acquire the best BSP for your target**.
33 layer index <>` to find and acquire the best BSP for your
35 best place to get your first BSP is from your silicon manufacturer or board
43 (which is reference embedded distribution) and then add your newly chosen
47 #. **Based on the layers you've chosen, make needed changes in your
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/input/sensors/accel/ |
| H A D | Kconfig | 18 To have support for your specific gsesnor you will have to
25 To have support for your specific gsesnor you will have to
32 To have support for your specific gsesnor you will have to
39 To have support for your specific gsesnor you will have to
45 To have support for your specific gsesnor you will have to
51 To have support for your specific gsesnor you will have to
58 To have support for your specific gsesnor you will have to
65 To have support for your specific gsesnor you will have to
71 To have support for your specific gsesnor you will have to
77 To have support for your specific gsesnor you will have to
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | maintainer-pgp-guide.rst | 66 Your distro should already have GnuPG installed by default, you just
92 You can put that in your ``.bashrc`` to make sure it's always the case.
111 edit your ``~/.gnupg/gpg-agent.conf`` file to set your own values::
120 beginning of your shell session. You may want to check your rc files
127 You will need to regularly refresh your keyring in order to get the
133 Check the full path to your ``gpg`` or ``gpg2`` command and use the
138 Protect your master PGP key
146 You should also make a new key if your current one is weaker than 2048 bits
169 lose your private subkey, it cannot be recreated from the master key
186 If you used the default parameters when generating your key, then that
[all …]
|
| H A D | 6.Followthrough.rst | 7 addition of your own engineering skills, have posted a perfect series of
17 kernel community to ensure that your code is up to the kernel's quality
19 prevent the inclusion of your patches into the mainline.
31 - If you have explained your patch well, reviewers will understand its
48 agendas at the expense of your own. Kernel developers often expect to
56 making. Do not let their form of expression or your own pride keep that
63 reviewers. If you believe that the reviewer has misunderstood your code,
65 suggested change, describe it and justify your solution to the problem. If
66 your explanations make sense, the reviewer will accept them. Should your
69 be easy to become blinded by your own solution to a problem to the point
[all …]
|
| H A D | submitting-patches.rst | 3 Submitting patches: the essential guide to getting your code into the kernel
9 can greatly increase the chances of your change being accepted.
18 This documentation assumes that you're using ``git`` to prepare your patches.
20 use it, it will make your life as a kernel developer and in general much
40 Describe your changes
43 Describe your problem. Whether your patch is a one-line bug fix or
55 from upstream, so include anything that could help route your change
64 different workloads. Describe the expected downsides of your
72 The maintainer will thank you if you write your patch description in a
76 Solve only one problem per patch. If your description starts to get
[all …]
|
| H A D | botching-up-ioctls.rst | 46 conversion or worse, fiddle the raw __u64 through your code since that
60 * Have a clear way for userspace to figure out whether your new ioctl or ioctl
73 and reject the ioctl if that's not the case. Otherwise your nice plan for
99 * Have simple testcases for every input validation failure case in your ioctl.
100 Check that the error code matches your expectations. And finally make sure
106 * Make all your ioctls restartable. First X really loves signals and second
108 interrupting your main test suite constantly with signals. Thanks to X's
109 love for signal you'll get an excellent base coverage of all your error
117 killable. GPUs just die and your users won't like you more if you hang their
122 * Have testcases for the really tricky corner cases in your error recovery code
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-orion5x/ |
| H A D | Kconfig | 26 Say 'Y' here if you want your kernel to support the
33 Say 'Y' here if you want your kernel to support the
40 Say 'Y' here if you want your kernel to support the
48 Say 'Y' here if you want your kernel to support the Marvell
55 Say 'Y' here if you want your kernel to support the
62 Say 'Y' here if you want your kernel to support the
68 Say 'Y' here if you want your kernel to support the
74 Say 'Y' here if you want your kernel to support the
81 Say 'Y' here if you want your kernel to support the
89 Say 'Y' here if you want your kernel to support the
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-ep93xx/ |
| H A D | Kconfig | 22 Say 'Y' here if you want your kernel to support the ADS
29 Say 'Y' here if you want your kernel to support the
39 Say 'Y' here if you want your kernel to support the Cirrus
46 Say 'Y' here if you want your kernel to support the Cirrus
53 Say 'Y' here if you want your kernel to support the Cirrus
60 Say 'Y' here if you want your kernel to support the Cirrus
67 Say 'Y' here if you want your kernel to support the Cirrus
74 Say 'Y' here if you want your kernel to support the Cirrus
81 Say 'Y' here if you want your kernel to support the Cirrus
88 Say 'Y' here if you want your kernel to support the Cirrus
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/ |
| H A D | auto-host.h | 123 /* Define if your target supports default PIE and it is enabled. */
129 /* Define if your target supports default stack protector and it is enabled.
312 /* Define if your assembler supports architecture modifiers. */
318 /* Define if your avr assembler supports -mgcc-isr option. */
324 /* Define if your avr assembler supports --mlink-relax option. */
330 /* Define if your avr assembler supports -mrmw option. */
336 /* Define to the level of your assembler's compressed debug section support.
343 /* Define if your assembler supports the --debug-prefix-map option. */
349 /* Define if your assembler supports .module. */
355 /* Define if your assembler supports DSPR1 mult. */
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/ |
| H A D | auto-host.h | 123 /* Define if your target supports default PIE and it is enabled. */
129 /* Define if your target supports default stack protector and it is enabled.
312 /* Define if your assembler supports architecture modifiers. */
318 /* Define if your avr assembler supports -mgcc-isr option. */
324 /* Define if your avr assembler supports --mlink-relax option. */
330 /* Define if your avr assembler supports -mrmw option. */
336 /* Define to the level of your assembler's compressed debug section support.
343 /* Define if your assembler supports the --debug-prefix-map option. */
349 /* Define if your assembler supports .module. */
355 /* Define if your assembler supports DSPR1 mult. */
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | submitting-patches.rst | 1 How to Get Your Patch Accepted Into the Hwmon Subsystem
6 increase the chances of your change being accepted.
19 * Please run your patch through 'checkpatch --strict'. There should be no
27 * If your patch generates checkpatch errors, warnings, or check messages,
33 * Please test your patch thoroughly. We are not your test group.
39 * If your patch (or the driver) is affected by configuration options such as
52 your patch into a cleanup part and the actual addition. This makes it easier
53 to review your changes, and to bisect any resulting problems.
61 * Running your patch or driver file(s) through checkpatch does not mean its
62 formatting is clean. If unsure about formatting in your new driver, run it
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/kernel-dev/ |
| H A D | common.rst | 8 with the Yocto Project Linux kernel. These tasks include preparing your
11 kernel, iterative development, working with your own sources, and
22 Before you can do any kernel development, you need to be sure your build
27 :term:`Source Directory` (``poky``) on your system. Follow the steps in the
29 section in the Yocto Project Development Tasks Manual to set up your
35 create your local branch by checking out a specific tag to get the
42 :ref:`devtool <sdk-manual/extensible:using \`\`devtool\`\` in your sdk workflow>`
69 2. *Prepare Your local.conf File:* By default, the
73 :term:`MACHINE` variable appropriately in your ``conf/local.conf`` file
97 Add your new layer with 'bitbake-layers add-layer ../../meta-mylayer'
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A D | uio-howto.rst | 62 If you use UIO for your card's driver, here's what you get:
66 - develop the main part of your driver in user space, with all the
69 - bugs in your driver won't crash the kernel.
71 - updates of your driver can take place without recompiling the kernel.
82 :c:func:`mmap()` to access registers or RAM locations of your card.
112 To handle interrupts properly, your custom kernel module can provide its
130 - ``name``: The name of your device. It is recommended to use the name
131 of your kernel module for this.
133 - ``version``: A version string defined by your driver. This allows the
134 user space part of your driver to deal with different versions of the
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-ixp4xx/ |
| H A D | Kconfig | 25 Say 'Y' here if you want your kernel to support Linksys's
33 Say 'Y' here if you want your kernel to support the Gateworks
41 Say 'Y' here if you want your kernel to support the Giant
49 Say 'Y' here if you want your kernel to support the ADI
57 Say 'Y' here if you want your kernel to support Gateway's
65 Say 'Y' here if you want your kernel to support Netgear's
72 Say 'Y' here if you want your kernel to support Intel's
79 Say 'Y' here if you want your kernel to support Intel's
86 Say 'Y' here if you want your kernel to support Intel's
93 Say 'Y' here if you want your kernel to support GORAMO
[all …]
|
| /OK3568_Linux_fs/buildroot/toolchain/toolchain-external/toolchain-external-custom/ |
| H A D | Config.in.options | 31 Set to the gcc version that is used by your external
97 Use this option if your GCC version is older than any of the
103 work at all. Use such old toolchains at your own risk.
107 comment "GCC older than 4.8 is not tested by Buildroot. Use at your own risk."
120 If unsure what version your toolchain is using, you can look
121 at the value of LINUX_VERSION_CODE in linux/version.h in your
127 If your toolchain uses headers newer than the latest version
387 comment "Kernel headers older than 3.13 is not tested by Buildroot. Use at your own risk."
398 Select this option if your external toolchain uses the
408 Select this option if your external toolchain uses the GNU C
[all …]
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | configure.txt | 30 code for your system. It consists of a compiler (in our case, +gcc+),
36 The system installed on your development station certainly already has
38 that runs on your system. If you're using a PC, your compilation
48 The compilation toolchain is provided by your distribution, and
53 As said above, the compilation toolchain that comes with your system
54 runs on and generates code for the processor in your host system. As
55 your embedded system has a different processor, you need a
57 your _host system_ but generates code for your _target system_ (and
58 target processor). For example, if your host system uses x86 and your
59 target system uses ARM, the regular compilation toolchain on your host
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/block/paride/ |
| H A D | Kconfig | 18 support into your kernel, you may answer Y here to build in the
21 must also have at least one parallel port protocol driver in your
34 support into your kernel, you may answer Y here to build in the
37 must also have at least one parallel port protocol driver in your
50 support into your kernel, you may answer Y here to build in the
54 your system. Among the devices supported by this driver are the
64 support into your kernel, you may answer Y here to build in the
68 your system. Among the devices supported by this driver is the
80 If you chose to build PARIDE support into your kernel, you may
86 your system.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/dev-manual/ |
| H A D | start.rst | 35 essential to completing subsequent steps, which are to get your
36 equipment together and set up your development environment's
75 4. *Use Git as Your Source Control Manager (SCM):* Keeping your
122 - Keep your cross-development toolchains updated. You can do this
140 - Keep the core system unchanged as much as possible and do your
223 - Maintain your Metadata in layers that make sense for your
264 This section provides procedures to set up a system to be used as your
266 development using the Yocto Project. Your build host can be a native
281 Once your build host is set up to use the Yocto Project, further steps
286 - *BSP Development:* See the ":ref:`bsp-guide/bsp:preparing your build host to work with bsp layer…
[all …]
|
| /OK3568_Linux_fs/buildroot/support/dependencies/ |
| H A D | dependencies.sh | 21 echo "You seem to have the current working directory in your"
37 echo "You seem to have the current working directory in your"
43 printf "Your PATH contains spaces, TABs, and/or newline (\\\n) characters.\n"
52 echo "is installed on your system. Please unset this variable"
63 echo "You must install '$prog' on your build machine" >&2
81 echo "You must install 'make' on your build machine";
87 echo "You must install 'make' on your build machine";
105 echo "You must install 'gcc' on your build machine";
113 echo "You must install 'gcc' on your build machine";
132 echo "You may have to install 'g++' on your build machine"
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/ |
| H A D | PolyForm-Small-Business-1.0.0 | 9 your licenses.
25 to distribute copies of the software. Your license
59 Use of the software for the benefit of your company is use for
60 a permitted purpose if your company has fewer than 100 total
71 your licenses to anyone else, or prevent the licensor from
78 contributes to infringement of any patent, your patent license
80 your company makes such a claim, your patent license ends
81 immediately for work on behalf of your company.
87 not covered by your licenses, your licenses can nonetheless
90 32 days of receiving notice. Otherwise, all your licenses
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Starting.html | 70 <a name="Starting-Your-Program"></a>
71 <h3 class="section">4.2 Starting Your Program</h3>
81 <dd><p>Use the <code>run</code> command to start your program under <small>GDB</small>.
90 <p>If you are running your program in an execution environment that
92 that process run your program. In some environments without processes,
93 <code>run</code> jumps to the start of your program. Other targets,
102 <p>then use <code>continue</code> to run your program. You may need <code>load</code>
107 information, which you must do <em>before</em> starting your program. (You
108 can change it after starting your program, but such changes only affect
109 your program the next time you start it.) This information may be
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Starting.html | 70 <a name="Starting-Your-Program"></a>
71 <h3 class="section">4.2 Starting Your Program</h3>
81 <dd><p>Use the <code>run</code> command to start your program under <small>GDB</small>.
90 <p>If you are running your program in an execution environment that
92 that process run your program. In some environments without processes,
93 <code>run</code> jumps to the start of your program. Other targets,
102 <p>then use <code>continue</code> to run your program. You may need <code>load</code>
107 information, which you must do <em>before</em> starting your program. (You
108 can change it after starting your program, but such changes only affect
109 your program the next time you start it.) This information may be
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | spkguide.txt | 29 capabilities, depending on how your system administrator has installed
42 If your system administrator has installed Speakup to work with your
44 is to boot your system, and Speakup should come up talking. This
45 assumes of course that your synthesizer is a supported hardware
46 synthesizer, and that it is either installed in or connected to your
50 kernel with no default synthesizer. It is even possible that your
53 your synthesizer is supported but not available, complain to the person
54 who compiled and installed your kernel. Or better yet, go to the web
55 site, and learn how to patch Speakup into your own kernel source, and
56 build and install your own kernel.
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/brief-yoctoprojectqs/ |
| H A D | index.rst | 47 Make sure your :term:`Build Host` meets the
57 information on preparing your build host, see the
69 If your build host does not meet any of these three listed version
78 You must install essential host packages on your build host. The
95 Once you complete the setup instructions for your machine, you need to
96 get a copy of the Poky repository on your build host. Use the following
156 to keep your local files in sync with the release branch:
167 Building Your Image
170 Use the following steps to build your image. The build process creates
175 - If you are working behind a firewall and your build host is not
[all …]
|
| /OK3568_Linux_fs/u-boot/tools/patman/ |
| H A D | README | 10 - Creates patch directly from your branch
20 It is configured almost entirely by tags it finds in your commits.
28 in one of your commits, the series will be sent there.
30 In Linux and U-Boot this will also call get_maintainer.pl on each of your
47 - Check out a branch, and run this script to create and send out your
56 file 'doc/git-mailrc' in your U-Boot directory to supply the email aliases
68 To add your own, create a file ~/.patman like this:
85 used. Failing that you can put it into your path or ~/bin/checkpatch.pl
88 by patman but are known to bounce you can add a [bounces] section to your
101 you can add a [settings] section to your .patman file. This can be used
[all …]
|