search for: txc

...t. By fiddling about, I've come up with the "almost working" configuration below. This works except that it takes about 4 seconds from when the console says the line is answered until it plays my prompt. Watching the card with zttool, all flags start at 0. Then RxA, RxB, TxA, TxB, TxC, TxD change to 1. Then, a split second later, TxA, TxB, TxC, and TxD change to 0. A couple of seconds later, TxA, TxB, TxC, TxD change to 1 and the call progresses. What does this mean? Can you identify the proper configuration from this "handshake?" Verbosity is at least 99 -- S...

...ium/drivers/nouveau/nvc0/nvc0_screen.c > index d435bec..820e38d 100644 > --- a/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c > +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c > @@ -991,6 +991,14 @@ nvc0_screen_create(struct nouveau_device *dev) > PUSH_DATAh(push, screen->txc->offset); > PUSH_DATA (push, screen->txc->offset); > PUSH_DATA (push, NVC0_TIC_MAX_ENTRIES - 1); > + if (screen->eng3d->oclass >= GM107_3D_CLASS) { > + screen->tic.maxwell = true; > + if (screen->eng3d->oclass == GM107_3D_CLASS) { > +...

I'm passing this on to the flac-dev list... --- Igor Schein <igor@txc.com> wrote: > Date: Tue, 11 Jun 2002 16:20:15 -0400 > From: Igor Schein <igor@txc.com> > To: Josh Coalson <xflac@yahoo.com> > Subject: Re: [Flac-dev] flac-1.0.3_beta released > > On Tue, Jun 11, 2002 at 10:04:25AM -0700, Josh Coalson wrote: > > One more thing...

...111111122222 ???????? ? ? ? ? ? 123456789012345678901234 ? Back ? ? ? ? ? ? TxA 000000000000000000000000 ???????? ? ? ? ? ? TxB 000000000000000000000000 ? ? ? ? ? TxC 000000000000000000000000 ? # ? ? ? TxD 000000000000000000000000 ? ? ? ? ???????? ? ? ? ? RxA 000000000000000000000000 ? Loop ? ? ?...

Hi, I am using samba-3.0.4 with ldap. Everything is working except the command net user. That command does not display domain users. For the same reason I can see only domain groups but not users in Windows 2000 Select Users or Groups window while adding domain user to local Administrators group. The command net user info <user> displays user's group. Net groups also displays domain

.../nvc0_screen.c b/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c index d435bec..820e38d 100644 --- a/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c @@ -991,6 +991,14 @@ nvc0_screen_create(struct nouveau_device *dev) PUSH_DATAh(push, screen->txc->offset); PUSH_DATA (push, screen->txc->offset); PUSH_DATA (push, NVC0_TIC_MAX_ENTRIES - 1); + if (screen->eng3d->oclass >= GM107_3D_CLASS) { + screen->tic.maxwell = true; + if (screen->eng3d->oclass == GM107_3D_CLASS) { + screen->tic.maxwel...

Hi! I've set up a Samba PDC(3.0.4+LDAP) and attached a W2k client to it. I've created users and group. I can log on to the W2k client. Now to my problem: I wanted to add a user to the local filesystem(for testing). So I opened up the Security Tab and listed my domain. Lo and behold. No users. That strange I thought and added the user manually and hit the Check button. It worked

...nvc0/nvc0_screen.c >> index d435bec..820e38d 100644 >> --- a/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c >> +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c >> @@ -991,6 +991,14 @@ nvc0_screen_create(struct nouveau_device *dev) >> PUSH_DATAh(push, screen->txc->offset); >> PUSH_DATA (push, screen->txc->offset); >> PUSH_DATA (push, NVC0_TIC_MAX_ENTRIES - 1); >> + if (screen->eng3d->oclass >= GM107_3D_CLASS) { >> + screen->tic.maxwell = true; >> + if (screen->eng3d->oclass == GM10...

This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of

...-info.org/tiki-index.php?page=adtran What should zttool show if everything is configured properly? After doing 'modprobe wct1xxp;ztcfg' I ran zttool. In the details for the T100P I saw: "Current Alarms: Red Alarm, Sync Source: Internally Clocked" ? TxA 00000000 ? TxB 11111111 ? TxC 00000000 ? TxD 11111111 ? RxA 00000111 ? RxB 11111010 ? RxC 00000000 ? RxD 00000000 Should the transmit and receive settings be mirror images of each other, or is this display correct given my situation? Unfortunately I don't understand what a good display would look like. On another topic...

..._create(struct nouveau_device *dev) PUSH_DATA (push, 3); } - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 1 << 17, 1 << 17, NULL, + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 1 << 17, 1 << 17, NULL, &screen->txc); if (ret) goto fail; diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c b/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c index 1000d8286d77..3fcca1671c8c 100644 --- a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_sh...

...) > PUSH_DATA (push, 3); > } > > - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 1 << 17, 1 << 17, NULL, > + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 1 << 17, 1 << 17, NULL, > &screen->txc); > if (ret) > goto fail; > diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c b/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c > index 1000d8286d77..3fcca1671c8c 100644 > --- a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c > +++ b/src/gall...

...eld values as arrayref 'XAID' => $data->{article_id}, 'XTITLE' => $title, # arrayref 'XDATE' => $data->{publicationdate}, 'XTYPE' => $data->{articletype}, 'XTID' => $tid, # arrayref 'XTXC' => $txc, # arrayref }); my @words = _get_text($data,$title); for my $i (0 .. $#words) { my $w = $words[$i]; $w =~ s/[\.-]$//g; $doc->add_posting($w,++$i) if $w; } $db->add_document($doc); sub _add_attr { my ($doc,$data) = @_; for my $k (keys %$data) { if (ref $...

...e *dev) > PUSH_DATA (push, 3); > } > > - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 1 << 17, 1 << 17, NULL, > + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 1 << 17, 1 << 17, NULL, > &screen->txc); > if (ret) > goto fail; > diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c b/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c > index 1000d8286d77..3fcca1671c8c 100644 > --- a/src/gallium/drivers/nouveau/nvc0/nvc0_shader_state.c > +++ b/src/galliu...

...nt Alarms: No alarms ( Should I see OK here instead ? Is it normal > ?) > Sync Source: Internally clocked > IRQ Misses: 0 > Bipolar Viol: 0 > Tx/Rx Levels: 0/ 0 > Total/Conf/Act: 1/ 1/ 1 > > 1 > TxA - > TxB - > TxC - > TxD - > > RxA - > RxB - > RxC - > RxD - > dahdi_cfg -vv > DAHDI Tools Version - 2.2.0 > > DAHDI Version: 2.2.0.2 > Echo Canceller(s): MG2 > Configuration > ====================== > Channel map: > Channel 01: FXS Kewlstart (Default) (Echo Canceler:...

...l ==== Zapata Telephony Interfaces Alarms Span OK Wildcard X101P Board 1 Current Alarms: No alarms. Sync Source: Internally clocked IRQ Misses: 0 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 1/ 1/ 1 1 TxA - TxB - TxC - TxD - RxA - RxB - RxC - RxD - ztcfg === Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) 1 channels configured. /etc/zaptel ======= loadzone=uk defaultzone=us fxsks=1 /etc/asterisk/zapata.conf ================ [trunkgroups] [channels] ; context=default switchtype=national ; sig...

Hi, It seems like my ATA is making a ringing noise... (as it used to), but now (After the upgrade from 1.0.7 to 1.2) asterisk also is either making the ringing, or passing the PRI ringing from the telco on to me. Any suggestions on how to fix this?

This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of

New revision of this patchset that prevents VRAM objects from being allocated on VRAM-less systems like Tegra. This is required for Mesa to work on such systems. Changes since v2: - Use vram_size to detect systems without VRAM and set the correct domain instead of expecting each chip to set its domain explicitly. Alexandre Courbot (2): nouveau: support for custom VRAM domains nvc0: use

...111111111122222 ???????? ? ? ? ? ? 123456789012345678901234 ? Back ? ? ? ? ? ? TxA --------------- - ???????? ? ? ? ? ? TxB --------------- - ? ?? ? ? ? TxC --------------- - ? ? ? ? ? TxD --------------- - ? ? ? ? ? ? ? ? RxA --------------- - ? ? ?...