search for: 36468

I have a no-windows Wine configuration. What happens if I install an application that a.o. adds a module to the Windows Control Panel? Is there a fake Control Panel for this?

I have been fighting with a kernel swapping bug for some time that was present in RH9 and carried over to RHEL 3 and hence CentOS. There is a beta U$ kernel and i was wondering would i break my system installing this beta U$ kernel? Also how would i go about installing this kernel? Is it a simple RPM command argument? Bugzilla report:

...0.01 1.171 0 4.21 0.01 0.827 0 4.74 0.01 0.372 0 > version _ platform x86_64-unknown-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu status Under development (unstable) major 2 minor 3.0 year 2005 month 11 day 25 svn rev 36468 language R Speed improves when the number of 'partial' indices is small, but even for 10 indices plain 'sort' is faster. Am I missing something? I haven't checked if NA's make a difference or if there might be memory usage issues, but even so, could 'quantile' at...

...; + +struct cvb_coef { + int c0; + int c1; + int c2; + int c3; + int c4; + int c5; +}; + +struct gk20a_volt_priv { + struct nouveau_volt base; + struct regulator *vdd; +}; + +const struct cvb_coef gk20a_cvb_coef[] = { + /* MHz, c0, c1, c2, c3, c4, c5 */ + /* 72 */ { 1209886, -36468, 515, 417, -13123, 203}, + /* 108 */ { 1130804, -27659, 296, 298, -10834, 221}, + /* 180 */ { 1162871, -27110, 247, 238, -10681, 268}, + /* 252 */ { 1220458, -28654, 247, 179, -10376, 298}, + /* 324 */ { 1280953, -30204, 247, 119, -9766, 304}, + /* 396 */ { 1344547, -31777, 24...

...; + +struct cvb_coef { + int c0; + int c1; + int c2; + int c3; + int c4; + int c5; +}; + +struct gk20a_volt_priv { + struct nouveau_volt base; + struct regulator *vdd; +}; + +const struct cvb_coef gk20a_cvb_coef[] = { + /* MHz, c0, c1, c2, c3, c4, c5 */ + /* 72 */ { 1209886, -36468, 515, 417, -13123, 203}, + /* 108 */ { 1130804, -27659, 296, 298, -10834, 221}, + /* 180 */ { 1162871, -27110, 247, 238, -10681, 268}, + /* 252 */ { 1220458, -28654, 247, 179, -10376, 298}, + /* 324 */ { 1280953, -30204, 247, 119, -9766, 304}, + /* 396 */ { 1344547, -31777, 24...

...3; > + int c4; > + int c5; > +}; > + > +struct gk20a_volt_priv { > + struct nouveau_volt base; > + struct regulator *vdd; > +}; > + > +const struct cvb_coef gk20a_cvb_coef[] = { > + /* MHz, c0, c1, c2, c3, c4, c5 */ > + /* 72 */ { 1209886, -36468, 515, 417, -13123, 203}, > + /* 108 */ { 1130804, -27659, 296, 298, -10834, 221}, > + /* 180 */ { 1162871, -27110, 247, 238, -10681, 268}, > + /* 252 */ { 1220458, -28654, 247, 179, -10376, 298}, > + /* 324 */ { 1280953, -30204, 247, 119, -9766, 304}, > + /* 396...

Some Tegra drivers might be complied as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> --- v2: add more description why we need this patch drivers/soc/tegra/fuse/fuse-tegra.c | 1

...t; + >> +struct gk20a_volt_priv { >> + struct nouveau_volt base; >> + struct regulator *vdd; >> +}; >> + >> +const struct cvb_coef gk20a_cvb_coef[] = { >> + /* MHz, c0, c1, c2, c3, c4, c5 */ >> + /* 72 */ { 1209886, -36468, 515, 417, -13123, 203}, >> + /* 108 */ { 1130804, -27659, 296, 298, -10834, 221}, >> + /* 180 */ { 1162871, -27110, 247, 238, -10681, 268}, >> + /* 252 */ { 1220458, -28654, 247, 179, -10376, 298}, >> + /* 324 */ { 1280953, -30204, 247, 119,...

Signed-off-by: Vince Hsu <vinceh at nvidia.com> --- nvkm/subdev/volt/base.c | 67 ++++++++++++++++++++++++++++--------------------- 1 file changed, 38 insertions(+), 29 deletions(-) diff --git a/nvkm/subdev/volt/base.c b/nvkm/subdev/volt/base.c index 32794a999106..26ccd8df193f 100644 --- a/nvkm/subdev/volt/base.c +++ b/nvkm/subdev/volt/base.c @@ -101,6 +101,41 @@ nouveau_volt_set_id(struct

Some Tegra drivers might be compiled as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> Acked-by: Alexandre Courbot <acourbot at nvidia.com> Acked-by: Thierry Reding <treding

Some Tegra drivers might be compiled as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> Acked-by: Alexandre Courbot <acourbot at nvidia.com> Acked-by: Thierry Reding <treding

...e/Benchmarks/VersaBench/bmm/bmm                                | > 0.0199 2896     0.0100      *                0.0300      |    2.34    2.35 >  2.36 *           2.39 | 1.00    0.99    n/a          n/a > MultiSource/Benchmarks/VersaBench/dbms/dbms                              | > 0.1200 36468    0.2500      *                0.2400      |    2.34    2.23 >  2.17 *           2.35 | 1.05    1.08    n/a          n/a > MultiSource/Benchmarks/VersaBench/ecbdes/ecbdes                          | > 0.0599 9740     0.0200      *                0.0200      |    2.87    2.91 >  2.77 *  ...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

...rsaBench/bmm/ > bmm | 0.0199 2896 0.0100 > * 0.0300 | 2.34 2.35 2.36 * > 2.39 | 1.00 0.99 n/a n/a > MultiSource/Benchmarks/VersaBench/dbms/ > dbms | 0.1200 36468 0.2500 > * 0.2400 | 2.34 2.23 2.17 * > 2.35 | 1.05 1.08 n/a n/a > MultiSource/Benchmarks/VersaBench/ecbdes/ > ecbdes | 0.0599 9740 0.0200 > * 0.0200 | 2.87...

This series does some refactoring in the GK20A's volt and clk drivers (fixing a few things while we are at it) to let GM20B benefit from the GK20A's logic with which it is compatible. GM20B is capable of more sophisticated (and power-efficient) reclocking which will follow later. Even after this more fancy reclocking is merged, the present logic will remain used in the lowest speedo of

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,