| /linux-2.6.39/drivers/hwmon/ |
| D | Kconfig | 10 Hardware monitoring devices let you monitor the hardware health
14 control the speed of the fans. If you want this support you
18 To find out which specific driver(s) you need, use the
35 Say Y here if you want the I2C chip drivers to produce a bunch of
36 debug messages to the system log. Select this if you are having
46 If you say yes here you get support for the sensor part of the first
61 If you say yes here you get support for the sensor part of the
75 If you say yes here you get support for the Analog Devices
85 If you say yes here you get support for the Analog Devices
95 If you say yes here you get support for the National Semiconductor
[all …]
|
| /linux-2.6.39/Documentation/ |
| D | ManagementStyle | 5 on who you ask) management style for the linux kernel. It's meant to
16 companies. If you sign purchase orders or you have any clue about the
17 budget of your group, you're almost certainly not a kernel manager.
18 These suggestions may or may not apply to you.
38 particular, if somebody tells you "choose (a) or (b), we really need you
39 to decide on this", you're in trouble as a manager. The people you
40 manage had better know the details better than you, so if they come to
41 you for a technical decision, you're screwed. You're clearly not
44 (Corollary:if the people you manage don't know the details better than
45 you, you're also screwed, although for a totally different reason.
[all …]
|
| D | BUG-HUNTING | 19 Always try the latest kernel from kernel.org and build from source. If you are
23 Finding bugs is not always easy. Have a go though. If you can't find it don't
24 give up. Report as much as you have found to the relevant maintainer. See
25 MAINTAINERS for who that is for the subsystem you have worked on.
27 Before you submit a bug report read REPORTING-BUGS.
56 This is how to track down a bug if you know nothing about kernel hacking.
67 . Rebuild a revision that you believe works, install, and verify that.
70 you know that 1.3.69 does. Pick a kernel in the middle and build
79 but 3.63 doesn't. So you diff -r those two kernels and come
97 found in my case that they were self explanatory - you may
[all …]
|
| D | kref.txt | 2 krefs allow you to add reference counters to your objects. If you
4 you don't have refcounts, your code is almost certainly broken. If
5 you want refcounts, krefs are the way to go.
20 You must initialize the kref after you allocate it. To do this, call
32 Once you have an initialized kref, you must follow the following
35 1) If you make a non-temporary copy of a pointer, especially if
36 it can be passed to another thread of execution, you must
39 If you already have a valid pointer to a kref-ed structure (the
40 refcount cannot go to zero) you may do this without a lock.
42 2) When you are done with a pointer, you must call kref_put():
[all …]
|
| D | spinlocks.txt | 35 The above is usually pretty simple (you usually need and want only one
38 sequences that you _know_ need to be split up: avoid it at all cost if you
39 aren't sure). HOWEVER, it _does_ mean that if you have some code that does
56 The above is a problem mainly if you end up mixing code - for example the
58 their actions, and if a driver uses spinlocks instead then you should
61 This is really the only really hard part about spinlocks: once you start
62 using spinlocks they tend to expand to areas you might not have noticed
63 before, because you have to make sure the spinlocks correctly protect the
68 NOTE! The spin-lock is safe only when you _also_ use the lock itself
77 If your data accesses have a very natural pattern where you usually tend
[all …]
|
| /linux-2.6.39/drivers/net/arm/ |
| D | Kconfig | 10 If you wish to compile a kernel for the EBSA-110, then you should
17 If you have an Acorn system with one of these (AKA25) network cards,
18 you should say Y to this option if you wish to use it with Linux.
24 If you have an Acorn system with one of these network cards, you
25 should say Y to this option if you wish to use it with Linux.
32 If you have an Acorn system with one of these network cards, you
33 should say Y to this option if you wish to use it with Linux.
40 If you wish to compile a kernel for the AT91RM9200 and enable
41 ethernet support, then you should always answer Y to this.
48 If you wish to compile a kernel for the KS8695 and want to
[all …]
|
| /linux-2.6.39/drivers/block/paride/ |
| D | Kconfig | 16 connected through a parallel port. If you chose to build PARIDE
17 support into your kernel, you may answer Y here to build in the
18 parallel port IDE driver, otherwise you should answer M to build
30 connected through a parallel port. If you chose to build PARIDE
31 support into your kernel, you may answer Y here to build in the
32 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
37 you have such a CD-ROM drive, you should also say Y or M to "ISO
46 connected through a parallel port. If you chose to build PARIDE
47 support into your kernel, you may answer Y here to build in the
48 parallel port ATAPI disk driver, otherwise you should answer M
[all …]
|
| /linux-2.6.39/drivers/rtc/ |
| D | Kconfig | 14 Generic RTC class support. If you say yes here, you will
28 If you say yes here, the system time (wall clock) will be set using
50 If the clock you specify here is not battery backed, it may still
69 Say yes here if you want to use your RTCs using sysfs interfaces,
79 Say yes here if you want to use your first RTC through the proc
89 Say yes here if you want to use your RTCs using the /dev
96 versions of "udev" are known to set up the symlink for you.
110 only if you know that you really need it.
115 If you say yes here you get support for the
119 You want this driver only if you are doing development
[all …]
|
| /linux-2.6.39/arch/arm/mach-orion5x/ |
| D | Kconfig | 9 Say 'Y' here if you want your kernel to support the
16 Say 'Y' here if you want your kernel to support the
23 Say 'Y' here if you want your kernel to support the
31 Say 'Y' here if you want your kernel to support the
37 Say 'Y' here if you want your kernel to support the
43 Say 'Y' here if you want your kernel to support the
50 Say 'Y' here if you want your kernel to support the
58 Say 'Y' here if you want your kernel to support the
65 Say 'Y' here if you want your kernel to support the
72 Say 'Y' here if you want your kernel to support the
[all …]
|
| /linux-2.6.39/drivers/staging/olpc_dcon/ |
| D | Kconfig | 7 only available on OLPC platforms. Unless you have one of these
8 platforms, you will want to say 'N'.
16 communicates with the DCON using model-specific code. If you
17 have an XO-1 (or if you're unsure what model you have), you should
26 communicates with the DCON using model-specific code. If you
27 have an XO-1.5 (or if you're unsure what model you have), you
|
| /linux-2.6.39/arch/arm/mach-ep93xx/ |
| D | Kconfig | 19 Select this option if you want support for EP93xx boards with the
25 Select this option if you want support for EP93xx boards with the
31 Select this option if you want support for EP93xx boards with the
37 Select this option if you want support for EP93xx boards with the
43 Select this option if you want support for EP93xx boards with the
52 Say 'Y' here if you want your kernel to support the ADS
63 Say 'Y' here if you want your kernel to support the Cirrus
71 Say 'Y' here if you want your kernel to support the Cirrus
79 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 …]
|
| /linux-2.6.39/drivers/auxdisplay/ |
| D | Kconfig | 14 If you say N, all options in this submenu will be skipped and disabled.
23 If you have a LCD controlled by one or more KS0108
27 Depends on Parallel Port support. If you say Y at
28 parport, you will be able to compile this as a module (M)
47 You can specify a different address if you need.
49 If you don't know what I'm talking about, load the parport module,
53 Usually you only need to use 0x378.
55 If you compile this as a module, you can still override this
68 If you don't know what I'm talking about, ignore it.
70 If you compile this as a module, you can still override this
[all …]
|
| /linux-2.6.39/arch/arm/mach-kirkwood/ |
| D | Kconfig | 8 Say 'Y' here if you want your kernel to support the
14 Say 'Y' here if you want your kernel to support the
20 Say 'Y' here if you want your kernel to support the
26 Say 'Y' here if you want your kernel to support the
32 Say 'Y' here if you want your kernel to support the
38 Say 'Y' here if you want your kernel to support the
44 Say 'Y' here if you want your kernel to support the
50 Say 'Y' here if you want your kernel to support the
57 Say 'Y' here if you want your kernel to support the
64 Say 'Y' here if you want your kernel to support the
[all …]
|
| /linux-2.6.39/fs/jbd/ |
| D | Kconfig | 9 If you are using the ext3 file system, you need to say Y here.
10 If you are not using ext3 then you will probably want to say N.
13 called jbd. If you are compiling ext3 into the kernel, you
20 If you are using the ext3 journaled file system (or potentially any
21 other file system/device using JBD), this option allows you to
23 help track down any problems you are having. By default the
26 If you select Y here, then you will be able to turn on debugging
|
| /linux-2.6.39/fs/jbd2/ |
| D | Kconfig | 11 If you are using ext4 or OCFS2, you need to say Y here.
12 If you are not using ext4 or OCFS2 then you will
16 called jbd2. If you are compiling ext4 or OCFS2 into the kernel,
17 you cannot compile this code as a module.
23 If you are using the ext4 journaled file system (or
25 allows you to enable debugging output while the system is running,
26 in order to help track down any problems you are having.
29 If you select Y here, then you will be able to turn on debugging
|
| /linux-2.6.39/drivers/media/dvb/frontends/ |
| D | Kconfig | 26 A DVB-S/S2/DSS Multistandard demodulator. Say Y when you want
35 demodulator. Say Y when you want to support this tuner.
43 Say Y when you want to support these frontends.
60 A DVB-S tuner module. Say Y when you want to support this frontend.
67 A DVB-S tuner module. Say Y when you want to support this frontend.
74 A DVB-S tuner module. Say Y when you want to support this frontend.
81 A DVB-S tuner module. Say Y when you want to support this frontend.
88 A DVB-S tuner module. Say Y when you want to support this frontend.
95 A DVB-S tuner module. Say Y when you want to support this frontend.
102 A DVB-S tuner module. Say Y when you want to support this frontend.
[all …]
|
| /linux-2.6.39/drivers/w1/slaves/ |
| D | Kconfig | 10 Say Y here if you want to connect 1-wire thermal sensors to your
16 Say Y here if you want to connect 1-wire
23 If you enable this you can read the counter values available
27 Say Y here if you want to use a 1-wire
33 Say Y here if you want to use a 1-wire
39 Say Y here if you want to use a 1-wire
55 If you enable this you will have the DS2760 battery monitor
62 If you are unsure, say N.
68 Say Y here if you want to use a hdq
|
| /linux-2.6.39/fs/nls/ |
| D | Kconfig | 34 If you specify a wrong value, it will use the built-in NLS;
45 codepage if you want to be able to read/write these filenames on
48 say Y here if you want to include the DOS codepage that is used in
57 codepage if you want to be able to read/write these filenames on
60 say Y here if you want to include the DOS codepage that is used for
69 codepage if you want to be able to read/write these filenames on
72 say Y here if you want to include the DOS codepage that is used
82 codepage if you want to be able to read/write these filenames on
85 say Y here if you want to include the DOS codepage that is used for
98 codepage if you want to be able to read/write these filenames on
[all …]
|
| /linux-2.6.39/Documentation/serial/ |
| D | sx.txt | 9 Please DO contact support@specialix.co.uk if you require
13 driver service. If you require a linux device driver for your
25 This program is free software; you can redistribute it and/or
41 I'd appreciate it that if you have fixes, that you send them
57 firmware for the card. This means that you need the separate package
58 "sx_firmware". For now you can get the source at
62 The firmware load needs a "misc" device, so you'll need to enable the
71 when you then run "sx_firmware" will the firmware be downloaded and
78 descriptor structures when you only have 8 ports. If you experience
96 interrupts would be better if you have most of the ports idle. Using
[all …]
|
| /linux-2.6.39/arch/arm/mach-at91/ |
| D | Kconfig | 112 Select this if you are using Ajeco's 1ARM Single Board Computer.
119 Select this if you are using Atmel's AT91RM9200-DK Development board.
126 Select this if you are using Atmel's AT91RM9200-EK Evaluation Kit.
132 Select this if you are using Cogent's CSB337 board.
138 Select this if you are using Cogent's CSB637 board.
144 Select this if you are using Conitec's AT91RM9200-MCU-Module.
150 Select this if you are using Embest's ATEB9200 board.
156 Select this if you are using KwikByte's KB920x board.
162 Select this if you are using a picotux 200.
168 Select this if you are using Sperry-Sun's KAFA board.
[all …]
|
| /linux-2.6.39/drivers/net/appletalk/ |
| D | Kconfig | 9 on a network. If your Linux box is connected to such a network and you
27 module so you can restart your AppleTalk stack without rebooting
37 to do IP over it, or you have a LocalTalk card and wish to use it to
45 This allows you to use the AppleTalk PC card to connect to LocalTalk
47 If you are in doubt, this card is the one with the 65C02 chip on it.
56 This allows you to use COPS AppleTalk cards to connect to LocalTalk
59 work. This driver will only work if you choose "AppleTalk DDP"
84 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
86 you want your Linux box to act as an Internet gateway for a zoo of
90 If you say Y here, the AppleTalk-IP support will be compiled into
[all …]
|
| /linux-2.6.39/Documentation/networking/ |
| D | arcnet.txt | 3 and cabling information if you're like many of us and didn't happen to get a
15 The point is: I REALLY REALLY REALLY REALLY REALLY want to hear from you if
16 you test this and get it working. Or if you don't. Or anything.
31 If you don't e-mail me about your success/failure soon, I may be forced to
35 If you think so, why not flame me in a quick little e-mail? Please also
36 include the type of card(s) you're using, software, size of network, and
84 Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
97 one you'll want to use with ARCnet cards) from
100 versions are available on my WWW page, or via e-mail if you don't have WWW
107 All you will need to do in order to install the driver is:
[all …]
|
| /linux-2.6.39/Documentation/development-process/ |
| D | 6.Followthrough | 3 At this point, you have followed the guidelines given so far and, with the
24 process. Life can be made much easier, though, if you keep a few things in
27 - If you have explained your patch well, reviewers will understand its
28 value and why you went to the trouble of writing it. But that value
31 Many of the changes you may be asked to make - from coding style tweaks
38 they see the same mistakes being made over and over again. If you get a
41 the people, and code reviewers are not attacking you personally.
50 What all of this comes down to is that, when reviewers send you comments,
51 you need to pay attention to the technical observations that they are
53 from happening. When you get review comments on a patch, take the time to
[all …]
|
| /linux-2.6.39/net/unix/ |
| D | Kconfig | 8 If you say Y here, you will include support for Unix domain sockets;
12 machine is not connected to any network. Unless you are working on
13 an embedded system or something similar, you therefore definitely
18 correctly if you say M here and then neglect to load the module.
20 Say Y unless you know what you are doing.
|
| /linux-2.6.39/ |
| D | README | 4 as they tell you what this is all about, explain how to install the
13 It has all the features you would expect in a modern fully-fledged Unix,
61 - If you install the full sources, put the kernel tarball in a
62 directory where you have permissions (eg. your home directory) and
89 source tree, _in_order_) and you should be ok. You may want to remove
91 failed patches (xxx# or xxx.rej). If there are, either you or me has
109 - If you are upgrading between releases using the stable series patches
112 example, if your base kernel is 2.6.12 and you want to apply the
113 2.6.12.3 patch, you do not and indeed must not first apply the
114 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
[all …]
|