similar to: Is Asterisk suitable for this use?

anyone have a recommendation for a place I can buy cheap motherboards that supports those 64-bit 3.3 volt PCI slots for the T100P ? I can't find them at Fry's or anywhere locally. All I can find online is dual processor server boards that are overkill for this application. I would like to use a P3/ P4/ AMD single processor. No Xeons or dual processor junk. Anyone know why digium

there is a field in the voltage table which tells us if the VIDs are taken from the entries or calculated through the header v2: don't break older versions of the table Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/include/nvkm/subdev/bios/volt.h | 5 +-- drm/nouveau/nvkm/subdev/bios/volt.c | 47 ++++++++++++++++-------------

info.min and info.max doesn't always represent the actual voltage range we can use. Do the same as with the entry based volting. Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors in sensors. Signed-off-by: Karol Herbst <karolherbst at gmail.com> --- drm/nouveau/nvkm/subdev/volt/base.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)

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

GF117 appears to use the same register as GK104 (but still with the general Fermi readout mechanism). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108980 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- v1 -> v2: split out different regid into separate file. .../drm/nouveau/include/nvkm/subdev/volt.h | 1 + .../gpu/drm/nouveau/nvkm/engine/device/base.c | 2 +-

Hello Vince, One minor question inline. Op 28-11-14 om 12:13 schreef Vince Hsu: > The voltage value are calculated by the hardware characterized > result. > > Signed-off-by: Vince Hsu <vinceh at nvidia.com> > --- > > Resend this patch with the fuse change and proper patch prefix > per Thierry's request. > > drm/Kbuild | 1 + >

On 21/03/16 18:16, Karol Herbst wrote: > these entries specify a maximum voltage nvidia never exceeds, we shouldn't do > that, too. > > Signed-off-by: Karol Herbst <nouveau at karolherbst.de> > --- > drm/nouveau/include/nvkm/subdev/bios/vmap.h | 2 ++ > drm/nouveau/include/nvkm/subdev/volt.h | 2 ++ > drm/nouveau/nvkm/subdev/bios/vmap.c | 5

Doing direct 64 bit divisions in kernel code leads to references to undefined symbols on 32 bit architectures. Replace such divisions with calls to div64_s64 to make the module usable on 32 bit archs. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drm/nouveau/nvkm/subdev/volt/base.c | 6 +++--- lib/include/nvif/os.h | 1 + 2 files changed, 4 insertions(+), 3

Loris, thank you thank you so much!!! do you know which CRAN mirror i select? There are loads - all related to various countries.. so appreciate the help Jenny Jenny Coetzee (PhD Candidate) Head of Prevention in Key Populations & Head of the Soweto Sex Worker Project Perinatal HIV Research Unit (PHRU) New Nurses Home Chris Hani Baragwanath Academic Hospital Soweto B: +27 11 989 9821 M:

On 18/04/16 22:13, Karol Herbst wrote: > I am sure that those are a bit different, but while testing the biggest error > compared to nvidia was -1.5%. Is this still true? I thought we were *much* closer now. > > Without this change we are most of the time around 10% below nvidias voltage, > so this change causes no harm and improves the situation a lot already. Yeah, this is

On a very few GPUs with the voltage table version 0x50 we have to read out the VIDs out of the entries of the table, where all the other gpus are either PWM based or get a base and a step voltage out of the table header. Currently nouveau tried to autodetect this and actually doesn't parse the entries. This Series adds two things: 1. It parses the entries 2. It decides upon a field in the

Hello Vince, Op 28-11-14 om 12:57 schreef Vince Hsu: > Hi Roy, > > On 11/28/2014 07:25 PM, Roy Spliet wrote: >> Hello Vince, >> >> One minor question inline. >> >> Op 28-11-14 om 12:13 schreef Vince Hsu: >>> The voltage value are calculated by the hardware characterized >>> result. >>> >>> Signed-off-by: Vince Hsu

With these both patches, most of the kepler cards should be able to reclock their core clock without issues. These patches should be tested carefully among nouveau devs, so that these don't break reclocking on other cards (especially Teslas). Particularly the second one might break reclocking here and there. Karol Herbst (2): bios/volt: handle voltage table version 0x50 with 0ed header

Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maarten Lankhorst <maarten.lankhorst at linux.intel.com> Signed-off-by:

Hi, Need to get an answer to the following. I find the naming to be little redundant regarding the 'input.transfer.boost.low - hige'. The same goes for input.transfer.trim.low - high. As I find it, there is only one point where the boost or buck (trim) kicks in. Let's say that the nominal voltage is 230 volt, then we have a input.transfer.boost point on say 220 volt. If the

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/volt/gk20a.c:49: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst drivers/gpu/drm/nouveau/nvkm/subdev/volt/gk20a.c:62: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/volt/gk20a.c:49: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst drivers/gpu/drm/nouveau/nvkm/subdev/volt/gk20a.c:62: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer

The first patch is also part of my reclocking series Karol Herbst (2): volt: save the voltage range we are able to set hwmon: add in_min and in_max drm/nouveau/include/nvkm/subdev/volt.h | 3 +++ drm/nouveau/nouveau_hwmon.c | 36 ++++++++++++++++++++++++++++++++++ drm/nouveau/nvkm/subdev/volt/base.c | 14 ++++++++++++- 3 files changed, 52 insertions(+), 1 deletion(-) --

I've splitted my big series between the part which actually fixes the engine reclocking bits and the part handling voltage/clock updates on temperature change, so that the more reviewed parts can be merged in faster. This series fixes a lot of Engine reclocking issues found on Fermi, Kepler and all Maxwell generation GPUs. It does _not_ fix memory reclocking on Fermi. It mostly contains of

> .expand_R_libs_env_var("poof/%p/%v") [1] "poof/x86_64-w64-mingw32/3.4" Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Jan 12, 2018 at 4:49 AM, Loris Bennett <loris.bennett at fu-berlin.de> wrote: > Hi, > > When I install a package as a non-root user, it gets saved in a path > such as > > ~/R/x86_64-unknown-linux-gnu-library/3.4 >