search for: 0x000000

..._boot_1 != 0x01000001) + return !big_endian; /* Assume GPU is LE in this case. */ + + /* 0 means LE and 0x01000001 means BE GPU. Condition is true when + * GPU/CPU endianness don't match. + */ + if (big_endian == !pmc_boot_1) { + nvkm_wr32(device, 0x000004, 0x01000001); + nvkm_rd32(device, 0x000000); + if (nvkm_rd32(device, 0x000004) != (big_endian ? 0x01000001 : 0x00000000)) + return !big_endian; /* Assume GPU is LE on any unexpected read-back. */ + } + + /* CPU/GPU endianness should (hopefully) match. */ return true; } @@ -2987,14 +3004,10 @@ nvkm_device_ctor(const struct nvkm_devic...

...0: Elf file type is EXEC (Executable file) Entry point 0x80002670 There are 3 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x000034 0x7ffff034 0x7ffff034 0x00060 0x00060 R 0x4 LOAD 0x000000 0x7ffff000 0x7ffff000 0x0a098 0x0a098 RWE 0x1000 GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x0 Section to Segment mapping: Segment Sections... 00 01 .text .rodata .data 02 From what I understand if a linker script is used and the headers fail to allocate...

...t; + > + /* 0 means LE and 0x01000001 means BE GPU. Condition is true when > + * GPU/CPU endianness don't match. > + */ > + if (big_endian == !pmc_boot_1) { > + nvkm_wr32(device, 0x000004, 0x01000001); > + nvkm_rd32(device, 0x000000); > + if (nvkm_rd32(device, 0x000004) != (big_endian ? 0x01000001 : 0x00000000)) > + return !big_endian; /* Assume GPU is LE on any unexpected read-back. */ > + } > + > + /* CPU/GPU endianness should (hopefully) match. */ > r...

...4f4920b9b829f922 "execve: warn if process starts with executable stack" objdump -x shows: /usr/lib/klibc/bin/sh: file format elf32-powerpc /usr/lib/klibc/bin/sh architecture: powerpc:common, flags 0x00000102: EXEC_P, D_PAGED start address 0x10000140 Program Header: PHDR off 0x00000034 vaddr 0x10000034 paddr 0x10000034 align 2**2 filesz 0x000000a0 memsz 0x000000a0 flags r-x INTERP off 0x000000d4 vaddr 0x100000d4 paddr 0x100000d4 align 2**0 filesz 0x0000002a memsz 0x0000002a flags r-- LOAD off 0x00000000 vaddr 0x10000000 paddr 0x10000000 align 2...

...a/drivers/gpu/drm/nouveau/nvkm/engine/disp/gv100.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/disp/gv100.c @@ -587,7 +587,7 @@ gv100_disp_curs = { .user = 73, }; -const struct nvkm_disp_mthd_list +static const struct nvkm_disp_mthd_list gv100_disp_core_mthd_base = { .mthd = 0x0000, .addr = 0x000000, -- 2.25.1

...vdev_error(device, "unable to map PRI\n"); + ret = -ENOMEM; goto done; + } + } + /* identify the chipset, and determine classes of subdev/engines */ + if (detect) { /* switch mmio to cpu's native endianness */ #ifndef __BIG_ENDIAN if (ioread32_native(map + 0x000004) != 0x00000000) { @@ -2980,7 +2985,6 @@ nvkm_device_ctor(const struct nvkm_device_func *func, /* read boot0 and strapping information */ boot0 = ioread32_native(map + 0x000000); strap = ioread32_native(map + 0x101000); - iounmap(map); /* chipset can be overridden for devel/testing purposes */...

...e system locks for a second (cursor locks up, etc) and then either returns to normal for a second before crashing or just crashes when we start moving again (the former happens more often when making things bigger, the latter when the console is shrunk). The error message reports an attempt to read 0x000000 so I'm guessing the problem is somewhere in the Rgui console's memory management code. I can duplicate this on both my home and lab desktop machines as well as my laptop. All are running Win2K Server (I take that back--- my lab machine is running Pro. edition) and all are reasonably update...

Add a simple test which uses scanelf or readelf to detect whether the supermin executable is really not executable. Kind of followup of commit c9f7a7998021e1cbe22a8ec325d43e2bdc3eff5a. --- tests/Makefile.am | 1 + tests/test-execstack.sh | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+) create mode 100755 tests/test-execstack.sh diff --git a/tests/Makefile.am

...000:00/0000:00:03.0/virtio0': KERNELS=="virtio0" SUBSYSTEMS=="virtio" DRIVERS=="virtio_scsi" ATTRS{device}=="0x0008" ATTRS{features}=="0110000000000000000000000000010000000000000000000000000000000000" ATTRS{status}=="0x00000007" ATTRS{vendor}=="0x1af4" looking at parent device '/devices/pci0000:00/0000:00:03.0': KERNELS=="0000:00:03.0" SUBSYSTEMS=="pci" DRIVERS=="virtio-pci" ATTRS{irq}=="11" ATTRS{subsystem_vendor}=="0x1af4&qu...

...mp; madeup < shortfall) { bar.width = bar.width + 1; @@ -295,14 +345,15 @@ package org.ovirt.charts { //add a 'tick' in the center of the bar to which this label //corresponds var ind:Box = new Box(); - ind.opaqueBackground = 0x000000; - ind.width=1; - ind.height=3; + ind.width=2; + ind.height=4; ind.x = label.getCenter(); ind.y = 0; ind.setVisible(true); - ind.setStyle("backgroundColor","0x000000"); + ind...

I re-wrote the compile script to build klibc (cleaning up how I do it, and how to find the source tarballs). It seems to be compiling fine. I tried several of the commands in usr/utils/static and most one. However, the sleep command fails in a strange way (EINVAL on execve): ================================================================ faraday/phil /home/phil/klibc-project-0 581> strace

...rivers/gpu/drm/nouveau/nvkm/engine/disp/coregv100.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/disp/coregv100.c @@ -23,7 +23,7 @@ #include <subdev/timer.h> -const struct nv50_disp_mthd_list +static const struct nv50_disp_mthd_list gv100_disp_core_mthd_base = { .mthd = 0x0000, .addr = 0x000000, @@ -39,7 +39,7 @@ gv100_disp_core_mthd_base = { } }; -const struct nv50_disp_mthd_list +static const struct nv50_disp_mthd_list gv100_disp_core_mthd_sor = { .mthd = 0x0020, .addr = 0x000020, -- 2.23.0

...x/change the HID parser (see libhid project) */ if (strstr(path, "000000") != NULL) { continue; } Would there be anything against skipping these reports while parsing the report descriptor, instead of ignoring them in HIDDumpTree()? In theory, this might break subdrivers where the nodes 0x000000??, 0x?000000? and 0x??000000 are used, but so far I have not seen any that does (if it is allowed at all). For the moment, I think skipping reports that end in node 0x00000000 (0) is sufficient. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E...

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

...truct nvkm_bios *bios, u16 offset, + u8 ramcfg) +{ + nvkm_memx_init_run(ram->memx, bios, offset, ramcfg); +} + #define ram_init(s,p) ramfuc_init(&(s)->base, (p)) #define ram_exec(s,e) ramfuc_exec(&(s)->base, (e)) #define ram_have(s,r) ((s)->r_##r.addr != 0x000000) @@ -174,4 +181,5 @@ ramfuc_unblock(struct ramfuc *ram) #define ram_train_result(s,r,l) ramfuc_train_result((s), (r), (l)) #define ram_block(s) ramfuc_block(&(s)->base) #define ram_unblock(s) ramfuc_unblock(&(s)->base) +#define ram_init_run(s,b,o,r) ramfuc_init_run(&a...

...16) Allocating 16 x 16 radeon RBO (pitch 16) Allocating 16 x 16 radeon RBO (pitch 16) Allocating 16 x 16 radeon RBO (pitch 16) Allocating 16 x 16 radeon RBO (pitch 16) Allocating 16 x 16 radeon RBO (pitch 16) Allocating 16 x 16 radeon RBO (pitch 16) fixme:win:EnumDisplayDevicesW ((null),0,0x32f370,0x00000000), stub! fixme:shdocvw:ViewObject_SetAdvise (0x19dfe8)->(1 00000002 0x123b0a8) fixme:shdocvw:PersistStreamInit_InitNew (0x19dfe8) fixme:shdocvw:WebBrowser_put_RegisterAsBrowser (0x19dfe8)->(ffffffff) fixme:shdocvw:WebBrowser_put_RegisterAsDropTarget (0x19dfe8)->(ffffffff) fixme:dsalsa:IDs...

...ce b/test/trace/loadvars-decode-5.swf.trace index 5ee0305..a3fde32 100644 --- a/test/trace/loadvars-decode-5.swf.trace +++ b/test/trace/loadvars-decode-5.swf.trace @@ -21,3 +21,185 @@ a = c = d = e decode = +>>> id=mplayer&javascriptid=mplayer&frontcolor=0xFFFFFF&backcolor=0x000000&enablejs=true&largecontrols=false&file=http://kanal5.se/c/ext/k5video/playlist?selectType=playlist-name%26selectWord=Mazda%26selectType2=playlist-name%26selectWord2=Fraga Olle 1107&bufferlength=6&displayheight=168&height=168&width=225&autostart=false&repeat=list&...

...+} + +static inline void +ramfuc_fb_enable(struct ramfuc *ram) +{ + nouveau_memx_fb_enable(ram->memx); +} + #define ram_init(s,p) ramfuc_init(&(s)->base, (p)) #define ram_exec(s,e) ramfuc_exec(&(s)->base, (e)) #define ram_have(s,r) ((s)->r_##r.addr[0] != 0x000000) @@ -121,5 +133,7 @@ ramfuc_wait_vblank(struct ramfuc *ram) #define ram_wait(s,r,m,d,n) ramfuc_wait(&(s)->base, (r), (m), (d), (n)) #define ram_nsec(s,n) ramfuc_nsec(&(s)->base, (n)) #define ram_wait_vblank(s) ramfuc_wait_vblank(&(s)->base) +#define ram_fb_disable(...

Patch 1 fixes nva3 bailing due to not finding the right ramcfg Patch 2 is a resend rebased on 3.17.0-rc4 for setting the vblank period Patch 3-5 handle writes to per-partition registers, for which NVA3 does not have special broadcast regs available. Patch 6 removes local structs from NVA3 reclocking in favour of the already existing "ram->base." variables, like in NVE0 As always,