search for: context

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_context.c | 1245 ++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_context.h | 174 +++++ 2 files changed, 1419 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_context.c create mode 100644 drivers/misc/vmw_vmci/vmci_context.h diff --git a/drivers/misc/vmw_vmci/v...

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_context.c | 1245 ++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_context.h | 174 +++++ 2 files changed, 1419 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_context.c create mode 100644 drivers/misc/vmw_vmci/vmci_context.h diff --git a/drivers/misc/vmw_vmci/v...

On Sun, Apr 11, 2010 at 4:09 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Kenneth Uildriks <kennethuil at gmail.com> wrote: >> As I see it, the context switching mechanism itself needs to know >> where to point the stack register when switching.  The C routines take >> an initial stack pointer when creating the context, and keep track of >> it from there.  If we don't actually need to interoperate with >> contexts creat...

Kenneth Uildriks <kennethuil at gmail.com> wrote: > As I see it, the context switching mechanism itself needs to know > where to point the stack register when switching.  The C routines take > an initial stack pointer when creating the context, and keep track of > it from there.  If we don't actually need to interoperate with > contexts created from the C ro...

Okay, I am not understanding if I have this correct or not. I have a requirement to allow guests into a PBX from different domains. However, I can not allow the guests into the default context because each domain has its own IVR. So I end up setting the domain context. I also need to provide separate contexts for different sip users (different dial groups). Small system, few users, so it doesn't make sense to create separate Asterisk boxes (cost wise and support) and some of the p...

...+ > .../auxiliary/target-helpers/inline_drm_helper.h | 30 + > src/gallium/drivers/tegra/Automake.inc | 11 + > src/gallium/drivers/tegra/Makefile.am | 17 + > src/gallium/drivers/tegra/Makefile.sources | 4 + > src/gallium/drivers/tegra/tegra_context.c | 699 +++++++++++++++++++++ > src/gallium/drivers/tegra/tegra_context.h | 80 +++ > src/gallium/drivers/tegra/tegra_resource.c | 219 +++++++ > src/gallium/drivers/tegra/tegra_resource.h | 98 +++ > src/gallium/drivers/tegra/tegra_screen.c...

I'm trying to clarify contexts and their uses. I do have a good general understanding of them. My question is about "undeclared" and "non-existant" contexts. If I have a block somewhere (in sip.conf, for example), and it has no "context=thiscontext" field, does it just automatically use the "...

...B fixme:msimtf:DllGetClassObject ({50d5107a-d278-4871-8989-f4ceaaf59cfc} {00000001-0000-0000-c000-000000000046} 0x329048) err:ole:apartment_getclassobject DllGetClassObject returned error 0x80040111 err:ole:CoGetClassObject no class object {50d5107a-d278-4871-8989-f4ceaaf59cfc} could be created for context 0x401 err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not registered err:ole:CoGetClassObject no class object {6c736db1-bd94-11d0-8a23-00aa00b58e10} could be created for context 0x1 fixme:shell:UnixFolder_IShellFolder2_QueryInterface Unimplemented interface {062e1261-a60e-11d0...

I'm trying to create several contexts for extentions with different levels of access to features and I'm wondering how the heck do I include all the contexts so that you can call internal to any extention in another context without giving the features of the higher level context to the lower level context? ie..... [admin] include...

...7;40m) [1;30;40m == [0;37;40mParsing '/etc/asterisk/adsi.conf': Found [1;30;40m [0;37;40m[[1;37;40mres_parking.so[0;37;40m] => ([33;40mCall Parking Resource[0;37;40m) [1;30;40m == [0;37;40mParsing '/etc/asterisk/parking.conf': Found [1;30;40m -- [0;37;40mRegistered extension context 'parkedcalls' [1;30;40m -- [0;37;40mAdded extension '701' priority 1 to parkedcalls [1;30;40m -- [0;37;40mAdded extension '702' priority 1 to parkedcalls [1;30;40m -- [0;37;40mAdded extension '703' priority 1 to parkedcalls [1;30;40m -- [0;37;40mAdded ext...

First of all, I am very mac illiterate as I have been using windows all my life. I am enquiring to see about getting some help on the whole wine thing. I have been looking at the wiki and FAQs but Im lost. I installed wine from sourceforge but when I go to click wineinstall in the tools folder, this is what I get: Last login: Sun Sep 18 21:31:41 on ttys000

...| 5 + .../auxiliary/target-helpers/inline_drm_helper.h | 30 + src/gallium/drivers/tegra/Automake.inc | 11 + src/gallium/drivers/tegra/Makefile.am | 17 + src/gallium/drivers/tegra/Makefile.sources | 4 + src/gallium/drivers/tegra/tegra_context.c | 699 +++++++++++++++++++++ src/gallium/drivers/tegra/tegra_context.h | 80 +++ src/gallium/drivers/tegra/tegra_resource.c | 219 +++++++ src/gallium/drivers/tegra/tegra_resource.h | 98 +++ src/gallium/drivers/tegra/tegra_screen.c | 311 +++++++++ s...

...it actually is. I like that plan. > There is code which relies on the fact that LDTs are allocated in page > chunks, and it is both cleaner and more convenient to keep the rather > poorly named "size" variable from the LDT in terms of LDT pages. I noticed it's replaced by context.ldt and context.ldt_pages, which appear to be decoupling the overloaded use from before. Looks sane. More comments below. > Signed-off-by: Zachary Amsden <zach@vmware.com> > Index: linux-2.6.13/include/asm-i386/mmu.h > ===============================================================...

...it actually is. I like that plan. > There is code which relies on the fact that LDTs are allocated in page > chunks, and it is both cleaner and more convenient to keep the rather > poorly named "size" variable from the LDT in terms of LDT pages. I noticed it's replaced by context.ldt and context.ldt_pages, which appear to be decoupling the overloaded use from before. Looks sane. More comments below. > Signed-off-by: Zachary Amsden <zach@vmware.com> > Index: linux-2.6.13/include/asm-i386/mmu.h > ===============================================================...

Right now the functionality is available, sometimes, from the C standard library. But embedded environments (often running a limited standard library) and server environments would benefit heavily from a standard way to specify context switches within a single thread in the style of makecontext/swapcontext/setcontext, and built-in support for these operations would also open the way for optimizers to begin handling these execution paths. The use cases for these operations, and things like coroutines built on top of them, will on...

doc/swfdec-sections.txt | 2 libswfdec/swfdec_as_context.c | 54 ++++++++++++++++++- libswfdec/swfdec_as_context.h | 9 ++- libswfdec/swfdec_as_interpret.c | 79 ++++++++++++++-------------- test/trace/Makefile.am | 7 ++ test/trace/try-throw-in-finally-6.swf |binary test/trace...

Hi there, I'm trying to run Lite Manager on Ubuntu 11.10 using Wine 1.3, but all I get is a "program encountered a serious problem" screen. Any chance that someone could help me with this? :/

Hi all, I need to configure DIDs for different companies and they should reach on different extension with different context. Cant we have same extension in different context? This is what we we want Company A: Context Company_A IVR Company A Extensions: 101,102,103,104 etc. Company B: Context Company_B IVR Company B Extensions: 101,102,103,104 etc. Company C: Context Company_C IVR Company Extensions: 101,102,103,104...

Greetings, Somewhere on my asterisk system, a calls come in in a certain context, for example, from-sip or from-pstn. Then the calls gets routed through the dialplan, and a macro gets called, and another one and then the call needs to be redirected to another number in the same initial context. And you can use Dial(Local/number/initialcontext) for that. Oops, this initial con...

Hello, I am trying to configure asterisk 1.0.7pre to get incoming calls from an ISDN line using an AVM fritz PCI 2.0 with Chan_capi 0.3.5. My problem is that the context is not recognised in the /etc/asterisk/capi.conf I have in /etc/asterisk/capi.conf 's section "[interfaces]" the following directive context=isdn and the following directive in /etc/asterisk/extensions.conf in the context [isdn] [isdn] exten => s,1,Dial(SIP/${DNID:4},60,tr) H...