Displaying 20 results from an estimated 4047 matches for "dryingly".
Did you mean:
drying
2005 Jun 22
2
r programming help
Dear list,
Is there anyway i can make the following formula short
by r-programming?
CYCLE.n<-c(NA,
WET[1]*DRY[1],
WET[1]*DRY[2]+WET[2]*DRY[1],
WET[1]*DRY[3]+WET[2]*DRY[2]+WET[3]*DRY[1],
WET[1]*DRY[4]+WET[2]*DRY[3]+WET[3]*DRY[2]+WET[4]*DRY[1],
WET[1]*DRY[5]+WET[2]*DRY[4]+WET[3]*DRY[3]+WET[4]*DRY[2]+WET[5]*DRY[1],
2016 Jun 28
2
nouveau_drv_video.so ?
nouveau_drv_video.so - what should it be?
https://koji.fedoraproject.org/koji/buildinfo?buildID=722316
... 0.7.4-13 - Revert symlinks - should be handled by mesa rhbz#1271842
https://bugzilla.redhat.com/show_bug.cgi?id=1271842
... 0.7.4-12 - Add symlinks for radeonsi,r600,nouveau - rhbz#1264499
https://bugzilla.redhat.com/show_bug.cgi?id=1264499
$ rpm -q
2016 Jun 30
1
[Mesa-dev] nouveau_drv_video.so ?
Are you using VA-API on X11? libva gets the driver name from Xserver,
it is nouveau for you. so libva tries to load nouveau_drv_video.so.
You can create a symlink for nouveau pointing to a available driver or
just ignore the message because you have gallium_drv_video.so now.
Thanks
Haihao
> nouveau_drv_video.so - what should it be?
>
>
>
2010 Feb 02
2
[RFC] Merge of a reincarnation of the nouveau classic mesa driver.
For a long time the gallium pipe drivers for nvidia fixed function cards
(nv0x, nv1x and, to some extent, nv2x) have remained unmaintained and
godforsaken -- especially nv0x and nv1x had seen almost no progress
since their creation.
They've recently grown a classic mesa driver which implements many new
features: texturing, hardware-accelerated tnl. However the killer
feature is "it
2007 Jun 09
2
Fedora and direct rendering
Hello,
I'm using Fedora 7 and I thought I should try nouveau. I couldn't get
direct rendering to work.
I found out that the Mesa package that ships with Fedora 7 doesn't
include a DRI interface for the nouveau module. So I fetched the latest
Mesa source from git, compiled with 'mke DRI_DIRS=nouveau linux-dri-x86'
and copied the produced ./lib/nouveau_dri.so in the
2014 Jan 10
2
[PATCH] nouveau: add framebuffer validation callback
Fixes assertions when trying to attach textures to fbs with formats not
supported by the render engines.
See https://bugs.freedesktop.org/show_bug.cgi?id=73459
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
In a perfect world I'd have separate callbacks for depth and color, but given
the list of supported values, I don't think this matters. Also I used
2007 Sep 16
5
"rake spec:doc" returns NO NAME (due to --dry-run) for each specify block
I went ahead and moved to the trunk versions of RSpec and Spec:Rails because
I wanted to try out the new Story Runner feature. However, when I tried to
do "rake spec:doc", I got the following:
AccountController
- NO NAME (Because of --dry-run)
AccountHelper
- NO NAME (Because of --dry-run)
User (in general)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME
2010 Feb 16
1
Build failure in Mesa
Hi,
Ben Skeggs latest changes in Mesa cause a build failure (libdrm is latest git ...).
Thanks.
Johannes
gmake[3]: Entering directory `/usr/src/packages/BUILD/Mesa/src/mesa/drivers'
gmake[4]: Entering directory `/usr/src/packages/BUILD/Mesa/src/mesa/drivers/dri'
sed -e 's, at INSTALL_DIR@,/usr,' -e 's, at INSTALL_LIB_DIR@,/usr/lib,' -e 's, at
2007 May 22
3
rspec_on_rails'' spec:doc and dry runs
In rspec_on_rails, the spec:doc task uses --dry-run, which doesn''t
jive well with rspec''s ability to write docs for you.
For example, I use the rspec_expectation_matchers plugin from
spicycode.com (scanned for a name, didn''t find one =), and end up
writing specs like:
it { @ticket.should validate_presence_of(:name) }
Which results in specdocs such as:
Ticket
2014 Feb 13
2
[PATCH] nouveau: fix chipset checks for nv1a by using the oclass instead
Commit f4ebcd133b9 ("dri/nouveau: NV17_3D class is not available for
NV1a chipset") fixed this partially by using the correct 3d class.
However there were a lot of checks left over comparing against the
chipset.
Reported-and-tested-by: John F. Godfrey <jfgodfrey at gmail.com>
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
I guess I didn't have to change the
2009 Jul 21
2
Split plot analysis problems
Hello,
I would be very grateful if someone could give me a hand with my split
plot design problems.
So here is my design :
I am studying the crossed-effects of water (wet/dry) and mowing
(mowed/not-mowed = nm) on plant height (PH) within 2 types of plant
communities (Xerobromion and Mesobromion) :
- Within each type of communities, I have localised 4 blocks
- In each block, I have defined
2016 Jun 30
1
[Mesa-dev] nouveau_drv_video.so ?
Hi poma,
Seems like you're missed your question. "nouveau_drv_video.so ?" does
not mean much I'm afraid :-(
On 30 June 2016 at 11:03, poma <pomidorabelisima at gmail.com> wrote:
> On 30.06.2016 08:27, Xiang, Haihao wrote:
>>
>>
>> Are you using VA-API on X11? libva gets the driver name from Xserver,
>> it is nouveau for you. so libva tries to
2020 Mar 10
3
Question/comment about -n (dry run) flag of rsync
Rsync is a remarkably handy tool that I use virtually every day.
But there is one thing about rsync that drives me totally crazy.
Under the -n (dry run) flag, rsync seems to produce exactly the same output
as without that flag.
I cannot tell you how many times I sit and scratch my head long and
hard,after I discover that my intended rsync operations did not actually
happen. Until I finally
2009 Mar 25
1
Requesting help with lattice again
Hello, this is a request for assistance that I submitted earlier, this time
with the dataset. My mistake for taking up bandwidth. I've also rephrased
the question to address an additional concern.
I'm working on a windows XP machine with R 2.8.1
1). I'd like a barchart (or other lattice type display) HSI ~ of the three
factors (Region, Scenario and HydroState).
However
2015 Nov 04
3
NOUVEAU(0): DRI3 on EXA enabled
On 04.11.2015 11:57, Martin Peres wrote:
> On 02/11/15 08:28, poma wrote:
>> An interesting results.
>>
>> DRI2:
>>
>> $ vblank_mode=0 glxgears
>> ATTENTION: default value of option vblank_mode overridden by environment.
>> 6321 frames in 5.0 seconds = 1264.103 FPS
>> 6380 frames in 5.0 seconds = 1275.943 FPS
>> 6369 frames in 5.0 seconds =
2014 Jan 14
0
[PATCH] nouveau: add framebuffer validation callback
Ilia Mirkin <imirkin at alum.mit.edu> writes:
> Fixes assertions when trying to attach textures to fbs with formats not
> supported by the render engines.
>
> See https://bugs.freedesktop.org/show_bug.cgi?id=73459
>
> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
> ---
Hi Ilia,
>
> In a perfect world I'd have separate callbacks for depth and
2016 Jun 30
0
[Mesa-dev] nouveau_drv_video.so ?
On 30.06.2016 08:27, Xiang, Haihao wrote:
>
>
> Are you using VA-API on X11? libva gets the driver name from Xserver,
> it is nouveau for you. so libva tries to load nouveau_drv_video.so.
> You can create a symlink for nouveau pointing to a available driver or
> just ignore the message because you have gallium_drv_video.so now.
>
> Thanks
> Haihao
>
In
2005 Dec 05
2
Re: [users] CentOS 4.2 dag repo problem.
Hello,
It would be nice if we could get a full list of packages which have a wrong
sha1 checksum. I don't have the bandwidth for a full mirror of all of Dag's
rpms and i also don't have shell access to such a mirror. So a small
request for a mirror admin:
The following checks the files repodata/*.xml.gz against the sha1 sums in
repomd.xml and checks the RPMS/*.rpm files against
2010 Jan 05
1
Assertion failure in gallium on nv50
I upgraded mesa, libdrm, xf86-video-nouveau and the DRM module to
latest git recently (previously I had git versions from Dec 22). Now,
when I try to run a simple GL program with the DRI driver, it fails:
glxgears: /usr/include/nouveau/nouveau_pushbuf.h:135: BIND_RING:
Assertion `0' failed.
The old, previously working build of mesa and the DRI driver also
failed, which makes me think the
2012 Jan 26
1
lattice panels with grouped extra data as text?
I have a problem with including extra data in a lattice graphic. I am
trying to put some calculated values in an extra column of a boxplot. A
minimal example should show what I am trying to do:
foo <- data.frame(
Treatment=rnorm(1:12,2),