| /Linux-v5.4/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 …]
|
| /Linux-v5.4/arch/arm/mach-orion5x/ |
| D | Kconfig | 28 Say 'Y' here if you want your kernel to support the
35 Say 'Y' here if you want your kernel to support the
42 Say 'Y' here if you want your kernel to support the
50 Say 'Y' here if you want your kernel to support the Marvell
57 Say 'Y' here if you want your kernel to support the
64 Say 'Y' here if you want your kernel to support the
70 Say 'Y' here if you want your kernel to support the
76 Say 'Y' here if you want your kernel to support the
83 Say 'Y' here if you want your kernel to support the
91 Say 'Y' here if you want your kernel to support the
[all …]
|
| /Linux-v5.4/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 …]
|
| D | howto.rst | 21 have been told by your manager, "Go write a Linux driver for this
55 documented; do not expect people to adapt to you or your company's way
215 will learn the basics of getting your patch into the Linux kernel tree,
360 One of the best ways to put into practice your hacking skills is by fixing
363 your skills, and other developers will be aware of your presence. Fixing
405 If multiple people respond to your mail, the CC: list of recipients may
411 Remember to keep the context and the attribution of your replies intact,
412 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
413 add your statements between the individual quoted sections instead of
416 If you add patches to your mail, make sure they are plain readable text
[all …]
|
| D | stable-api-nonsense.rst | 6 (all of your questions answered and then some)
30 you get that only if your driver is in the main kernel tree. You also
31 get lots of other good benefits if your driver is in the main kernel
84 Now a number of these issues can be addressed by simply compiling your
95 multiple versions of your module.
172 Simple, get your kernel driver into the main kernel tree (remember we are
173 talking about drivers released under a GPL-compatible license here, if your
174 code doesn't fall under this category, good luck, you are on your own here,
175 you leech). If your driver is in the tree, and a kernel interface changes,
177 place. This ensures that your driver is always buildable, and works over
[all …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 26 Say 'Y' here if you want your kernel to support Linksys's
34 Say 'Y' here if you want your kernel to support the Gateworks
42 Say 'Y' here if you want your kernel to support the Giant
50 Say 'Y' here if you want your kernel to support the ADI
58 Say 'Y' here if you want your kernel to support Gateway's
66 Say 'Y' here if you want your kernel to support Netgear'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 Intel's
87 Say 'Y' here if you want your kernel to support Intel's
94 Say 'Y' here if you want your kernel to support GORAMO
[all …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/ioctl/ |
| 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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 113 3. Once your application has started, prevent CPU-hotplug operations
116 bring it back online before you start your application.)
125 3. Once your application has started, prevent CPU-hotplug operations
128 bring it back online before you start your application.)
137 3. Once your application has started, prevent CPU-hotplug operations
140 bring it back online before you start your application.)
230 1. Run your workload at a real-time priority, which will allow
243 3. Do any of the following needed to avoid jitter that your
246 a. Build your kernel with CONFIG_SLUB=y rather than
252 c. Limit your CPU frequency so that a CPU-frequency
[all …]
|
| D | reporting-bugs.rst | 18 contact your Linux distribution or embedded vendor for support.
31 Identifying which part of the Linux kernel might be causing your issue
32 increases your chances of getting your bug fixed. Simply posting to the
33 generic linux-kernel mailing list (LKML) may cause your bug report to be
38 maintainer doesn't answer, then expand your scope to mailing lists like
50 To find out where to send an emailed bug report, find your subsystem or
52 entries, and send your bug report to the person(s) listed in the "M:"
96 a netconsole trace, or type the message from your screen into the bug
97 report. Please read "Documentation/admin-guide/bug-hunting.rst" before posting your
105 relevant to your bug, feel free to exclude it.
[all …]
|
| /Linux-v5.4/Documentation/s390/ |
| D | 3270.rst | 22 VM-ESA operating system, define a 3270 to your virtual machine by using
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
32 another 3270 emulator, started from an xterm window on your PC or
34 and this Linux-390 3270 driver, you have another way of talking to your
50 you should rerun the configuration script every time your set of 3270s,
63 3270 console support, then the driver automatically converts your console
97 login prompts appear on your 3270s as soon as boot is complete (or
98 with emulated 3270s, as soon as you dial into your vm guest using the
104 3. Define graphic devices to your vm guest machine, if you
115 you have chosen 3270 console support, your console now behaves
[all …]
|
| /Linux-v5.4/Documentation/scsi/ |
| D | libsas.txt | 32 After initializing your hardware, from the probe() function
33 you call sas_register_ha(). It will register your LLDD with
35 register your SAS driver with the sysfs SAS tree it creates.
36 It will then return. Then you enable your phys to actually
37 start OOB (at which point your driver will start calling the
43 Normally this is statically embedded to your driver's
50 And then all the phys are an array of my_phy in your HA
53 Then as you go along and initialize your phys you also
54 initialize the sas_phy struct, along with your own
73 address of the phy, possibly somewhere in your my_phy
[all …]
|
| /Linux-v5.4/fs/reiserfs/ |
| D | README | 11 other licenses. If you add your code to governed files, and don't
12 want it to be owned by Hans Reiser, put your copyright label on that
15 Reiser, and by adding your code to it, widely distributing it to
19 to license code labeled as owned by you on your behalf other than
25 right to decline to allow him to license your code contribution other
52 mkreiserfs and other utilities are in reiserfs/utils, or wherever your
63 Yes, if you update your reiserfs kernel module you do have to
64 recompile your kernel, most of the time. The errors you get will be
65 quite cryptic if your forget to do so.
70 Hideous Commercial Pitch: Spread your development costs across other OS
[all …]
|
| /Linux-v5.4/arch/arm/mach-mvebu/ |
| D | Kconfig | 37 Say 'Y' here if you want your kernel to support boards based
54 Say 'Y' here if you want your kernel to support boards based
73 Say 'Y' here if you want your kernel to support boards based
89 Say 'Y' here if you want your kernel to support boards based
101 Say 'Y' here if you want your kernel to support boards based
116 Say 'Y' here if you want your kernel to support the
132 Say 'Y' here if you want your kernel to support boards based
|
| /Linux-v5.4/drivers/input/mouse/ |
| D | Kconfig | 24 Say Y here if you have a PS/2 mouse connected to your system. This
48 your system.
58 your system.
68 your system.
78 your system.
100 your system.
110 TouchScreen connected to your system.
120 to your system.
129 to your system.
163 connected to your system.
[all …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/ |
| D | sb1000.txt | 4 It's a one-way downstream-only cable modem, meaning that your upstream net link
5 is provided by your regular phone modem.
20 2.) Several PPP scripts which live in /etc/ppp to make connecting via your
35 3.) The standard isapnp tools. These are necessary to configure your SB1000
38 If you don't have these installed as a standard part of your Linux
43 or check your Linux distribution binary CD or their web site. For help with
53 you prefer, in the top kernel tree directory to set up your kernel
60 by isapnp to access your PnP cards. This is the value of READPORT in
65 4.) Boot your new kernel following the usual procedures.
69 IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
[all …]
|
| /Linux-v5.4/drivers/input/touchscreen/ |
| D | Kconfig | 38 and your board-specific setup code includes that in its
42 on your board, you will also get hwmon interfaces for the voltage
55 AD7877 controller, and your board-specific initialization
114 controller chip in your system.
127 such as AT42QT602240/ATMXT224, connected to your system.
161 your system.
173 connected to your system.
222 to your system. You will also need to select appropriate
308 your system.
320 your system.
[all …]
|
| /Linux-v5.4/arch/openrisc/ |
| D | Kconfig | 84 Select this if your implementation features write through data caches.
101 Select this if your implementation has the Class II instruction l.ff1
107 Select this if your implementation has the Class II instruction l.fl1
113 Select this if your implementation has a hardware multiply instruction
119 Select this if your implementation has a hardware divide instruction
149 Say N here if you know that your OpenRISC processor has
156 Say Y here if your OpenRISC processor features shadowed
179 your kernel crashes this doesn't have any influence.
|
| /Linux-v5.4/arch/mips/include/asm/ |
| D | war.h | 82 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
112 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
128 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
142 #error Check setting of BCM1250_M3_WAR for your platform
149 #error Check setting of SIBYTE_1956_WAR for your platform
165 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
184 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
195 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
205 #error Check setting of ICACHE_REFILLS_WORKAROUND_WAR for your platform
213 #error Check setting of R10000_LLSC_WAR for your platform
[all …]
|
