Home
last modified time | relevance | path

Searched refs:enough (Results 1 – 25 of 223) sorted by relevance

123456789

/linux-2.6.39/Documentation/fb/
Dsa1100fb.txt16 on the kernel command line should be enough to configure the
25 options may not be enough to configure the display. Adding sections to
/linux-2.6.39/drivers/staging/olpc_dcon/
DTODO3 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/linux-2.6.39/drivers/thermal/
DKconfig24 Say Y if your user-space is new enough.
/linux-2.6.39/arch/parisc/math-emu/
DREADME5 enough to update our copies with later changes from HP-UX -- it'll
/linux-2.6.39/arch/arm/boot/compressed/
Dhead-xscale.S22 add r3, r2, #0x10000 @ 64 kb is quite enough...
/linux-2.6.39/Documentation/scheduler/
Dsched-nice-design.txt79 nice levels were not 'punchy enough', so lots of people had to resort to
87 enough), the scheduler was decoupled from 'time slice' and HZ concepts
104 The third complaint (of negative nice levels not being "punchy" enough
/linux-2.6.39/drivers/staging/gma500/
DTODO8 interfaces rather than just faking it enough for a framebuffer
/linux-2.6.39/Documentation/power/
Dvideo.txt9 initialized by BIOS, and kernel does not have enough information to
49 the BIOS works well enough to be able to set video mode. Use
56 a new enough X, and a plain text console (no vesafb or radeonfb). See
60 (6) other radeon systems, where vbetool is enough to bring system back
/linux-2.6.39/drivers/message/i2o/
DREADME.ioctl81 ENOBUFS Buffer not large enough. If this occurs, the required
110 ENOBUFS Buffer not large enough. If this occurs, the required
145 ENOBUFS Buffer not large enough. If this occurs, the required
182 ENOBUFS Buffer not large enough. If this occurs, the required
367 ENOBUFS Buffer not large enough. If this occurs, the required
/linux-2.6.39/Documentation/i2o/
Dioctl81 ENOBUFS Buffer not large enough. If this occurs, the required
110 ENOBUFS Buffer not large enough. If this occurs, the required
145 ENOBUFS Buffer not large enough. If this occurs, the required
182 ENOBUFS Buffer not large enough. If this occurs, the required
367 ENOBUFS Buffer not large enough. If this occurs, the required
/linux-2.6.39/Documentation/networking/
Dtc-actions-env-rules.txt12 avoid loops, etc. A few are generic enough that skb_act_clone()
Dipvs-sysctl.txt14 enough available memory, the respective strategy will be
62 modes (when there is no enough available memory, the strategy
/linux-2.6.39/Documentation/hwmon/
Dpkgtemp29 may be raised, if the temperature grows enough (more than TjMax) to trigger
Dw83l785ts39 there is no old value). It seems to work well enough so that you should
/linux-2.6.39/include/linux/
Dpage_cgroup.h132 #error Not enough space left in pc->flags to store page_cgroup array IDs
/linux-2.6.39/arch/sh/lib/
Dmemset-sh4.S36 ! Check if enough bytes need to be copied to be worth the big loop
/linux-2.6.39/arch/arm/lib/
Dmemset.S19 1: subs r2, r2, #4 @ 1 do we have enough
Dmemzero.S21 1: subs r1, r1, #4 @ 1 do we have enough
/linux-2.6.39/Documentation/ABI/testing/
Dsysfs-class-pktcdvd53 device has processed enough bio's
/linux-2.6.39/Documentation/video4linux/cx88/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
/linux-2.6.39/Documentation/video4linux/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
/linux-2.6.39/Documentation/device-mapper/
Dzero.txt15 enough data has been written to fill up the actual storage space, the sparse
/linux-2.6.39/Documentation/
Dio_ordering.txt28 which could cause problems. Fixing it is easy enough though:
/linux-2.6.39/drivers/staging/iio/
DTODO39 1) Discussion of approach. Is it general enough?
/linux-2.6.39/Documentation/i2c/
Di2c-stub51 If you spam it hard enough, printk can be lossy. This module really wants

123456789