search for: 0x1000000

Hi all, I''ve got overlapped and offset support in both nread and nwrite. The only thing left before I want to release this (as 0.4.0) is to get NO_BUFFERING to work. Unfortunately, I can''t get it to work. Park, I looked at that site you sent (and borrowed some code from it), but I don''t see anything special happening for NO_BUFFERING. I thought it required

http://bugs.freedesktop.org/show_bug.cgi?id=14941 Summary: ioremap leak in DRM Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

...ype2 Ri, Rj, Rk, Rl, Rm, Rn add_type3 Ri, Rj, Rk, Rl, Rm, Rn, Ro, Rp, Rq Q2. Some of the instructions need to setup additional configuration, e.g. { scache wa ; Set cache mode: write allocate ssize 64 ; Set write size = 64 bits sendian big ; Set big endian writing store R0, 0x1000000 ; Write "R0" to 0x1000000 } So, again, parser has to parse the entire bundle to generate correct encoding. Or I should define my instruction in this way: store R0, 0x1000000, wa, 64, big, .... (10 options can be set) Q3. The destination register can be omitted, e.g. add , Rj, Rk S...

...0 0x00000000 - 0xffffffff (0x0) MX[b] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xdd000000 - 0xdfefffff (0x2f00000) MX[b] (II) Bus 1 prefetchable memory range: [0] -1 0 0xc0000000 - 0xcfffffff (0x10000000) MX[b] (II) Subtractive PCI-to-PCI bridge: (II) Bus 3: bridge is at (0:30:0), (0,3,7), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 3 I/O range: [0] -1 0 0x00002000 - 0x00002fff (0x1000) IX[b] (II) Bus 3 non-prefetchable memory range: [0] -1 0 0xdcf00000 - 0xdcffffff (0x100000) MX[b] (II) Bus 3 pref...

Hello, all I thought dom0 is layed out on physical memory starting 0, linearly, but this message, (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to be allocated) shows the address range 0000000c14000000->0000000c18000000 , what is this? it''s 64MB range and why 64MB from Dom0 is located here? I think 498...

...of decompressed kernel and fails to do that for me. extract_kernel() method is: https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/boot/compressed/misc.c#L334 I added next lines before return: __putstr("hi from extract_kernel"); if ((int) output == 0x1000000) __putstr("== 0x1000000"); output[0] = 0xEB; output[1] = 0xFE; return output; And during boot in shows all text from above and enters infinite loop as expected. So, that means it successfully jumps to 0x1000000, but looks something is wrong in decompressed code. Next destination point...

...:LivePhysRegs <- %RDX #DEBUG_VALUE: isReg:this <- %RDI .loc 2 127 18 prologue_end # ../lib/CodeGen/DeadMachineInstructionElim.cpp:127:18 movl $16777471, %eax # imm = 0x10000FF andl (%rdi), %eax .Ltmp128: #DEBUG_VALUE: isReg:this <- %RDI cmpl $16777216, %eax # imm = 0x1000000 jne .LBB4_2 # BB#1: # %if.then #DEBUG_VALUE: xfuncx:LivePhysRegs <- %RDX #DEBUG_VALUE: xfuncx:TRI <- %RSI #DEBUG_VALUE: xfuncx:MO <- %RDI .Ltmp129: .loc 2 129 5 # ../lib/CodeGen/DeadMachineInstructionElim.cpp:129:5 jmp _Z6xfunc2RKN4ll...

...o the asm: > > 0000000000000000 > <_Z6xfuncxPKN4llvm14MachineOperandEPKNS_18TargetRegisterInfoEPNS_9BitVectorE>: > > 0: b8 ff 00 00 01 mov $0x10000ff,%eax > 5: 23 07 and (%rdi),%eax > 7: 3d 00 00 00 01 cmp $0x1000000,%eax > c: 75 05 jne 13 > <_Z6xfuncxPKN4llvm14MachineOperandEPKNS_18TargetRegisterInfoEPNS_9BitVectorE+0x13> > > e: e9 00 00 00 00 jmpq 13 > <_Z6xfuncxPKN4llvm14MachineOperandEPKNS_18TargetRegisterInfoEPNS_9BitVectorE+0x13> &gt...

...+ nv_mask(pmc, 0x00000200, 0x2000, 0x00000000); + return 0; + } +} +static void +gk20a_pmu_enable_irq(struct gk20a_pmu_priv *priv, struct nvkm_mc *pmc, bool enable) +{ + if (enable) { + nv_debug(priv, "enable pmu irq\n"); + nv_wr32(priv, 0x0010a010, 0xff); + nv_mask(pmc, 0x00000640, 0x1000000, 0x1000000); + nv_mask(pmc, 0x00000644, 0x1000000, 0x1000000); + } else { + nv_debug(priv, "disable pmu irq\n"); + nv_mask(pmc, 0x00000640, 0x1000000, 0x00000000); + nv_mask(pmc, 0x00000644, 0x1000000, 0x00000000); + nv_wr32(priv, 0x0010a014, 0xff); + } - nvkm_timer_alarm_cancel(pr...

Hi, The following code: #include<stdio.h> char bigArray[0x1000000]; int main(int argc, char **argv) { printf("mem: 0x%x\n", (unsigned) bigArray); return 0; } causes lli to silently fail, even though it compiles correctly with llc. The reason is that in JITEmitter.cpp only checks to see if CurBufferPtr == BufferEnd at the beginning of the functi...

Here is the corrected version. Thomas Jablin wrote: > Actually, there is a problem with the patch. Please delay review. > > Thomas Jablin wrote: > >> Hi, >> The following code: >> >> #include<stdio.h> >> >> char bigArray[0x1000000]; >> >> int main(int argc, char **argv) { >> printf("mem: 0x%x\n", (unsigned) bigArray); >> return 0; >> } >> >> causes lli to silently fail, even though it compiles correctly with >> llc. The reason is that in JITEmitter.cpp only checks...

...[ALKC] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 90 PCI: Setting latency timer of device 0000:00:11.5 to 64 codec_read: codec 0 is not valid [0x1fc0000] codec_read: codec 0 is not valid [0x1fe0000] codec_ready: codec 0 is not ready [0x1000000] codec_ready: codec 0 is not ready [0x1000000] codec_read: codec 0 is not valid [0x1fc0000] codec_read: codec 0 is not valid [0x1fe0000] AC'97 0 access is not valid [0xffffffff], removing mixer. ACPI: PCI interrupt for device 0000:00:11.5 disabled VIA 82xx Audio: probe of 0000:00:11.5 failed wi...

...- 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xf5200000 - 0xf53fffff (0x200000) MX[B]E [1] -1 0 0xf5000000 - 0xf5ffffff (0x1000000) MX[B]E [2] -1 0 0xf5004000 - 0xf5007fff (0x4000) MX[B]E [3] -1 0 0x80080000 - 0x800fffff (0x80000) MX[B]E [4] -1 0 0x80081000 - 0x80081fff (0x1000) MX[B]E [5] -1 0 0x80082000 - 0x80083fff (0x2000) MX[B]E [6] -1 0 0x80083000...

...177c..05c62549c39b 100644 --- a/drm/nouveau/nvkm/subdev/secboot/base.c +++ b/drm/nouveau/nvkm/subdev/secboot/base.c @@ -85,8 +85,8 @@ nvkm_secboot_falcon_enable(struct nvkm_secboot *sb) /* enable IRQs */ nvkm_wr32(device, sb->base + 0x010, 0xff); - nvkm_mask(device, 0x640, sb->irq_mask, 0x1000000); - nvkm_mask(device, 0x644, sb->irq_mask, 0x1000000); + nvkm_mask(device, 0x640, sb->irq_mask, sb->irq_mask); + nvkm_mask(device, 0x644, sb->irq_mask, sb->irq_mask); return 0; } -- 2.7.2

...happen. - I copied the necessary "mshta.exe" into the "system32" directory of my wine installation, now when i try to run TD.exe i get: Code: fixme:process:RegisterApplicationRestart (L"\"ms-its:TD.lib::/directorFS.hta\"",0) fixme:mshtml:RunHTMLApplication 0x1000000 (nil) "\"ms-its:TD.lib::/directorFS.hta\"" 10 I'm using ubuntu 8.04 and wine 1.1.5 without any modifications. Has anyone had more luck with this software? Thanks a lot in advance!

Saludos a la lista, I installed CentOS under Vmware, when start statrx, this service goes down with the this error: (WW) VMWARE (0): Failed to set up write-combining range (0xf0000000, 0x1000000). Somebody knows where may I find a driver or files needed to solve it? Atentamente, Miguel. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070218/cc6d3134/attachment.html>

If you compiled your kernel and booted under Xen and got: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x9db000 (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xa30f0 (XEN) elf_parse_binary: phdr: paddr=0x1aa4000 memsz=0x13c00 (XEN) elf_parse_binary: phdr: paddr=0x1ab8000 memsz=0x206000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x1cbe000 (XEN) elf_xen_note_check: ERROR: Will only lo...

...t; > which should hopefully print some info from the kernel boot paths. > > -- > Matt Fleming, Intel Open Source Technology Center > I tried it with pre11, same problem. I modified the debug append line to the one above. I get the following output: efi_boot_linux: kernel_start 0x1000000 kernel_size 0x472390 initramfs 0x7e3dc998 setup_data 0x0 cmdline 0x9f000 efi_boot_linux: setup_sects 32 kernel_size 4662160 Hope this helps Regards Michael

...; + } else { + nv_mask(pmc, 0x00000200, 0x2000, 0x00000000); + return 0; + } +} +static void +pmu_enable_irq(struct nvkm_pmu *ppmu, struct nvkm_mc *pmc, bool enable) +{ + if (enable) { + nv_debug(ppmu, "enable pmu irq\n"); + nv_wr32(ppmu, 0x0010a010, 0xff); + nv_mask(pmc, 0x00000640, 0x1000000, 0x1000000); + nv_mask(pmc, 0x00000644, 0x1000000, 0x1000000); + } else { + nv_debug(ppmu, "disable pmu irq\n"); + nv_mask(pmc, 0x00000640, 0x1000000, 0x00000000); + nv_mask(pmc, 0x00000644, 0x1000000, 0x00000000); + nv_wr32(ppmu, 0x0010a014, 0xff); + } + +} + +static int +pmu_idle(s...

...B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] rev 21, Mem @ 0x44000000/24, 0x46000000/25 (--) PCI: (0:15:0) S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] rev 4, Mem @ 0x10000000/26 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0...