search for: 0x300000

...om signature, with a workaround for a PROM reading * issue on some chipsets. the first read after a period of * inactivity returns the wrong result, so retry the first header @@ -164,31 +168,38 @@ nouveau_bios_shadow_prom(struct nouveau_bios *bios) */ i = 16; do { - if (nv_rd08(bios, 0x300000) == 0x55) + if ((nv_rd32(bios, 0x300000) & 0xffff) == 0xaa55) break; } while (i--); - if (!i || nv_rd08(bios, 0x300001) != 0xaa) + if (!i) goto out; - /* additional check (see note below) - read PCI record header */ - pcir = nv_rd08(bios, 0x300018) | - nv_rd08(bios, 0x30001...

...me chipsets. the first read after a period of > * inactivity returns the wrong result, so retry the first header > @@ -164,31 +168,38 @@ nouveau_bios_shadow_prom(struct nouveau_bios *bios) > */ > i = 16; > do { > - if (nv_rd08(bios, 0x300000) == 0x55) > + if ((nv_rd32(bios, 0x300000) & 0xffff) == 0xaa55) > break; > } while (i--); > > - if (!i || nv_rd08(bios, 0x300001) != 0xaa) > + if (!i) > goto out; > > - /* additional check...

...ios/base.c +++ b/nvkm/subdev/bios/base.c @@ -183,10 +183,11 @@ nouveau_bios_shadow_prom(struct nouveau_bios *bios) goto out; bios->data = kmalloc(bios->size, GFP_KERNEL); - if (bios->data) { - for (i = 0; i < bios->size; i += 4) - ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 + i); - } + if (!bios->data) + goto out; + + for (i = 0; i < bios->size; i += 4) + ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 + i); /* check the PCI record header */ pcir = nv_ro16(bios, 0x0018); -- 1.9.1

...ios) >> goto out; >> >> bios->data = kmalloc(bios->size, GFP_KERNEL); >> - if (bios->data) { >> - for (i = 0; i < bios->size; i += 4) >> - ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 >> + i); >> - } >> + if (!bios->data) >> + goto out; >> + >> + for (i = 0; i < bios->size; i += 4) >> + ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 + i); >> >> /* check the...

...ase.c > @@ -183,10 +183,11 @@ nouveau_bios_shadow_prom(struct nouveau_bios *bios) > goto out; > > bios->data = kmalloc(bios->size, GFP_KERNEL); > - if (bios->data) { > - for (i = 0; i < bios->size; i += 4) > - ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 + i); > - } > + if (!bios->data) > + goto out; > + > + for (i = 0; i < bios->size; i += 4) > + ((u32 *)bios->data)[i/4] = nv_rd32(bios, 0x300000 + i); > > /* check the PCI record header */ > pcir = nv_ro16(bios, 0x0018); > This patch never got revi...

....997918] nouveau [ PTHERM][0000:01:00.0] FAN control: none / external [ 1.997926] nouveau [ PTHERM][0000:01:00.0] fan management: disabled [ 1.997979] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes [ 2.032309] nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x300000 [ IBUS ] [ 2.032962] nouveau [ DRM] VRAM: 2048 MiB [ 2.032966] nouveau [ DRM] GART: 1048576 MiB [ 2.032972] nouveau E[ DRM] Pointer to TMDS table invalid [ 2.033016] nouveau [ DRM] DCB version 4.0 [ 2.033019] nouveau E[ DRM] Pointer to flat panel table invalid...

...;subdev.device, 0x8c1c0) & 0x4) == 0x4 ? 2 : 1; @@ -108,7 +108,7 @@ gk104_pcie_lnkctl_speed(struct nvkm_pci *pci) return -1; } -static enum nvkm_pcie_speed +enum nvkm_pcie_speed gk104_pcie_max_speed(struct nvkm_pci *pci) { u32 max_speed = nvkm_rd32(pci->subdev.device, 0x8c1c0) & 0x300000; @@ -146,7 +146,7 @@ gk104_pcie_set_link_speed(struct nvkm_pci *pci, enum nvkm_pcie_speed speed) nvkm_mask(device, 0x8c040, 0x1, 0x1); } -static int +int gk104_pcie_init(struct nvkm_pci * pci) { enum nvkm_pcie_speed lnkctl_speed, max_speed, cap_speed; @@ -178,7 +178,7 @@ gk104_pcie_init(st...

...went into another computer, 'ssh'ed into that one, and typed 'dmesg'. The last important lines are these: application Picasa2 uses obsolete OSS audio interface [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 3123 emitted: 3125 mtrr: base(0x80020000) is not aligned on a size(0x300000) boundary (this last line kept repeating many times) 'top' showed almost 100% for process X, that disappeared and appeared again with a different PID. It seems that X got killed for some reason, and xdm was trying to start up again, but got killed every time with that mtrr error. My video...

...;subdev.device, 0x8c1c0) & 0x4) == 0x4 ? 2 : 1; @@ -108,7 +108,7 @@ gk104_pcie_lnkctl_speed(struct nvkm_pci *pci) return -1; } -static enum nvkm_pcie_speed +enum nvkm_pcie_speed gk104_pcie_max_speed(struct nvkm_pci *pci) { u32 max_speed = nvkm_rd32(pci->subdev.device, 0x8c1c0) & 0x300000; @@ -146,7 +146,7 @@ gk104_pcie_set_link_speed(struct nvkm_pci *pci, enum nvkm_pcie_speed speed) nvkm_mask(device, 0x8c040, 0x1, 0x1); } -static int +int gk104_pcie_init(struct nvkm_pci * pci) { enum nvkm_pcie_speed lnkctl_speed, max_speed, cap_speed; @@ -178,7 +178,7 @@ gk104_pcie_init(st...

...;subdev.device, 0x8c1c0) & 0x4) == 0x4 ? 2 : 1; @@ -110,7 +110,7 @@ gk104_pcie_lnkctl_speed(struct nvkm_pci *pci) return -1; } -static enum nvkm_pcie_speed +enum nvkm_pcie_speed gk104_pcie_max_speed(struct nvkm_pci *pci) { u32 max_speed = nvkm_rd32(pci->subdev.device, 0x8c1c0) & 0x300000; @@ -156,7 +156,7 @@ gk104_pcie_set_link_speed(struct nvkm_pci *pci, enum nvkm_pcie_speed speed) return 0; } -static int +int gk104_pcie_init(struct nvkm_pci * pci) { enum nvkm_pcie_speed lnkctl_speed, max_speed, cap_speed; @@ -188,7 +188,7 @@ gk104_pcie_init(struct nvkm_pci * pci) retur...

...;subdev.device, 0x8c1c0) & 0x4) == 0x4 ? 2 : 1; @@ -108,7 +108,7 @@ gk104_pcie_lnkctl_speed(struct nvkm_pci *pci) return -1; } -static enum nvkm_pcie_speed +enum nvkm_pcie_speed gk104_pcie_max_speed(struct nvkm_pci *pci) { u32 max_speed = nvkm_rd32(pci->subdev.device, 0x8c1c0) & 0x300000; @@ -146,7 +146,7 @@ gk104_pcie_set_link_speed(struct nvkm_pci *pci, enum nvkm_pcie_speed speed) nvkm_mask(device, 0x8c040, 0x1, 0x1); } -static int +int gk104_pcie_init(struct nvkm_pci * pci) { enum nvkm_pcie_speed lnkctl_speed, max_speed, cap_speed; @@ -178,7 +178,7 @@ gk104_pcie_init(st...

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem with large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k

....997918] nouveau [ PTHERM][0000:01:00.0] FAN control: none / external [ 1.997926] nouveau [ PTHERM][0000:01:00.0] fan management: disabled [ 1.997979] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes [ 2.032309] nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x300000 [ IBUS ] [ 2.032962] nouveau [ DRM] VRAM: 2048 MiB [ 2.032966] nouveau [ DRM] GART: 1048576 MiB [ 2.032972] nouveau E[ DRM] Pointer to TMDS table invalid [ 2.033016] nouveau [ DRM] DCB version 4.0 [ 2.033019] nouveau E[ DRM] Pointer to flat panel table invalid...

.... EXAMPLE 2 > > Example, Freescale crypto device (modified to illustrate): > > crypto at 300000 { > compatible = "fsl,sec-v4.2", "fsl,sec-v4.0"; > #address-cells = <0x1>; > #size-cells = <0x1>; > reg = <0x300000 0x10000>; > interrupts = <0x5c 0x2 0x0 0x0>; > > jr at 1000 { > compatible = "fsl,sec-v4.2-job-ring", "fsl,sec-v4.0-job-ring"; > interrupts = <0x58 0x2 0x0 0x0>; > }; > > jr at 2000 { >...

...ffe000000/sata at 220000" 6. EXAMPLE 2 Example, Freescale crypto device (modified to illustrate): crypto at 300000 { compatible = "fsl,sec-v4.2", "fsl,sec-v4.0"; #address-cells = <0x1>; #size-cells = <0x1>; reg = <0x300000 0x10000>; interrupts = <0x5c 0x2 0x0 0x0>; jr at 1000 { compatible = "fsl,sec-v4.2-job-ring", "fsl,sec-v4.0-job-ring"; interrupts = <0x58 0x2 0x0 0x0>; }; jr at 2000 { compatible = "fsl,se...

...ffe000000/sata at 220000" 6. EXAMPLE 2 Example, Freescale crypto device (modified to illustrate): crypto at 300000 { compatible = "fsl,sec-v4.2", "fsl,sec-v4.0"; #address-cells = <0x1>; #size-cells = <0x1>; reg = <0x300000 0x10000>; interrupts = <0x5c 0x2 0x0 0x0>; jr at 1000 { compatible = "fsl,sec-v4.2-job-ring", "fsl,sec-v4.0-job-ring"; interrupts = <0x58 0x2 0x0 0x0>; }; jr at 2000 { compatible = "fsl,se...

While investigating the runpm issues on my GP107 I noticed that something inside devinit makes runpm break. If Nouveau loads up to the point right before doing devinit, runpm works without any issues, if devinit is ran, not anymore. Out of curiousity I even tried to "bisect" devinit by not running it on vbios provided signed PMU image, but on the devinit parser we have inside Nouveau.

not much changed since the last time I sent those patches out, but there are a couple of annoying bug fixes, which users would probably never hit unless they do rmmod/modprobe nouveau cycles. Biggest change is that I force the link to a 8.0 speed rather than the speed the GPU came up with. Also this series depends on the PCIe improvement patches I sent out recently. Karol Herbst (4): pci:

...MPLE 2 > > Example, Freescale crypto device (modified to illustrate): > > crypto at 300000 { > compatible = "fsl,sec-v4.2", "fsl,sec-v4.0"; > #address-cells = <0x1>; > #size-cells = <0x1>; > reg = <0x300000 0x10000>; > interrupts = <0x5c 0x2 0x0 0x0>; > > jr at 1000 { > compatible = "fsl,sec-v4.2-job-ring", "fsl,sec-v4.0-job-ring"; > interrupts = <0x58 0x2 0x0 0x0>; > }; > > jr at 200...