search for: _inst

...man/ upssched.conf.5 ../../../docs/man/nut.conf.5 ../../../docs/man/ ups.conf.5 ../../../docs/man/upsd.conf.5 ../../../docs/man/upsd.users. 5 ../../../docs/man/upsmon.conf.5 ../../../docs/man/upssched.conf.5 '/ var/lib/buildbot/buildbot-slave-cayenne/Ubuntu-lucid-x86/build/ nut-2.4.3-r2739/_inst/share/man/man5' /usr/bin/install: will not overwrite just-created `/var/lib/buildbot/ buildbot-slave-cayenne/Ubuntu-lucid-x86/build/nut-2.4.3-r2739/_inst/ share/man/man5/nut.conf.5' with `../../../docs/man/nut.conf.5' /usr/bin/install: will not overwrite just-created `/var/lib/buildb...

...ce package ... OK * checking if there is a namespace ... OK * checking for executable files ... OK * checking for hidden files and directories ... NOTE Found the following hidden files and directories: .BBSoptions ._.BBSoptions ._DESCRIPTION ._NAMESPACE ._R ._README ._build ._inst ._man ._src ._vignettes R/._AffyRNAdeg.R R/._Constructors.R R/._TreeSetClasses.R R/._bgcorrect.R R/._dabg.call.R ... man/._AffyRNAdeg.Rd man/._AnalysisTreeSet-class.Rd man/._CallTreeSet-class.Rd man/._DataTreeSet-class.Rd man/._ExprTreeSet-class.Rd ... src/...

...ome as files to be directly loaded. However for the current GR firmware we took the approach of splitting the bl, code and data sections into their own files, and building the image and descriptor on-the-fly, as you can see from gm200/gr: gm200/gr/fecs_bl.bin gm200/gr/fecs_data.bin gm200/gr/fecs_inst.bin gm200/gr/fecs_sig.bin The bl, data, and inst files are loaded and combined into an image while the corresponding descriptor is built. This is done in the ls_ucode_img_build() function. The main reason for doing this is there is that for a given GPU generation, the _bl and _inst files are v...

...e current GR firmware we took the approach of splitting the bl, code and >> data sections into their own files, and building the image and descriptor >> on-the-fly, as you can see from gm200/gr: >> >> gm200/gr/fecs_bl.bin >> gm200/gr/fecs_data.bin >> gm200/gr/fecs_inst.bin >> gm200/gr/fecs_sig.bin >> >> The bl, data, and inst files are loaded and combined into an image while the >> corresponding descriptor is built. This is done in the ls_ucode_img_build() >> function. >> >> The main reason for doing this is there is that...

...ode >>>> and >>>> data sections into their own files, and building the image and descriptor >>>> on-the-fly, as you can see from gm200/gr: >>>> >>>> gm200/gr/fecs_bl.bin >>>> gm200/gr/fecs_data.bin >>>> gm200/gr/fecs_inst.bin >>>> gm200/gr/fecs_sig.bin >>>> >>>> The bl, data, and inst files are loaded and combined into an image while >>>> the >>>> corresponding descriptor is built. This is done in the >>>> ls_ucode_img_build() >>>> f...

...s a namespace ... OK > * checking for executable files ... OK > * checking for hidden files and directories ... NOTE > Found the following hidden files and directories: > .BBSoptions > ._.BBSoptions > ._DESCRIPTION > ._NAMESPACE > ._R > ._README > ._build > ._inst > ._man > ._src > ._vignettes > R/._AffyRNAdeg.R > R/._Constructors.R > R/._TreeSetClasses.R > R/._bgcorrect.R > R/._dabg.call.R > ... > man/._AffyRNAdeg.Rd > man/._AnalysisTreeSet-class.Rd > man/._CallTreeSet-class.Rd > man/._DataTreeSet-class.Rd...

...r own files, and building the image and >>>>>> descriptor >>>>>> on-the-fly, as you can see from gm200/gr: >>>>>> >>>>>> gm200/gr/fecs_bl.bin >>>>>> gm200/gr/fecs_data.bin >>>>>> gm200/gr/fecs_inst.bin >>>>>> gm200/gr/fecs_sig.bin >>>>>> >>>>>> The bl, data, and inst files are loaded and combined into an image >>>>>> while >>>>>> the >>>>>> corresponding descriptor is built. This is don...

...ded. However for > the current GR firmware we took the approach of splitting the bl, code and > data sections into their own files, and building the image and descriptor > on-the-fly, as you can see from gm200/gr: > > gm200/gr/fecs_bl.bin > gm200/gr/fecs_data.bin > gm200/gr/fecs_inst.bin > gm200/gr/fecs_sig.bin > > The bl, data, and inst files are loaded and combined into an image while the > corresponding descriptor is built. This is done in the ls_ucode_img_build() > function. > > The main reason for doing this is there is that for a given GPU generation,...

...roach of splitting the bl, code >>> and >>> data sections into their own files, and building the image and descriptor >>> on-the-fly, as you can see from gm200/gr: >>> >>> gm200/gr/fecs_bl.bin >>> gm200/gr/fecs_data.bin >>> gm200/gr/fecs_inst.bin >>> gm200/gr/fecs_sig.bin >>> >>> The bl, data, and inst files are loaded and combined into an image while >>> the >>> corresponding descriptor is built. This is done in the >>> ls_ucode_img_build() >>> function. >>> >&g...

...data sections into their own files, and building the image and >>>>> descriptor >>>>> on-the-fly, as you can see from gm200/gr: >>>>> >>>>> gm200/gr/fecs_bl.bin >>>>> gm200/gr/fecs_data.bin >>>>> gm200/gr/fecs_inst.bin >>>>> gm200/gr/fecs_sig.bin >>>>> >>>>> The bl, data, and inst files are loaded and combined into an image >>>>> while >>>>> the >>>>> corresponding descriptor is built. This is done in the >>>&gt...

...ble files ... OK >> * checking for hidden files and directories ... NOTE >> Found the following hidden files and directories: >> .BBSoptions >> ._.BBSoptions >> ._DESCRIPTION >> ._NAMESPACE >> ._R >> ._README >> ._build >> ._inst >> ._man >> ._src >> ._vignettes >> R/._AffyRNAdeg.R >> R/._Constructors.R >> R/._TreeSetClasses.R >> R/._bgcorrect.R >> R/._dabg.call.R >> ... >> man/._AffyRNAdeg.Rd >> man/._AnalysisTreeSet-class.Rd >> m...

...ich files will be included diff -urp oldrsync/install-sh newrsync/install-sh --- oldrsync/install-sh Tue Nov 19 18:57:34 2002 +++ newrsync/install-sh Tue Nov 19 18:58:11 2002 @@ -208,7 +208,7 @@ else # Make a temp file name in the proper directory. - dsttmp=$dstdir/#inst.$$# + dsttmp=$dstdir/_inst.$$_ # Move or copy the file name to the temp name diff -urp oldrsync/lib/getaddrinfo.c newrsync/lib/getaddrinfo.c --- oldrsync/lib/getaddrinfo.c Sun Nov 17 04:52:57 2002 +++ newrsync/lib/getaddrinfo.c Sun Nov 17 05:05:28 2002 @@ -73,9 +73,9 @@ static const char in6_loopback[] = { }; struct...