search for: parse_init_table

http://bugs.freedesktop.org/show_bug.cgi?id=14597 Summary: randr12 failures on 12" powerbooks, and workarounds Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...ght_sleep(); + if (usecs < 1000 * MAX_UDELAY_MS) + udelay(usecs); + else + msleep(usecs / 1000 + 1); +} + static bool nv_cksum(const uint8_t *data, unsigned int length) { /* there's a few checksums in the BIOS, so here's a generic checking function */ @@ -262,7 +269,7 @@ static int parse_init_table(struct nvbios *, unsigned int, struct init_exec *); static void still_alive(void) { // sync(); -// BIOS_USLEEP(2000); +// bios_usleep(2000); } static uint32_t @@ -1608,17 +1615,18 @@ init_condition_time(struct nvbios *bios, uint16_t offset, for (; retries > 0; retries--) if (bios_c...

...all the code is allowed to execute (no comments) and 0x32 is changed to 0x72. THEN, to change that 0x72 back to 0x32, and add nv32_wr(pScrn, 0x006828b4, 0x72); nv32_wr(pScrn, 0x006828b0, 0x02); on the end of the unrolled script as a fix-up, and check that works. Assuming that's ok, calling parse_init_table, then calling that same fix-up code ought be have exactly the same result, and these two writes can be added as a ppc specific quirk. Hopefully this all makes sense to you ppc people, but if I'm being incoherent please say and I'll code up a set of numbered patches of what I want testing :...

...y()) path? > > >> > static bool nv_cksum(const uint8_t *data, unsigned int > >> > length) { > >> > /* there's a few checksums in the BIOS, so here's a > >> > generic checking function */ @@ -262,7 +269,7 @@ static int > >> > parse_init_table(struct nvbios *, unsigned int, struct > >> > init_exec *); static void still_alive(void) { > >> > // sync(); > >> > -// BIOS_USLEEP(2000); > >> > +// bios_usleep(2000); > >> > } > >> > > >> > static uint32_t &g...

...bc 00000000 eea547a0 Call Trace: [<c1192fd0>] ? notify_update+0x22/0x24 [<c1022380>] io_reserve_memtype+0x6a/0xf2 [<c1041bed>] ? __cond_resched+0x16/0x26 [<c1023493>] iomap_create_wc+0x18/0x2b [<f0e5452b>] init_compute_mem+0x1e5/0x9c4 [nouveau] [<f0e52d70>] parse_init_table+0xcd/0x189 [nouveau] [<f0e57cc3>] nouveau_run_vbios_init+0x1fb/0x2a9 [nouveau] [<f0e58a6b>] nouveau_bios_init+0xcfa/0x102c [nouveau] [<c101fed6>] ? vmalloc_sync_all+0x116/0x116 [<c125152a>] ? error_code+0x5a/0x60 [<f0e3f630>] ? nouveau_stub_init+0x7/0x7 [nouveau]...

--- drivers/gpu/drm/nouveau/nouveau_bios.c | 47 ++++++++++++++----------------- 1 files changed, 21 insertions(+), 26 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c b/drivers/gpu/drm/nouveau/nouveau_bios.c index 5eec5ed..04ac564 100644 --- a/drivers/gpu/drm/nouveau/nouveau_bios.c +++ b/drivers/gpu/drm/nouveau/nouveau_bios.c @@ -181,43 +181,42 @@ struct methods { const char

It seems it was only locking up in the context of nouveau_hw_save_vga_fonts, when it actually did something (because the console wasn't already in graphics mode). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_hw.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_hw.c

This patch series adds TV-out modesetting support to the KMS implementation. I've tried to test it on all the hardware I've got at hand (that is nv11, nv17, nv34, nv35, nv40, nv4b) with every possible output combination; I believe it has reached a mergeable state, however it depends on some commits from drm-next that haven't got into Linus' tree yet, if you agree to merge this