search for: 0x1800

HI all, I am running FreeBSD 6.0-STABLE (of today) on a HP Pavillon (centrino based notebook with i915 graphic chipset). I am trying to use the latest drm hook for i915, but I get this error: drmsub0: <Intel i915GM> port 0x1800-0x1807 mem 0xb0080000-0xb00fffff,0xc0000000-0xcfffffff,0xb0000000-0xb003ffff irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: <display> at device 2.1 (no driver attached) Any i...

...T61 laptop? I've got CentOS 5.4 on it but Xorg crashes when I try to change resolution, and Xorg.log has: (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) PCI:*(0:2:0) Intel Corporation unknown chipset (0x2a02) rev 12, Mem @ 0xf8100000/20, 0xe0000000/28, I/O @ 0x1800/3 (--) PCI: (0:2:1) Intel Corporation unknown chipset (0x2a03) rev 12, Mem @ 0xf8200000/20 I didn't find one on the vendor's website. Is there something I can do? Best, -at

...sense_ina2x9_config(struct nvkm_iccsense *iccsense, + struct nvkm_iccsense_sensor *sensor) +{ + struct nvkm_subdev *subdev = &iccsense->subdev; + /* configuration: + * 0x0007: 0x0007 shunt and bus continous + * 0x0078: 0x0078 128 samples shunt + * 0x0780: 0x0780 128 samples bus + * 0x1800: 0x0000 +-40 mV shunt range + * 0x2000: 0x0000 16V FSR + */ + u16 value = 0x07ff; + nvkm_debug(subdev, "config for sensor id %i: 0x%x\n", sensor->id, value); + nv_wr16i2cr(sensor->i2c, sensor->addr, 0x00, value); +} + +static void +nvkm_iccsense_ina3221_config(struct nvk...

...og, could somebody help me sort this out, please, or at least point me in the right direction? I do see this: (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) PCI:*(0:2:0) Intel Corporation unknown chipset (0x2a02) rev 12, Mem @ 0xf8100000/20, 0xe0000000/28, I/O @ 0x1800/3 (--) PCI: (0:2:1) Intel Corporation unknown chipset (0x2a03) rev 12, Mem @ 0xf8200000/20 Do I need a special video driver? I checked http://www.linlap.com/wiki/ibm-lenovo+thinkpad+t61 which says this laptop should work OK with recent Linux distros; and I tried the xorg.conf mod in http://www.th...

...---------------- sector decimal hex 0 - 0 - 0x0 1 - 512 - 0x200 2 - 1024 - 0x400 3 - 1536 - 0x600 4 - 2048 - 0x800 5 - 2560 - 0xa00 6 - 3072 - 0xc00 7 - 3584 - 0xe00 8 - 4096 - 0x1000 ... 12- 6144 - 0x1800 FSINFO sectors basically store one or two numbers (they left room to grow, I guess). It stores the cached number of clusters in use, and the last free cluster (IIRC). You can set them both to 0xFFFF, and they will be regenerated on bootup. Extended Bios Parameter Block (EBPB) starts on byte 12 (d...

...sense_ina209_config(struct nvkm_iccsense *iccsense, - struct nvkm_iccsense_sensor *sensor) -{ - struct nvkm_subdev *subdev = &iccsense->subdev; - /* configuration: - * 0x0007: 0x0007 shunt and bus continous - * 0x0078: 0x0078 128 samples shunt - * 0x0780: 0x0780 128 samples bus - * 0x1800: 0x0000 +-40 mV shunt range - * 0x2000: 0x0000 16V FSR - */ - u16 value = 0x07ff; - nvkm_debug(subdev, "config for sensor id %i: 0x%x\n", sensor->id, value); - nv_wr16i2cr(sensor->i2c, sensor->addr, 0x00, value); -} - -static void -nvkm_iccsense_ina3221_config(struct nvk...

...quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1208-0x120b on acpi0 cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 fxp0: <Intel 82559 Pro/100 Ethernet> port 0x1800-0x183f mem 0xf4001000-0xf4001fff,0xf4100000-0xf41fffff irq 17 at device 3.0 on pci0 miibus0: <MII bus> on fxp0 inphy0: <i82555 10/100 media interface> on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:3a:97:a5 fxp1: <Intel 82559...

...hostb0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem 0xd8000000-0xdfffffff,0xd0100000-0xd010ffff irq 11 at device 0.0 on pci1 uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0x1800-0x181f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0 usb0: USB revision 1.0 uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: <...

The power sensors can be configured to sample the readout values over time. Nvidia does this too, so nouveau should probably do that too. Karol Herbst (4): iccsense: remove read function iccsense: convert to linked list iccsense: split sensor into own struct iccsense: configure sensors like nvidia does drm/nouveau/include/nvkm/subdev/iccsense.h | 6 +- drm/nouveau/nouveau_hwmon.c

The power sensors can be configured to sample the readout values over time. Nvidia does this too, so nouveau should probably do that too. v2: use list_del and rework an error message Karol Herbst (4): iccsense: remove read function iccsense: convert to linked list iccsense: split sensor into own struct iccsense: configure sensors like nvidia does

So a new thinkpad: 01:00.0 VGA compatible controller: NVIDIA Corporation GP107GLM [Quadro P2000 Mobile] (rev a1) Hangs whenever I try to poke at the card. It starts happily enough with [ 3.971515] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20181003/nsarguments-66) [ 3.971553] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4

Second version of this patchset. Not many changes since first version - I hope this means the changes are not too controversial. Changes since v1: - Removed lookup for previous FW files in "nouveau/" - Went back to using request_firmware() since we only try to load one file Original cover letter follows: GM20B is the GPU of the upcoming Tegra X1 SoC. This series adds initial support

Hello everyone, GM20B is the GPU of the upcoming Tegra X1 SoC. This series adds initial support for it, based on a rework of the already-supported GK20A. It also introduces support for NVIDIA-provided firmware files, which is why I have added a few NVIDIA people who are relevant to this discussion. The first patch adds support for loading the FECS and GPCCS firmwares from firmware files

...w] [ 0.194847] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) [ 0.194938] pnp 00:01: [io 0x1000-0x107f] [ 0.194941] pnp 00:01: [io 0x1080-0x10ff] [ 0.194944] pnp 00:01: [io 0x1400-0x147f] [ 0.194948] pnp 00:01: [io 0x1480-0x14ff] [ 0.194951] pnp 00:01: [io 0x1800-0x187f] [ 0.194953] pnp 00:01: [io 0x1880-0x18ff] [ 0.194956] pnp 00:01: [mem 0xfefe0000-0xfefe01ff] [ 0.194959] pnp 00:01: [mem 0xfefe1000-0xfefe10ff] [ 0.194961] pnp 00:01: [mem 0x7c000000-0x7fffffff] [ 0.195034] system 00:01: [io 0x1000-0x107f] has been reserved [ 0.195038] s...

...vs0 mvsch7: <Marvell SATA channel> at channel 7 on mvs0 pci0: <base peripheral> at device 15.0 (no driver attached) pcib10: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0 pci10: <ACPI PCI bus> on pcib10 uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x1800-0x181f irq 20 at device 29.0 on pci0 usbus0 on uhci0 uhci1: <Intel 631XESB/632XESB/3100 USB controller USB-2> port 0x1820-0x183f irq 21 at device 29.1 on pci0 usbus1 on uhci1 uhci2: <Intel 631XESB/632XESB/3100 USB controller USB-3> port 0x1840-0x185f irq 22 at device 29.2 on pci0 usbus2...

...-compatible display> port 0x1000-0x10ff mem 0xe8000000-0xefffffff,0xf7ff0000-0xf7ffffff irq 44 at device 3.0 on pci0 pci0: <base peripheral> at device 4.0 (no driver attached) pci0: <base peripheral> at device 4.2 (no driver attached) uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 45 at device 4.4 on pci0 usbus0 on uhci0 pci0: <serial bus> at device 4.6 (no driver attached) pcib1: <ACPI PCI-PCI bridge> at device 5.0 on pci0 pci1: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci1 pci2: <ACPI PCI bus> on pcib2...

...) { If ((Arg1 == One)) { Local0 = GIVD /* \_SB_.PCI0.GFX0.GIVD */ Local0 ^= One Local0 |= (GMFN << One) Local0 |= 0x1800 Local0 |= (IDMS << 0x11) Local0 |= (DerefOf (DerefOf (CDCT [HVCO]) [CDVL]) << 0x15) Return (Local0) } } Ca...

This patchset applies some minor fixes to renouveau.xml and then unifies the nv30 and nv40 register definitions. nv30 and nv40 are very similar and have the same offsets for the registers they share. The major differences are: 1. Texture setup is different due to full NPOT support on nv40 2. More advanced blending/render targets on nv40 3. NV30 has fixed function registers, which NV40 lacks The

Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_drv.h | 23 +++++ drivers/gpu/drm/nouveau/nouveau_reg.h | 16 ++-- drivers/gpu/drm/nouveau/nouveau_state.c | 8 ++ drivers/gpu/drm/nouveau/nv10_fb.c | 32 ++++++-- drivers/gpu/drm/nouveau/nv10_graph.c | 47 ++++++++--- drivers/gpu/drm/nouveau/nv20_graph.c | 80

...has been reserved [ 0.298005] system 00:02: [io 0x0680-0x069f] has been reserved [ 0.298075] system 00:02: [io 0xffff] has been reserved [ 0.298145] system 00:02: [io 0xffff] has been reserved [ 0.298214] system 00:02: [io 0xffff] has been reserved [ 0.298284] system 00:02: [io 0x1800-0x18fe] could not be reserved [ 0.298355] system 00:02: [io 0x164e-0x164f] has been reserved [ 0.298425] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.298474] system 00:03: [io 0x0800-0x087f] has been reserved [ 0.298555] system 00:03: Plug and Play ACPI device, ID...