/linux-3.4.99/arch/powerpc/platforms/cell/spufs/ |
D | hw_ops.c | 40 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read() 56 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read() 67 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll() 99 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read() 120 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write() 140 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write() 145 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write() 192 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read() 197 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write() 202 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read() [all …]
|
D | switch.c | 97 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate() 217 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl() 236 struct spu_problem __iomem *prob = spu->problem; in save_spu_status() 310 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync() 382 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask() 393 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype() 404 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus() 517 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc() 601 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat() 611 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb() [all …]
|
/linux-3.4.99/ |
D | REPORTING-BUGS | 13 be involved with the problem, and cc the relevant mailing list. Don't 19 know the file name that causes the problem you can use the following 44 [1.] One line summary of the problem: 45 [2.] Full description of the problem/report: 54 problem (if possible) 62 [8.7.] Other information that might be relevant to the problem
|
/linux-3.4.99/Documentation/zh_CN/ |
D | SecurityBugs | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
D | stable_kernel_rules.txt | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
D | stable_api_nonsense.txt | 4 original document maintainer directly. However, if you have problem 7 is problem with translation.
|
D | sparse.txt | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
D | volatile-considered-harmful.txt | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
D | SubmittingDrivers | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
D | email-clients.txt | 4 original document maintainer directly. However, if you have a problem 7 or if there is a problem with the translation.
|
/linux-3.4.99/Documentation/networking/ |
D | vortex.txt | 198 decision. If you think that Tx checksums are causing a problem, you 217 "Variables to work-around the Compaq PCI BIOS32 problem".... 320 On a side note, adding HAS_NWAY seems to share a problem with the 335 If autonegotiation is a problem, you may need to specify "speed 345 Maintainers find that accurate and complete problem reports are 348 the bottom of the problem. 350 If you believe you have a driver problem here are some of the 353 - Is it really a driver problem? 359 - OK, it's a driver problem. 366 problem. If it's a kernel crash then you should refer to the [all …]
|
D | skfp.txt | 90 is not there, then you may have a hardware problem or PCI 95 Some COMPAQ machines have a problem with PCI under 104 forwarding or there is a problem with the routing table 108 If your problem is not listed here, please contact our 217 document for details about this problem.
|
/linux-3.4.99/arch/powerpc/platforms/ps3/ |
D | spu.c | 136 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument 141 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas() 190 iounmap(spu->problem); in spu_unmap() 227 spu->problem = ioremap(spu->problem_phys, in setup_areas() 230 if (!spu->problem) { in setup_areas() 247 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
|
/linux-3.4.99/arch/powerpc/platforms/cell/ |
D | spu_manage.c | 75 iounmap(spu->problem); in spu_unmap() 155 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old() 156 if (!spu->problem) in spu_map_device_old() 248 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device() 273 spu->problem_phys, spu->problem); in spu_map_device() 355 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
|
/linux-3.4.99/Documentation/development-process/ |
D | 3.Early-stage | 13 clear description of the problem to be solved. In some cases, this step is 15 example. In others, though, it is tempting to confuse the real problem 27 immediate problem. To the wider kernel community, though, it was seen as a 49 the right solution to the problem than they were with a specific module. 50 The moral of the story is to focus on the problem - not a specific solution 57 - What, exactly, is the problem which needs to be solved? 59 - Who are the users affected by this problem? Which use cases should the 62 - How does the kernel fall short in addressing that problem now? 73 - It may well be that the problem is addressed by the kernel in ways which 87 problem; they may have ideas for a better solution, and may be willing [all …]
|
/linux-3.4.99/Documentation/power/ |
D | basic-pm-debugging.txt | 102 that there is a problem with the tasks freezer subsystem that should be 117 make sure to report the problem with the driver. 125 If the "platform" test fails, there is a problem with the handling of the 131 work (of course, this only may be an issue on SMP systems) and the problem 138 the problem is most probably hardware-related and serious, so it should be 143 indicates a serious problem that very well may be related to the hardware, but 151 probably is a problem with a driver statically compiled into the kernel and you 153 individually. Otherwise, there is a problem with a modular driver and you can 163 before hibernation, and please report the problem with it(them). 170 techniques to find the problem. First, if there is a serial port in your box,
|
/linux-3.4.99/Documentation/sound/oss/ |
D | mwave | 9 OK, first thing - the IRQ problem IS a problem, whether the test is bypassed or 10 not. It is NOT a Linux problem, but an MWAVE problem that is fixed with the 169 problem with the SB1.5 (CD sound) or SBPRO (Mixers) settings. No one knows why
|
/linux-3.4.99/Documentation/arm/nwfpe/ |
D | NOTES | 1 There seems to be a problem with exp(double) and our emulator. I haven't 22 This code will cause this problem:
|
D | README | 41 attempting to isolate the problem. Please report them, but don't 42 expect quick action. Bugs still exist. The problem remains in isolating 44 problem are a godsend.
|
/linux-3.4.99/fs/exofs/ |
D | BUGS | 1 - Out-of-space may cause a severe problem if the object (and directory entry)
|
/linux-3.4.99/Documentation/filesystems/ |
D | sysfs-tagging.txt | 7 The problem. Network devices show up in sysfs and with the network 11 To avoid that problem and allow existing applications in network
|
/linux-3.4.99/drivers/i2c/ |
D | Kconfig | 95 problem with I2C support and want to see more of what is going on. 102 a problem with I2C support and want to see more of what is going 110 a problem with I2C support and want to see more of what is going
|
/linux-3.4.99/Documentation/ide/ |
D | ChangeLog.ide-cd.1994-2004 | 3 * 1.01 Nov 2, 1994 -- Fixed problem with starting request in 24 * Aztech drives, which seem to have the same problem. 84 * Work around sporadic Sony55e audio play problem. 86 * problem with "hde=cdrom" with no drive present. -ml 241 * - Fixed a problem with WPI CDS-32X drive - it 255 * - Fix small problem with ide_cdrom_capacity 257 * 4.59 Aug 11, 2000 - Fix changer problem in cdrom_read_toc, we weren't
|
/linux-3.4.99/drivers/infiniband/hw/amso1100/ |
D | Kconfig | 15 or trying to diagnose a problem.
|
/linux-3.4.99/drivers/infiniband/hw/nes/ |
D | Kconfig | 16 driver. Select this if you are diagnosing a problem.
|