Home
last modified time | relevance | path

Searched refs:same (Results 1 – 25 of 307) sorted by relevance

12345678910>>...13

/linux-2.4.37.9/fs/umsdos/
DREADME-WIP.txt33 + rename file (same dir) - works
35 + rename dir (same dir) - works
66 + rename file (same dir) - works
68 + rename hardlink (same dir) - works
70 + rename symlink (same dir) - works
72 + rename dir (same dir) - works
Dspecs35 * Since umsdos entries are much larger, we share the same f_pos.
147 * same target at the same time. Again, I am not sure it
156 * We will used the same strategy as a normal Unix file system
233 * keeps the same pseudo inode when a rename operation
234 * is done on a file in the same directory.
/linux-2.4.37.9/Documentation/video4linux/bttv/
DREADME.quirks6 The vsfx insmod option does the same for EN_VSFX bit. If you have
43 (1) Deassert REQ at the same time as asserting FRAME.
61 responsibility to remove its request at the same time. It is the
73 during the same cycle that GNT is de-asserted. This is non PCI 2.1
78 transaction from starting the same cycle as GNT is de-asserted. This
/linux-2.4.37.9/Documentation/
DIO-mapping.txt33 external hardware sees the memory the same way.
35 Now, on normal PCs the bus address is exactly the same as the physical
37 because the memory and the devices share the same address space, and that is
47 Now, that looks simple enough. However, when you look at the same thing from
61 where all the addresses actually point to the same thing. It's just seen
71 are the same).
138 conceptually in the same memory space as "real memory" at all, so you cannot
139 just dereference a pointer. (Sadly, on x86 it _is_ in the same memory space,
Ddevices.txt65 Second, please include a description of the device *in the same format
276 Partitions are handled in the same way as for IDE
474 Partitions are handled in the same way as IDE disks
500 Partitions are handled in the same way as IDE disks
569 Partitions are handled the same way as for IDE disks
580 Partitions are handled the same way as for the first
685 Partitions are handled in the same way as for IDE
761 Partitions are handled the same way as for the first
779 Partitions are handled the same way as for the first
810 Partitions are handled in the same way as IDE disks
[all …]
Dspinlocks.txt34 essentially is just the same as doing a
71 at the same time on two different CPU's. That's fine per se, but the
95 readers to be in the same critical region at once, but if somebody wants
97 routines look the same as above:
147 guarantee the same kind of exclusive access, and it will be much faster.
161 interrupt happens on the same CPU that already holds the lock, because the
DREADME.moxa11 b. Multiple Smartio PCI series boards sharing the same IRQ
/linux-2.4.37.9/Documentation/filesystems/
Disofs.txt1 Mount options that are the same as for msdos and vfat partitions.
7 Mount options that are the same as vfat partitions. These are only useful
21 check=strict Matches only filenames with the exact same case
Dumsdos.txt36 The default behavior of Umsdos is to do the same thing as the msdos driver
47 same way the msdos driver does. Short file names, no goodies, default
61 from the same directory above (sunsite) in the file umsdos_progs-0.7.tar.gz.
96 so you will be allowed to manage umsdos partitions in the same way
/linux-2.4.37.9/Documentation/isdn/
DREADME.icn22 all cards are mapped to the same window and activated as needed.
88 maps all cards into the same address-space.
105 where p, m, idstring1 and idstring2 have the same meanings as the
113 Using the "icnctrl"-utility, the same features apply to the modularized
139 To load a 4B-card, the same command is used, except a second firmware
/linux-2.4.37.9/Documentation/ia64/
DREADME10 - IA-64 kernel installation is the same as the other platforms, see
23 Configuration is the same, see original README for details.
/linux-2.4.37.9/drivers/scsi/
DREADME.g_NCR538011 modes at a time but it does support both of these chips at the same time.
13 the same time. It should be able to handle multiple different cards in the
14 same machine.
/linux-2.4.37.9/fs/cramfs/
DREADME28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
29 lines); put another way, the same order as `find -type d -exec
48 same as the start of the (i+1)'th <block> if there is one). The first
53 tree, i.e. the same order as `find -size +0 \( -type f -o -type l \)
107 kernels, not even necessarily kernels of the same architecture if
/linux-2.4.37.9/Documentation/networking/
Dfilter.txt14 the same filter code structure as the BSD Berkeley Packet Filter
28 may be adding a different filter on the same socket where you had another
Dz8530drv.txt103 IRQs or the same. If they share an interrupt, it needs to be
222 Its parameters are exactly the same as the ones you use with
232 does the same for the BAYCOM USCC card. In my opinion it is much easier
415 same way in the SCC driver. You can change parameters by using
537 has same result as the fullduplex mode 1. This parameter
559 one frequency on the same band, e.g. using several receivers and
561 Also, you can connect several radios that are active on the same
576 Interfaces are in the same group, when the logical AND
581 keyed at the same time.
583 when both channels are clear at the same time. When group 301,
[all …]
Dx25-iface.txt54 LAPB link has been established. The same message is used for both a LAPB
59 LAPB link has been terminated. This same message is used for both a LAPB
92 always executed on the same CPU. Thus,
/linux-2.4.37.9/Documentation/sound/
DIntroduction71 for the same or a similar feature (dma1= versus dma16=). As a last
88 multiple sounds at the same time via a single card, eliminating
248 multiple PCI sound cards of the same type.
259 If you have two cards of the same type that are jumpered
260 cards or different PnP revisions, you may load the same
277 same type to load at the same time. I have tried this several times
299 A) If you have Win95 or NT on the same computer,
301 those were using for the same hardware. You probably
320 2) If you get motor-boating (the same sound or part of a
/linux-2.4.37.9/arch/x86_64/kernel/
Dtrampoline.S37 mov %cs, %ax # Code and data in the same place
/linux-2.4.37.9/arch/i386/kernel/
Dtrampoline.S40 mov %cs, %ax # Code and data in the same place
/linux-2.4.37.9/Documentation/vm/
Dnuma9 Each region of memory to which access times are the same from any
19 can use the same code. All this code is bracketed by CONFIG_DISCONTIGMEM.
/linux-2.4.37.9/Documentation/mips/
DGT64120.README9 Many MIPS boards share the same system controller (or CPU companian chip),
11 the same controller code instead of duplicating them.
/linux-2.4.37.9/fs/
DChangeLog27 the directory we remove is the same as parent (BUG: we
83 the same name and said mv . /tmp/goodbye_sticky_bit... Well,
92 * namei.c (VFS_rename): New function. It gets the same arguments as
127 Added new function: vfs_unlink, with the same arguments as
/linux-2.4.37.9/arch/sh/kernel/
Dubc.S24 mov.l 2f, r1 ! .. same for BBRB ..
/linux-2.4.37.9/net/ipv4/
Ddevinet.c795 int same = 0; in confirm_addr_indev() local
803 if (same) in confirm_addr_indev()
806 if (!same) { in confirm_addr_indev()
807 same = (!local || inet_ifa_match(local, ifa)) && in confirm_addr_indev()
809 if (same && addr) { in confirm_addr_indev()
821 same = 0; in confirm_addr_indev()
826 return same? addr : 0; in confirm_addr_indev()
/linux-2.4.37.9/drivers/char/ftape/
DREADME.PCI25 implementations having the same of similar problems.
31 My DOS backup software seems to be suffering from the same problems

12345678910>>...13