search for: regoffset

..._CIO_CRE_PIXEL_INDEX, @@ -258,7 +258,7 @@ nv_nv17_load_detect(ScrnInfoPtr pScrn, struct nouveau_encoder *nv_encoder) nvWriteMC(pNv, NV_PBUS_POWERCTRL_4, saved_powerctrl_4 & 0xffffffcf); } - usleep(4000); + nouveau_usleep(4000); saved_routput = NVReadRAMDAC(pNv, 0, NV_PRAMDAC_DACCLK + regoffset); head = (saved_routput & 0x100) >> 8; @@ -269,7 +269,7 @@ nv_nv17_load_detect(ScrnInfoPtr pScrn, struct nouveau_encoder *nv_encoder) /* nv driver and nv31 use 0xfffffeee, nv34 and 6600 use 0xfffffece */ NVWriteRAMDAC(pNv, 0, NV_PRAMDAC_DACCLK + regoffset, (saved_routput &a...

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

...ts should accept and ignore any tag names or tag modifiers they do not understand, allowing the annotations to grow in richness without breaking older clients. For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a literal '<' character is output as '<<' in...

...nd ignore any tag names or tag modifiers they do not understand, allowing the annotations to grow in richness without breaking older clients. > > For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: > > ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> > > > 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a literal '<' character is output as '&lt...

Hello, Talking with Soren Sratje about Caller ID in Brazil, we compare ours DTMF tones captured by ztmonitor. wcfxo correctly recognize the "DTMF CLIP" and asterisk shot the AST_STATE_PRERING correctly. But the DTMF tones are not reconized. In the chan_zap.c, the code: if (f->frametype == AST_FRAME_DTMF) { (...) Does not occurs because the frametype is always reconized as voice

...names or tag modifiers they do not understand, allowing the annotations to grow in richness without breaking older clients. >> >> For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: >> >> ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> >> >> >> 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a literal '<' character is outp...

...not understand, allowing the annotations to grow in richness without breaking older clients. >>>> >>>> For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: >>>> >>>> ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> >>>> >>>> >>>> 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a literal '&lt...

...modifiers they do not understand, allowing the annotations to grow in richness without breaking older clients. >>> >>> For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: >>> >>> ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> >>> >>> >>> 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a literal '<' charact...

...d, allowing the annotations to grow in richness without breaking older clients. >>>>> >>>>> For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: >>>>> >>>>> ldr <reg gpr:r0>, <mem regoffset:[<reg gpr:sp>, <imm:#4>]> >>>>> >>>>> >>>>> 1: For assembly dialects in which '<' and/or '>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example, a litera...

...annotations to grow in richness without breaking older clients. >>>>>> >>>>>> For example, a possible annotation of an ARM load of a stack-relative location might be annotated as: >>>>>> >>>>>> ldr<reg gpr:r0>,<mem regoffset:[<reg gpr:sp>,<imm:#4>]> >>>>>> >>>>>> >>>>>> 1: For assembly dialects in which '<' and/or'>' are legal tokens, a literal token is escaped by following immediately with a repeat of the character. For example...