search for: netlists

...CS/FECS firmware, should we release the netlist "pack" file > or adopt the same format as Nouveau does? (1 file per firmware) > - Should we keep the current files names (e.g. nvxx_fucxxxx[cd]), or > try to switch to more meaningful ones? I'd actually prefer to have the entire netlists bundled, that gives us updated reg/ctx production values too as you guys tweak/update them for hw bugs (etc). They're also nicer in that you get a single bundle of everything that's required for that chipset+engine. I don't have too much opinion on naming. The current model of nv{CHI...

I set virt-manager in qemu:///system space and tried to add new VM but it didn't proceed. Found out serial in crypic form. # cat /sys/devices/virtual/dmi/id/product_serial ÿÿÿÿÿÿÿ #virt-manager --debugTraceback (most recent call last):   File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 225, in _reparse_xml     self._xmlobj = self._build_xmlobj(self._get_raw_xml())

On Mon, Mar 24, 2014 at 6:42 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > Add a GR device for GK20A based on NVE4, with the correct classes > definitions (GK20A's 3D class is 0xa297). > > Most of the NVE4 code can be used on GK20A, so make relevant bits of > NVE4 available to other chips as well. This will need a bit of a rebase on top of the tree I mentioned

I am (belatedly) updating pkgsrc to 2.8.1 (+ bugfix). (FWIW, I think a 2.8.1.1 or 2.8.2 immediately with the fix is in order. >From a packaging viewpoint, the effort to update for a release is about 3 minutes plus time to adapt anythhing that has changed. So I'd much rather have releases more often.) In the pkgsrc build, nut finds tcp wrappers because they are part of the base system.

Dear R-help list: I have two related questions regarding the functions boot.strength and custom.strength in bnlearn. 1) I am using the following commands (on a set of continuous data, the example here run on fake data): > myblacklist<-data.frame(from=c("x1", "x1", "x1", "x2", "x2", "x2")) , to=c("x2",

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

On Fri, 18 May 2007, Keith Whitwell wrote: > I'm interested in understanding the extent of the assumptions which llvm > makes about the types of hardware it is capable of targeting. Different pieces of the compiler make different assumptions. In particular, the code generator we ship is good for targetting certain classes of devices, but isn't fully general (it doesn't help

I'm interested in understanding the extent of the assumptions which llvm makes about the types of hardware it is capable of targeting. In particular, I'm investigating a proposal by Zack Rusin to use llvm as the shader compilation engine within Mesa, targeting GPU backends. I'm aware of the Apple GLSL compiler, and also I've seen the Vector LLVA paper. However, I'm not

On Wed, Mar 26, 2014 at 1:24 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On Mon, Mar 24, 2014 at 6:42 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: >> Add a GR device for GK20A based on NVE4, with the correct classes >> definitions (GK20A's 3D class is 0xa297). >> >> Most of the NVE4 code can be used on GK20A, so make relevant bits of >>

By the way, on the NUT CI farm the libwrap is present on some (though not all) systems - covering linux, freebsd, openindiana... and neither complained about `sockdebug` :\ What version do you have? Maybe it is some alternate implementation? Jim On Thu, Nov 9, 2023 at 3:44?PM Greg Troxel <gdt at lexort.com> wrote: > I am (belatedly) updating pkgsrc to 2.8.1 (+ bugfix). > >

...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>

...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>

Hi Daniel, First of all, awfully sorry for replying so late. Unfortunately your reply had gone to the Spam drawer... Also, I'm answering from Gmail's webmail which IIRC only allows for 'quote original post below'. So please forgive me for not following the proper netiquette of 'quote original post above'. > Is net.ipv4.ip_forward set to 0 ? > > I assume

On Thu, Jul 23, 2020 at 03:34:03PM +0100, Rui Correia wrote: > > Is net.ipv4.ip_forward set to 0 ? > > > > > I assume you're asking if this is setup on the host and not on the VM's. > I've checked the host and it is configured like this: > $ sysctl net.ipv4.ip_forward > net.ipv4.ip_forward = 1 This is good. > Should I change it to =0 ? It

On 13 April 2015 at 20:42, Alexandre Courbot <acourbot at nvidia.com> wrote: > Ben, I guess our main remaining concern with this patch is how it should > integrate wrt. the existing PMU code. Since it is designed to interact with > the NVIDIA firmware, maybe we should use a different base code, or do you > think we can somehow share code and data structures? Hey Alexandre, Sorry

Thanks, I think it would not hurt to add the variables into the source if that helps? A bit puzzled why it wants TCP wrappers though, the program is primarily about the Unix socket access. It can be used by end-users or more likely by developers for troubleshooting; potentially for some automations that act like a NUT driver. Not intended as a prime-time mechanism, but could have its uses... As

On Thu, Jul 23, 2020 at 3:54 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > No, don't change it to 0. We need ip_forward enabled as you say. > That's what I thought. I'm leaving it as it is. > Correct. The KVM host knows where the 10.2.2.1/24 subnet is - it owns > it. The other hosts on your LAN don't know anything about 10.2.2.1/24, > so if they

Chris Lattner wrote: > On Fri, 18 May 2007, Keith Whitwell wrote: >> I'm interested in understanding the extent of the assumptions which llvm >> makes about the types of hardware it is capable of targeting. > > Different pieces of the compiler make different assumptions. In > particular, the code generator we ship is good for targetting certain > classes of

The Wine development release 1.7.51 is now available. What's new in this release (see below for details): - XAudio2 implementation using OpenAL Soft. - Support for the new Universal C Runtime DLL. - Dropdown menu support in the standard Open Dialog. - Grayscale rendering mode in DirectWrite. - Various bug fixes. The source is available from the following locations:

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