| /kernel/linux/linux-5.10/arch/arm/mach-orion5x/ |
| 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 …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-orion5x/ |
| D | Kconfig | 27 Say 'Y' here if you want your kernel to support the
34 Say 'Y' here if you want your kernel to support the
41 Say 'Y' here if you want your kernel to support the
49 Say 'Y' here if you want your kernel to support the Marvell
56 Say 'Y' here if you want your kernel to support the
63 Say 'Y' here if you want your kernel to support the
69 Say 'Y' here if you want your kernel to support the
75 Say 'Y' here if you want your kernel to support the
82 Say 'Y' here if you want your kernel to support the
90 Say 'Y' here if you want your kernel to support the
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-ep93xx/ |
| D | Kconfig | 21 Say 'Y' here if you want your kernel to support the ADS
28 Say 'Y' here if you want your kernel to support the
38 Say 'Y' here if you want your kernel to support the Cirrus
45 Say 'Y' here if you want your kernel to support the Cirrus
52 Say 'Y' here if you want your kernel to support the Cirrus
59 Say 'Y' here if you want your kernel to support the Cirrus
66 Say 'Y' here if you want your kernel to support the Cirrus
73 Say 'Y' here if you want your kernel to support the Cirrus
80 Say 'Y' here if you want your kernel to support the Cirrus
87 Say 'Y' here if you want your kernel to support the Cirrus
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-ep93xx/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| 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 …]
|
| 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 …]
|
| 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.
22 control system; if you use ``git`` to prepare your patches, you'll find much
25 your life as a kernel developer easier.
48 If you must generate your patches by hand, use ``diff -up`` or ``diff -uprN``
53 generated by :manpage:`diff(1)`. When creating your patch, make sure to
68 vi $MYFILE # make your change
73 or unmodified kernel source tree, and generate a ``diff`` against your
87 Make sure your patch does not include any extra files which do not
88 belong in a patch submission. Make sure to review your patch -after-
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | submitting-patches | 1 How to Get Your Patch Accepted Into the Hwmon Subsystem
6 increase the chances of your change being accepted.
18 * Please run your patch through 'checkpatch --strict'. There should be no
22 * If your patch generates checkpatch errors, warnings, or check messages,
28 * Please test your patch thoroughly. We are not your test group.
34 * If your patch (or the driver) is affected by configuration options such as
47 your patch into a cleanup part and the actual addition. This makes it easier
48 to review your changes, and to bisect any resulting problems.
56 * Running your patch or driver file(s) through checkpatch does not mean its
57 formatting is clean. If unsure about formatting in your new driver, run it
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-ixp4xx/ |
| 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 …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 12 Say 'Y' here if you want your kernel to support Linksys's
20 Say 'Y' here if you want your kernel to support the Gateworks
28 Say 'Y' here if you want your kernel to support the Giant
36 Say 'Y' here if you want your kernel to support the ADI
44 Say 'Y' here if you want your kernel to support Gateway's
52 Say 'Y' here if you want your kernel to support Netgear's
59 Say 'Y' here if you want your kernel to support Intel's
66 Say 'Y' here if you want your kernel to support Intel's
73 Say 'Y' here if you want your kernel to support Intel's
80 Say 'Y' here if you want your kernel to support GORAMO
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-ks8695/ |
| D | Kconfig | 9 Say 'Y' here if you want your kernel to run on the original
15 Say 'Y' here if you want your kernel to run on the D-Link
21 say 'Y' here if you want your kernel to run on the Brivo
27 Say 'Y' here if you want your kernel to support the
34 Say 'Y' here if you want your kernel to support the
41 Say 'Y' here if you want your kernel to support the
49 Say 'Y' here if you want your kernel to support the OpenGear
57 Say 'Y' here if you want your kernel to support the OpenGear
65 Say 'Y' here if you want your kernel to support the OpenGear
73 Say 'Y' here if you want your kernel to support the OpenGear
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 45 conversion or worse, fiddle the raw __u64 through your code since that
59 * Have a clear way for userspace to figure out whether your new ioctl or ioctl
72 and reject the ioctl if that's not the case. Otherwise your nice plan for
98 * Have simple testcases for every input validation failure case in your ioctl.
99 Check that the error code matches your expectations. And finally make sure
105 * Make all your ioctls restartable. First X really loves signals and second
107 interrupting your main test suite constantly with signals. Thanks to X's
108 love for signal you'll get an excellent base coverage of all your error
116 killable. GPUs just die and your users won't like you more if you hang their
121 * Have testcases for the really tricky corner cases in your error recovery code
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| 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 …]
|
| /kernel/linux/linux-4.19/drivers/block/paride/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 14 Now your system is properly set up, your disk is encrypted except for
17 an initrd that does your current crypto setup already.
19 At this point you want to encrypt your swap, too. Still you want to
30 within your running system. The easiest way to achieve this is
36 Now set up your kernel to use /dev/mapper/swap0 as the default
37 resume partition, so your kernel .config contains:
41 Prepare your boot loader to use the initrd you will create or
50 Finally you need to create or modify your initrd. Lets assume
55 named "swapkey". /etc/fstab of your initrd contains something
63 of your crypto devices, again by reading the setup from the
[all …]
|
| /kernel/linux/linux-4.19/drivers/staging/speakup/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 16 Now your system is properly set up, your disk is encrypted except for
19 an initrd that does your current crypto setup already.
21 At this point you want to encrypt your swap, too. Still you want to
32 within your running system. The easiest way to achieve this is
38 Now set up your kernel to use /dev/mapper/swap0 as the default
39 resume partition, so your kernel .config contains::
43 Prepare your boot loader to use the initrd you will create or
52 Finally you need to create or modify your initrd. Lets assume
57 named "swapkey". /etc/fstab of your initrd contains something
65 of your crypto devices, again by reading the setup from the
[all …]
|