search for: l192

...those errors are? (Or, even better, provide the full table so that we'll have a better idea in future cases as well.) Here are a few that we know about, so you know exactly what table I'm talking about (our full list at https://github.com/envytools/envytools/blob/master/rnndb/nv50_defs.xml#L192): 0x04: INVALID_VALUE 0x05: INVALID_ENUM 0x08: INVALID_OBJECT 0x0c: INVALID_BITFIELD 0x3f: PRIMITIVE_ID_NEEDS_GP We read this data error value from mmio reg 0x400110. Furthermore, if you could provide any insight as to why we would see those errors on GF106 but not any other Fermi/Kepler that we...

..._ext/Connections.h I'm not sure of a good pedagogic example; people who want to write their own connections usually want to do so for complicated reasons! This is my own abandoned attempt https://github.com/mtmorgan/socketeer/blob/b0a1448191fe5f79a3f09d1f939e1e235a22cf11/src/connection.c#L169-L192 where connection_local_client() is called from R and _connection_local() creates and populates the appropriate structure. Probably I have done things totally wrong (e.g., by not checking the version of the API, as advised in the header file!) Martin Morgan ?On 5/6/20, 2:26 PM, "R-devel on be...

...t; I'm not sure of a good pedagogic example; people who want to write their own connections usually want to do so for complicated reasons! > > This is my own abandoned attempt https://github.com/mtmorgan/socketeer/blob/b0a1448191fe5f79a3f09d1f939e1e235a22cf11/src/connection.c#L169-L192 where connection_local_client() is called from R and _connection_local() creates and populates the appropriate structure. Probably I have done things totally wrong (e.g., by not checking the version of the API, as advised in the header file!) > > Martin Morgan > > ?On 5/...

...r one fetched from (1) or one you passed on the command line. Libguestfs then looks that up with libvirt to check it exists and to get the list of disks. That happens in src/libvirt-auth.c:guestfs___open_libvirt_connection: https://github.com/libguestfs/libguestfs/blob/master/src/libvirt-auth.c#L192 (3) Finally if you are using the libvirt backend (which you are not on Ubuntu) then there would be a third connection to run the appliance, although it uses the same code as (2). I believe the problem here is that (1) does not pass an auth handler. ie. it calls virConnectOpenReadonly, not virConn...

Hello, I'm running into an issue using the 'virt-df' command when SASL is enabled in libvirt. I'm running version 1.26.5 of libguestfs on an Ubuntu 14.04 OS. I'm running 'virt-df' for all guests at one time, not specifying a domain or image to use. I was expecting a SASL authentication prompt but to no avail. Below is a sample run: root@all-in-one:~# virt-df -P 15

...le; people who want to write > > their own connections usually want to do so for complicated reasons! > > > > > > This is my own abandoned attempt > > > https://github.com/mtmorgan/socketeer/blob/b0a1448191fe5f79a3f09d1f939e1e235a22cf11/src/connection.c#L169-L192 > > where connection_local_client() is called from R and _connection_local() > > creates and populates the appropriate structure. Probably I have done > > things totally wrong (e.g., by not checking the version of the API, as > > advised in the header file!) > > &g...

...en better, provide the full table so that we'll have a better idea > in future cases as well.) > > Here are a few that we know about, so you know exactly what table I'm > talking about (our full list at > https://github.com/envytools/envytools/blob/master/rnndb/nv50_defs.xml#L192): > > 0x04: INVALID_VALUE > 0x05: INVALID_ENUM > 0x08: INVALID_OBJECT > 0x0c: INVALID_BITFIELD > 0x3f: PRIMITIVE_ID_NEEDS_GP > > We read this data error value from mmio reg 0x400110. > > Furthermore, if you could provide any insight as to why we would see > those...

...> > I'm not sure of a good pedagogic example; people who want to write their own connections usually want to do so for complicated reasons! > > This is my own abandoned attempt https://github.com/mtmorgan/socketeer/blob/b0a1448191fe5f79a3f09d1f939e1e235a22cf11/src/connection.c#L169-L192 where connection_local_client() is called from R and _connection_local() creates and populates the appropriate structure. Probably I have done things totally wrong (e.g., by not checking the version of the API, as advised in the header file!) > > Martin Morgan > > ?On 5/6/20, 2:26 PM, &...

...r one fetched from (1) or one you passed on the command line. Libguestfs then looks that up with libvirt to check it exists and to get the list of disks. That happens in src/libvirt-auth.c:guestfs___open_libvirt_connection: https://github.com/libguestfs/libguestfs/blob/master/src/libvirt-auth.c#L192 (3) Finally if you are using the libvirt backend (which you are not on Ubuntu) then there would be a third connection to run the appliance, although it uses the same code as (2). I believe the problem here is that (1) does not pass an auth handler. ie. it calls virConnectOpenReadonly, not virConn...

...of a good pedagogic example; people who want to write > their own connections usually want to do so for complicated reasons! > > > > This is my own abandoned attempt > https://github.com/mtmorgan/socketeer/blob/b0a1448191fe5f79a3f09d1f939e1e235a22cf11/src/connection.c#L169-L192 > where connection_local_client() is called from R and _connection_local() > creates and populates the appropriate structure. Probably I have done > things totally wrong (e.g., by not checking the version of the API, as > advised in the header file!) > > > > Martin M...

...1) or one you passed on the command line. > Libguestfs then looks that up with libvirt to check it exists and to get the list of disks. That happens in > src/libvirt-auth.c:guestfs___open_libvirt_connection: > > https://github.com/libguestfs/libguestfs/blob/master/src/libvirt-auth.c#L192 > > (3) Finally if you are using the libvirt backend (which you are not on > Ubuntu) then there would be a third connection to run the appliance, although it uses the same code as (2). > > I believe the problem here is that (1) does not pass an auth handler. > ie. it calls virCo...

Dear R Devel, Since Linux moved away from using a file-system interface for audio, I think it is necessary to write special libraries to interface with audio hardware from various languages on Linux. In R, it seems like the appropriate datatype for a `snd_pcm_t` handle pointing to an open ALSA source or sink would be a "connection". Connection types are already defined in R for