search for: netlist

...nder /lib/firmware/nouveau or > /lib/firmware/nvidia ? (this directory already exists for Tegra USB > firmware and makes more sense to me, since the firmware is not > Nouveau-specific) I think /lib/firmware/nvidia makes sense here too. > - For GPCCS/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...

...quot;, line 344, in reset_state     self.set_conn(activeconn, force_validate=True)   File "/usr/share/virt-manager/virtManager/create.py", line 225, in set_conn     self.set_conn_state()   File "/usr/share/virt-manager/virtManager/create.py", line 626, in set_conn_state     self.netlist.reset_state()   File "/usr/share/virt-manager/virtManager/netlist.py", line 405, in reset_state     self._populate_network_list()   File "/usr/share/virt-manager/virtManager/netlist.py", line 253, in _populate_network_list     vnet_bridges)   File "/usr/share/virt-manager/v...

...to other chips as well. This will need a bit of a rebase on top of the tree I mentioned earlier (also queued for drm-next now), where I've further split out and named the various chunks of state. Does GK104 match entirely correctly, or just happen to work? I could probably hunt down the GK20A netlist images and check that actually :) > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > drivers/gpu/drm/nouveau/Makefile | 1 + > .../gpu/drm/nouveau/core/engine/graph/ctxnve4.c | 4 +- > drivers/gpu/drm/nouveau/core/engine/graph/nvc0...

...ing all in server `libparseconf.la' is up to date. CC sockdebug.o `libcommon.la' is up to date. CC upsd.o CC user.o CC conf.o CC netssl.o CC sstate.o CC desc.o CC netget.o CC netmisc.o CC netlist.o CC netuser.o CC netset.o CC netinstcmd.o CCLD sockdebug ld: /usr/lib/libwrap.so: undefined reference to `deny_severity' ld: /usr/lib/libwrap.so: undefined reference to `allow_severity' *** [sockdebug] Error code 1 as I understand it, the tcprap...

...there a way to completely disallow all blacklisted arcs, such that their strength is 0.0? Or is there a compelling reason why that should not be done? 2) In the documentation of custom.strength, the following code example is given: start = random.graph(nodes = names(learning.test), num = 50) netlist = lapply(start, function(net) { hc(learning.test, score = "bde", iss = 10, start = net) }) arcs = custom.strength(netlist, nodes = names(learning.test), cpdag = FALSE) This code makes 50 different networks from the same data, then uses them as input for custom.strength. The networks ar...

...s/netget.Tpo .deps/netget.Po gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT netmisc.o -MD -MP -MF .deps/netmisc.Tpo -c -o netmisc.o netmisc.c mv -f .deps/netmisc.Tpo .deps/netmisc.Po gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT netlist.o -MD -MP -MF .deps/netlist.Tpo -c -o netlist.o netlist.c mv -f .deps/netlist.Tpo .deps/netlist.Po gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT netuser.o -MD -MP -MF .deps/netuser.Tpo -c -o netuser.o netuser.c mv -f .deps/netuser.Tpo .deps/netuser.Po gcc -DHAVE_...

...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 if you're synthesizing a netlist from llvm, for example). > In particular, I'm investigating a proposal by Zack Rusin to use llvm as > the shader compilation engine within Mesa, targeting GPU backends. Ok > It seems that LLVA and by extension Vector-LLVA assumes that looping and > branching control flow can be e...

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

...bit of a rebase on top of the tree I mentioned > earlier (also queued for drm-next now), where I've further split out > and named the various chunks of state. Will do that. > > Does GK104 match entirely correctly, or just happen to work? I could > probably hunt down the GK20A netlist images and check that actually :) Do you mean, the init sequence? I haven't checked in detail (we are certainly doing things differently in the non-DRM driver), but the registers seem to match and the GPU is able to render after that. I admit I have not looked much further for now. The only r...

.... > CC sockdebug.o > `libcommon.la' is up to date. > CC upsd.o > CC user.o > CC conf.o > CC netssl.o > CC sstate.o > CC desc.o > CC netget.o > CC netmisc.o > CC netlist.o > CC netuser.o > CC netset.o > CC netinstcmd.o > CCLD sockdebug > ld: /usr/lib/libwrap.so: undefined reference to `deny_severity' > ld: /usr/lib/libwrap.so: undefined reference to `allow_severity' > *** [sockdebug] Error cod...

...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

...d. One global instance that runs as root for privileged set ups, and then one per user instance that runs unprivileged. If you run "virsh" as non-root, you'll be querying the per-user instance. virt-manager uses the privileged instance by default. Try 'virsh -c qemu:///system netlist' instead, or simply run virsh as root. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange...

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

.... > CC sockdebug.o > `libcommon.la' is up to date. > CC upsd.o > CC user.o > CC conf.o > CC netssl.o > CC sstate.o > CC desc.o > CC netget.o > CC netmisc.o > CC netlist.o > CC netuser.o > CC netset.o > CC netinstcmd.o > CCLD sockdebug > ld: /usr/lib/libwrap.so: undefined reference to `deny_severity' > ld: /usr/lib/libwrap.so: undefined reference to `allow_severity' > *** [sockdebug] Error cod...

...as root for privileged set ups, and then one per > user instance that runs unprivileged. > > If you run "virsh" as non-root, you'll be querying the per-user instance. > > virt-manager uses the privileged instance by default. > > Try 'virsh -c qemu:///system netlist' instead, or simply run > virsh as root. > Got it. Here's the output with sudo: $ sudo virsh net-list [sudo] password for ******: Name State Autostart Persistent -------------------------------------------- default active yes yes routed active yes...

...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 if you're > synthesizing a netlist from llvm, for example). > >> In particular, I'm investigating a proposal by Zack Rusin to use llvm as >> the shader compilation engine within Mesa, targeting GPU backends. > > Ok > >> It seems that LLVA and by extension Vector-LLVA assumes that looping and >...

...ut native quartz 36300 valgrind shows an invalid read in msxml3/tests/saxreader.c 36498 Project64: about page is black 36589 valgrind shows uninitialized memory use in usp10/tests/usp10.c 36875 Incorrect check in PlayEnhMetaFileRecord() with case == EMR_SCALEWINDOWEXTEX 37266 LTSpice netlist text unreadable (monospaced text glyphs are misplaced and overlapping) 37451 python 3.1.1: test_test_decimal failed 37865 echo/ not works as expected (like echo. and echo:) 37915 Multiple games and applications need proper handling of Vista+ 'PROCESS_QUERY_LIMITED_INFORMATION' righ...

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