similar to: [PATCH v2 1/3] device: use the correct mmio size when mapping

Displaying 20 results from an estimated 700 matches similar to: "[PATCH v2 1/3] device: use the correct mmio size when mapping"

2020 Apr 17
2
[PATCH 1/3] device: use the correct mmio size when mapping
Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++
2020 Apr 28
3
[PATCH v3 1/3] device: rework mmio mapping code to get rid of second map
Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..37589f365 100644 ---
2020 Oct 13
3
[PATCH] drm/nouveau/device: fix changing endianess code to work on older GPUs
With this we try to detect if the endianess switch works and assume LE if not. Suggested by Ben. Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") --- .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c
2020 Apr 28
0
[PATCH v3 2/3] device: detect if changing endianness failed
v2: relax the checks a little Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 37589f365..c732074bf 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++
2020 Oct 13
0
[PATCH] drm/nouveau/device: fix changing endianess code to work on older GPUs
On Tue, Oct 13, 2020 at 8:01 AM Karol Herbst <kherbst at redhat.com> wrote: > > With this we try to detect if the endianess switch works and assume LE if > not. Suggested by Ben. > > Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") > --- > .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- > 1 file
2020 Oct 05
2
[PATCH] device: return error for unknown chipsets
Previously the code relied on device->pri to be NULL and to fail probing later. We really should just return an error inside nvkm_device_ctor for unsupported GPUs. Fixes: 24d5ff40a732 ("drm/nouveau/device: rework mmio mapping code to get rid of second map") Signed-off-by: Karol Herbst <kherbst at redhat.com> Cc: dann frazier <dann.frazier at canonical.com> ---
2016 Dec 12
2
[PATCH] drm/nouveau: fix unknown chipset for GTX 1060
Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it only gives VGA resolution on screen. Use the same chipset as nv134 then it shows FullHD. This commit copies fields from nv134_chipset to nv136_chipset for GTX 1060. Signed-off-by: Chris Chiu <chiu at endlessm.com> --- drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 29 +++++++++++++++++++++++ 1 file changed, 29
2020 Oct 06
1
[PATCH] device: return error for unknown chipsets
On Mon, Oct 05, 2020 at 03:52:30PM +0200, Karol Herbst wrote: > Previously the code relied on device->pri to be NULL and to fail probing > later. We really should just return an error inside nvkm_device_ctor for > unsupported GPUs. > > Fixes: 24d5ff40a732 ("drm/nouveau/device: rework mmio mapping code to get rid of second map") > Signed-off-by: Karol Herbst
2020 Oct 06
1
[PATCH] device: return error for unknown chipsets
On Tue, Oct 06, 2020 at 06:46:35PM +0200, Karol Herbst wrote: > On Tue, Oct 6, 2020 at 6:43 PM dann frazier <dann.frazier at canonical.com> wrote: > > > > On Mon, Oct 05, 2020 at 03:52:30PM +0200, Karol Herbst wrote: > > > Previously the code relied on device->pri to be NULL and to fail probing > > > later. We really should just return an error inside
2015 Jan 29
28
[Bug 88868] New: PowerPC e5500, kernel crash, GT520, GT610
https://bugs.freedesktop.org/show_bug.cgi?id=88868 Bug ID: 88868 Summary: PowerPC e5500, kernel crash, GT520, GT610 Product: xorg Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at
2017 Feb 14
1
[PATCH] drm/nouveau/core: recognise GP107 chipset
From: Chris Chiu <chiu at endlessm.com> This new graphics card was failing to initialize with nouveau due to an "unknown chipset" error. Copy the GP106 configuration and rename for GP107/NV137. We don't know for certain that this is fully correct, but brief desktop testing suggests this is working fine. Signed-off-by: Chris Chiu <chiu at endlessm.com> Signed-off-by:
2015 Oct 07
2
Chipset & Family
dmesg -t | grep -i nvidia nouveau 0000:02:00.0: NVIDIA G98 (098200a2) input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input6 input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input7 input: HDA NVidia Line as /devices/pci0000:00/0000:00:07.0/sound/card0/input8 input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:07.0/sound/card0/input9
2015 Oct 06
2
Chipset & Family
Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only
2020 Oct 09
3
nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian
On Fri, Oct 9, 2020 at 5:54 PM Karol Herbst <kherbst at redhat.com> wrote: > > On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary <linux at zary.sk> wrote: > > > > Hello, > > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working: > > [ 0.000000] Linux version 5.9.0-rc8+ (zary at gsql) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian)
2008 Oct 22
1
NEW: COM32 module to alias
From: Gene Cumm <gene.cumm at gmail.com> alias.c: A simple COM32 module that allows the creation of an alias within the config for SYSLINUX, etc. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same
2004 Sep 01
1
[R/S] strange
Dear R and S People: I have run across something very strange. Here is a function that I wrote for R: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y){n2 - pmax(x,y)})) return(a) } and here is the R output: > y1 [1] 9 8 7 3 6 > source("boot1.R") > boot1(y=y1,p=4) [,1] [,2]
2013 Dec 16
1
extlinux and btrfs
I am a relative newcomer to using extlinux. I am running Fedora 20 which means I am using syslinux 4.05. When I noticied that all of your documentation said that booting off ext234 and btrfs was supported, I gave it a try. Indeed, this does work with the boot files and the extlinux directory installed into the btrfs (root) volume. Has any thought been given to supporting supporting
2006 Mar 29
2
GRUB does not boot FreeBSD after installworld ...
HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no
2015 Jun 15
3
Two partitions with samd UUID??
I seem to have partitions on two different disks with the same UUID: [tim at helen ~]$ sudo blkid /dev/sda2 /dev/sda2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" [tim at helen ~]$ sudo blkid /dev/sdb2 /dev/sdb2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" This is
2012 Feb 08
1
How indices calculated in package "boot"
Hi,there, I am using R package "boot" to bootstrap. I have one question here: does anybody possibly know how the boot package generates the "indices" which is used in the statistic function? I thought "indices = sample(data, replace=TRUE)", but when I replaced "indices" with this command and used "boot", I got different results. Specifically,