search for: ringmast

...t; + /* Acknowledge interrupt */ > + nv_mask(priv, 0x12004c, 0x2, 0x2); > + > + while (--retry >= 0) { > + command = nv_rd32(priv, 0x12004c) & 0x3f; > + if (command == 0) > + break; > + } > + > + if (retry < 0) > + nv_warn(priv, "timeout waiting for ringmaster ack\n"); > +} Perhaps I'm being paranoid, but this loop now depends on the frequency of the various clocks involved and therefore might break at some point if the frequencies get sufficiently high. So a slightly safer implementation would use a proper timeout using a combination of...

...>>> + command = nv_rd32(priv, 0x12004c) & 0x3f; >>> + if (command == 0) >>> + break; >>> + } >>> + >>> + if (retry < 0) >>> + nv_warn(priv, "timeout waiting for ringmaster ack\n"); >>> +} >> >> Perhaps I'm being paranoid, but this loop now depends on the frequency >> of the various clocks involved and therefore might break at some point >> if the frequencies get sufficiently high. >> >> So a slightly safer imple...

...while (--retry >= 0) { >> + command = nv_rd32(priv, 0x12004c) & 0x3f; >> + if (command == 0) >> + break; >> + } >> + >> + if (retry < 0) >> + nv_warn(priv, "timeout waiting for ringmaster ack\n"); >> +} > > Perhaps I'm being paranoid, but this loop now depends on the frequency > of the various clocks involved and therefore might break at some point > if the frequencies get sufficiently high. > > So a slightly safer implementation would use a proper...

...; + > + while (--retry >= 0) { > + command = nv_rd32(priv, 0x12004c) & 0x3f; > + if (command == 0) > + break; > + } > + > + if (retry < 0) > + nv_debug(priv, "timeout waiting for ringmaster ack\n"); this sounds kinda bad, no? perhaps a nv_warn? > +} > + > +static int > +nvea_ibus_init(struct nouveau_object *object) > +{ > + struct nvea_ibus_priv *priv = (void *)object; > + int ret; > + > + ret = _nouveau_ibus_init(object); > +...

Using distinctive ring detection with bell202 cid, is there any way to tell DAHDI to sometimes expect the cid after the 2nd ring, other times after the 1st? I just added RingMaster service (2nd DID w/ distinctive ring) to a TDM800P FXO line. No problem setting dringcontext for the 2nd DID. The 1st DID works normally, but I get no CallerID on the 2nd because the call is picked up before the FSK spill is sent. In both cases, the spill is sent about 2.8 secs after the start...

Hi everyone, I'd like to use Asterisk to build a phonetree (www.phonetree.com) type of application, like this: 1. Read a text-based name/phonenumber file. 2. Call every number and play a recorded message. 3. If a beep is detected, replay the message from scratch (to leave messages on an answering machine). 4. Write results to a log file. Does anything like this exist already? Can this be

...cknowledge interrupt */ + command = nv_rd32(priv, 0x0012004c); + command |= 0x2; + nv_wr32(priv, 0x0012004c, command); + + while (--retry >= 0) { + command = nv_rd32(priv, 0x12004c) & 0x3f; + if (command == 0) + break; + } + + if (retry < 0) + nv_debug(priv, "timeout waiting for ringmaster ack\n"); +} + +static int +nvea_ibus_init(struct nouveau_object *object) +{ + struct nvea_ibus_priv *priv = (void *)object; + int ret; + + ret = _nouveau_ibus_init(object); + if (ret) + return ret; + + nvea_ibus_init_priv_ring(priv); + + return 0; +} + +static int +nvea_ibus_ctor(struct nou...

...g\n"); + nvea_ibus_init_priv_ring(priv); + } + + /* Acknowledge interrupt */ + nv_mask(priv, 0x12004c, 0x2, 0x2); + + while (--retry >= 0) { + command = nv_rd32(priv, 0x12004c) & 0x3f; + if (command == 0) + break; + } + + if (retry < 0) + nv_warn(priv, "timeout waiting for ringmaster ack\n"); +} + +static int +nvea_ibus_init(struct nouveau_object *object) +{ + struct nvea_ibus_priv *priv = (void *)object; + int ret; + + ret = _nouveau_ibus_init(object); + if (ret) + return ret; + + nvea_ibus_init_priv_ring(priv); + + return 0; +} + +static int +nvea_ibus_ctor(struct nou...

...> will pay a consultant to answer. The main CentOS IRC channel #centos on irc.freenode.net consciously tries to mix relentlessly On Topic, fast, technically accurate, work safe _teaching_ replies [based loosely on a Socratic method], with a bit of 'floorshow' -- I am one of the 'ringmasters' most weekday US business hours, and we have developed a cadre of 'regulars,' each of whom demonstrates advanced RHCE level expertise in addressing questions in real time from all comers. > The mailing lists and IRC will not spoon feed an answer and > will tell a person th...

Hi everyone, Here is the second batch of patches to add GK20A support to Nouveau. This time we are adding the actual chip support, and this series brings the driver to a point where a slightly-tweaked Mesa successfully runs shaders and renders triangles on GBM! Many thanks to Thierry Reding and the people on the #nouveau IRC channel for their help without which we would not have reached this

Hi all, After a long time having no time, I have finally done some fresh work on my software fax machine. I have replaced the original carrier tracking with something more robust. I have also added 4800, and 2400 bits per second modes, and cleaned up a few bugs in areas like superfine mode operation. I apologise for this update taking so long. At ftp://ftp.opencall.org/pub/spandsp you will

Latest patches for GK20A, taking comments received for v3 into account. Changes since v3: - use only pfn_to_page() and page_to_pfn() in GK20A's FB. These functions are present on every arch and the physical address to page frame number conversion is also consistently a shift of PAGE_SHIFT. This part will probably be replaced by something nicer in the future anyway. - fixed a warning on

Hi everyone, Way overdue v2 of the final patches that enable basic GK20A support. Hopefully all the issues raised with v1 have been addressed. Changes since v1: - Use gk20a clock driver by Ben instead of twiddling nv04's - Name new classes after gk20a instead of nvea - Addressed comments about BAR initialization code factorization - Removed non-essential code which only purpose was to avoid

Hello everyone, GK20A is the Kepler-based GPU used in the upcoming Tegra K1 chips. The following patches perform architectural changes to Nouveau that are necessary to support non-PCI GPUs and add initial support for GK20A. Although the support is still very basic and more user-space changes will be needed to make the full graphics stack run on top of it, we were able to successfully open

Changes since v2: - Enabled software class - Removed unneeded changes to nouveau_accel_init() - Replaced use of architecture-private pfn_to_dma() and dma_to_pfn() with the portable page_to_phys()/phys_to_page() - Fixed incorrect comment/commit log talking about bytes instead of words Hope this looks good! Once this gets merged the next set will be to use this driver on Jetson and Venice2