search for: generer

Displaying 16 results from an estimated 16 matches for "generer".

Did you mean: generar
2006 Nov 11
2
Segmentation fault
Hi! I'm running NUT 2.0.4 and occasionally I get a segfault when starting newhidups and if I don't get a segfault when starting newhidups the process starts eating away at my memory. I sat down trying to genererate -DDDDD debug info, but just because of that I can't get it to do a segfault. So until I can, has things changed in the development version, that might have fixed this? Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) Detected a UPS: American Power Conversion/Back-UPS CS 500 FW:808...
2010 Jul 20
20
render :js => "alert('Test !')"
Hi Folks, I use render :js => "alert(''Test !'')" in my modele, but instead of having the alert displayed, the browser try to donload a file containing this string : <<render :js => "alert(''Test !'')">>. Do you know why I the browser behaves such a way ? Regards -- Posted via http://www.ruby-forum.com/. -- You received
2013 May 18
0
[ANNOUNCE] bitmap 1.0.7
...- X bitmap (XBM) editor and converter utilities This minor maintenance release fixes some compiler warnings & man page typos, and other code cleanups. Alan Coopersmith (6): Fix pixmap leak in error paths of BWGetUnzoomedPixmap Combine usage messages into a single string Fix genererate typo in bmtoa error messages Simplify & unify error path between mktemp & mkstemp versions Mark usage() functions as noreturn, as suggested by gcc bitmap 1.0.7 Bjarni Ingi Gislason (1): bitmap.man: Fix some typos. git tag: bitmap-1.0.7 http://xorg.freedesktop....
2024 Jul 30
1
[PATCH 2/2] [v6] drm/nouveau: expose GSP-RM logging buffers via debugfs
...some weird C++ wanna-be code, IMHO. ?I don't think this is an improvement. I'd rather keep it as-is. > > +/* > > + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" > > + * data structures, and each engine has a "class ID" genererated by a > > + * pre-processor. This is the class ID for the PMU. > > + */ > > +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 > > + > > +/** > > + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers > > Is this structure version...
2001 Apr 28
3
VPN?
Once you have Samba shares up and running on the internal network, how do you go about making them available (browsable) via the Internet--a VPN? I hate to say it but in Windows 2k it's just a matter of a few clicks on the server and client. I'm hoping that it's not much harder with a Linux server/Windows client. Anything involving something like SSH will be too hard for most users.
2007 Apr 06
2
lm() intercept at the end, rather than at the beginning
Hi, I wonder if someone has already figured out a way of making summary(mylm) # where mylm is an object of the class lm() to print the "(Intercept)" at the last line, rather than the first line of the output. I don't know about, say, biostatistics, but in economics the intercept is usually the least interesting of the parameters of a regression model. That's why, say, Stata
2024 Jul 31
1
[PATCH 2/2] [v6] drm/nouveau: expose GSP-RM logging buffers via debugfs
...hutdown can't be called with the "head instance" of struct struct nvif_log. > > > > +/* > > > + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" > > > + * data structures, and each engine has a "class ID" genererated by a > > > + * pre-processor. This is the class ID for the PMU. > > > + */ > > > +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 > > > + > > > +/** > > > + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers > &...
2024 Jul 30
1
[PATCH 2/2] [v6] drm/nouveau: expose GSP-RM logging buffers via debugfs
...); > +MODULE_PARM_DESC(keep_gsp_logging, > + "Migrate the GSP-RM logging debugfs entries upon exit"); > + > +/* > + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" > + * data structures, and each engine has a "class ID" genererated by a > + * pre-processor. This is the class ID for the PMU. > + */ > +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 > + > +/** > + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers Is this structure versioned? If so, does it relate to a specific...
2024 Jul 29
1
[PATCH 2/2] [v6] drm/nouveau: expose GSP-RM logging buffers via debugfs
...m(keep_gsp_logging, bool, 0444); +MODULE_PARM_DESC(keep_gsp_logging, + "Migrate the GSP-RM logging debugfs entries upon exit"); + +/* + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" + * data structures, and each engine has a "class ID" genererated by a + * pre-processor. This is the class ID for the PMU. + */ +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 + +/** + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers + * @ucode_eng_desc: the engine descriptor + * @libos_print_buf_size: the size of the libos_prin...
2024 Oct 30
2
[PATCH 2/2] [v9] drm/nouveau: expose GSP-RM logging buffers via debugfs
...m(keep_gsp_logging, bool, 0444); +MODULE_PARM_DESC(keep_gsp_logging, + "Migrate the GSP-RM logging debugfs entries upon exit"); + +/* + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" + * data structures, and each engine has a "class ID" genererated by a + * pre-processor. This is the class ID for the PMU. + */ +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 + +/** + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers + * @ucode_eng_desc: the engine descriptor + * @libos_print_buf_size: the size of the libos_prin...
2024 Aug 02
1
[PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object
Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- Notes: v2: added get/put_device calls
2024 Jul 29
2
[PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object
Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> v2: added get/put_device calls ---
2024 Sep 10
1
[PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object
Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- .../gpu/drm/nouveau/include/nvkm/subdev/gsp.h | 1 +
2024 Oct 30
2
[PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object
Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- .../gpu/drm/nouveau/include/nvkm/subdev/gsp.h | 1 +
2024 Oct 03
1
[PATCH 2/2] [v8] drm/nouveau: expose GSP-RM logging buffers via debugfs
...l this should go into module_init() and module_exit(), then you don't need the mutex and all the reference counts. > + > +/* > + * GSP-RM uses a pseudo-class mechanism to define of a variety of per-"engine" > + * data structures, and each engine has a "class ID" genererated by a > + * pre-processor. This is the class ID for the PMU. > + */ > +#define NV_GSP_MSG_EVENT_UCODE_LIBOS_CLASS_PMU 0xf3d722 > + > +/** > + * rpc_ucode_libos_print_v1E_08 - RPC payload for libos print buffers > + * @ucode_eng_desc: the engine descriptor > + * @libos_pr...
2004 Jul 13
12
Permutations
Dear R users, I?m a beginner user of R and I?ve a problem with permutations that I don?t know how to solve. I?ve 12 elements in blocks of 3 elements and I want only to make permutations inter-blocks (no intra-blocks) (sorry if the terminology is not accurate), something similar to: 1 2 3 | 4 5 6 | 7 8 9 | 10 11 12 ----------1st permutation 1 3 2 | 4 5 6 | 7 8 9 | 10 11 12 NO - - 3 2 1