search for: amound

Displaying 6 results from an estimated 6 matches for "amound".

Did you mean: amount
2008 Nov 18
1
sound quality between two back-to-back asterisk
...ave two asterisks that are connected to each other via a back-to-back E1 link using a pair of sangoma cards. With the following scenario: SIP-PHONE <-> Asterisk <-> E1 <-> Asterisk <-> SIP-PHONE, the sound quality degrades significantly. I can't understand why as the amound of packet lost should be very minimum. Does anyone know why? Does it have anything to do with what codec to use? Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081119/733a68f5/attachment....
2010 Jan 28
1
[PATCH] drm/nouveau: enlarge GART aperture
This patch enlarges the PCI GART aperture to 512 MB. The current 64MB aperture is too small and should be enlarged. The optimal amound may be card/system-dependent, so a more sophisticated approach may be preferable. In particular, if RAMIN is less than 1MB, a 512MB aperture won't fit. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_sgdma.c | 2 +- 1 files changed, 1 inse...
2018 Jul 21
2
Finding scratch register after function call
...depending on the amount (= adjustment size) *and some other rules*: 1. via one or more target "pop <reg>" instructions (SP increments +2 per instruction), using an unused reg (disregarding the contents after the operation), followed by an optional +1 increment on the SP for odd amounds (SP can be inc/dec'd by 1 directly). 2. incrementing the SP register directly with a special target operation (increments +1 per operation), without using any other register. Requires twice as much instructions as "pop" in sequence, though. 3. via a long sequence of target-specif...
2010 Feb 09
0
[PATCH] drm/nouveau: enlarge GART aperture (v2)
Changes in v2: - Compute size based on ramin_rsvd_size This patch enlarges the PCI GART aperture to 512 MB, or the space covered by a DMA object filling half RAMIN. The current 64MB aperture is too small and should be enlarged. The optimal amound may be card/system-dependent, so a more sophisticated approach may be preferable. Could anyone with an nv04 test whether this doesn't break there? Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_sgdma.c | 14 ++++++++++++-- 1 files changed...
2006 Apr 15
6
Phones that work well through NAT
Hi, everyone, We've been reasonably happy with Polycom SoundPoint phones, but we only have them installed on the LAN. I've read that they have problems working across NAT. So ... I guess I have a few questions. First, is there a way to get Polycoms to work well over NAT? If not, then are there phones of comparable voice quality that do work well over NAT? Without costing a lot more?
2009 Feb 06
14
Credit Card processing machines
Anyone have much luck with these on ATA's? I have a few sites that use them succesfully with multi-port Audiocodes boxes, but just connected ten machines to Linksys 2102s and they are very flaky. Using u-law on a 100Mb switched network that is barely utilized, then out a T1 on a Sangoma card. Perhaps there is some tuning on the Linksys or the credit card machine itself? Going to look