similar to: NVIDIA dropping support for older hardware (G8xxx, G9xxx and GT2xx chipsets)

--- man/nouveau.man | 9 ++++++++- src/nv_driver.c | 8 ++++++-- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 07d53c8..4878f24 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -63,7 +63,14 @@ GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119 GK104, GK106, GK107, GK110, GK208 .TP 22 .B GeForce GTX 750 -GM107 +GM107,

Builds upon the existing NVIDIA 16Bx2 block linear format modifiers by adding more "fields" to the existing parameterized DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier macro that allow fully defining a unique-across- all-NVIDIA-hardware bit layout using a minimal set of fields and values. The new modifier macro DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D is effectively backwards

On 01/03/16 23:38, Ilia Mirkin wrote: > On Tue, Mar 1, 2016 at 4:36 PM, Martin Peres <martin.peres at free.fr> wrote: >> On 26/02/16 17:19, Karol Herbst wrote: >>> currently there is no change, because nobody uses those macros yet, but >>> they >>> shouldn't stay broken >>> >>> Signed-off-by: Karol Herbst <nouveau at

On (06/19/19 02:07), Ilia Mirkin wrote: > On Wed, Jun 19, 2019 at 1:48 AM Sergey Senozhatsky > <sergey.senozhatsky.work at gmail.com> wrote: > > > > On (06/19/19 01:20), Ilia Mirkin wrote: > > > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky > > > <sergey.senozhatsky.work at gmail.com> wrote: > > > > > > > > On (06/14/19

Builds upon the existing NVIDIA 16Bx2 block linear format modifiers by adding more "fields" to the existing parameterized DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier macro that allow fully defining a unique-across- all-NVIDIA-hardware bit layout using a minimal set of fields and values. The new modifier macro DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D is effectively backwards

Builds upon the existing NVIDIA 16Bx2 block linear format modifiers by adding more "fields" to the existing parameterized DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier macro that allow fully defining a unique-across- all-NVIDIA-hardware bit layout using a minimal set of fields and values. The new modifier macro DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D is effectively backwards

On 10/15/19 7:19 AM, Daniel Vetter wrote: > On Mon, Oct 14, 2019 at 03:13:21PM -0700, James Jones wrote: >> Builds upon the existing NVIDIA 16Bx2 block linear >> format modifiers by adding more "fields" to the >> existing parameterized >> DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier >> macro that allow fully defining a unique-across- >>

On Tue, Oct 15, 2019 at 5:14 PM James Jones <jajones at nvidia.com> wrote: > > On 10/15/19 7:19 AM, Daniel Vetter wrote: > > On Mon, Oct 14, 2019 at 03:13:21PM -0700, James Jones wrote: > >> Builds upon the existing NVIDIA 16Bx2 block linear > >> format modifiers by adding more "fields" to the > >> existing parameterized > >>

On Mon, Oct 14, 2019 at 03:13:21PM -0700, James Jones wrote: > Builds upon the existing NVIDIA 16Bx2 block linear > format modifiers by adding more "fields" to the > existing parameterized > DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier > macro that allow fully defining a unique-across- > all-NVIDIA-hardware bit layout using a minimal > set of fields and values.

Greetings CentOS users, I have run into a hardware issue with the Intel 965 chipset. It appears that the latest kernel doesn't support the Marvell PATA controller. I can kickstart the computer, but after the OS is installed the DVD drive can't be accessed. There are patches against 2.6.18 for the Marvell PATA controller here: http://lkml.org/lkml/2006/10/16/157 There is bug

Greetings. HP claims RHEL 4 supports their servers with the Intel 3000 and 5000 chipsets. Has anyone had any trouble/success building machines that use this? For example, CentOS 4.4 on http://www.supermicro.com/products/system/1U/5015/SYS-5015M-T+.cfm Thx. Mike -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 30/07/13 21:39, Christ-Jan Wijtmans wrote: > Hi, my apologies if this is the wrong place to post this. > I had the desire to turn on or off support for certain chipsets. > Because i felt like the nouveau drivers are (relatively) quite large and > depends on some kernel code that would only be used for certain chipsets. > I will take some time this week to see how this is coded

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 nvkm_device_ctor for > > unsupported GPUs. > > > > Fixes: 24d5ff40a732

Hello all, Anybody know of any good and reliable AMD AM2 socket motherboards with SATA chipsets that support NCQ such as SIL3124, NForce 570 Ultra and offer six or more SATA channels?

Hi. I want run Centos 5.5 with mobo ASUS M4A88TD-V Evo/USB3 which have AMD chipset 880G/SB850 Any idea, if kernel in centos 5.5 supports this chipset and SATA HDD will be recognized during install process ? Best regards, I.Piasecki

It's time to purchase hardware again, and I'm going through the usual "of that which is on the market, what will CentOS run without leaving new hardware collecting dust for a year"? I'm looking at a number of commodity-grade machines (ie: desktop grade will suffice) with reasonably fast CPUs and able to use at least 8GB each (preferably 32GB). These will be deployed as

Hi All, I found it very difficult to get Xen-3.1 up on a a machine with Intel''s ICH9 family of disk controllers :-(. Is the ICH9 support really there in xen-3.2 ? I tried but was not successful in booting even xen-3.2 from xen.org. Did anyone have a success? Or any help on what extra config options I need to pass while compiling a domain0 from xen sources? Thanks, -- Pradeep Singh

On 30/07/2013 18:43, Ilia Mirkin wrote: > On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote: >> On 30/07/13 21:39, Christ-Jan Wijtmans wrote: >>> Hi, my apologies if this is the wrong place to post this. >>> I had the desire to turn on or off support for certain chipsets. >>> Because i felt like the nouveau drivers are

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

On 31/07/2013 11:03, Ilia Mirkin wrote: > On Wed, Jul 31, 2013 at 10:44 AM, Martin Peres <martin.peres at free.fr> wrote: >> On 30/07/2013 18:43, Ilia Mirkin wrote: >>> On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com> >>> wrote: >>>> On 30/07/13 21:39, Christ-Jan Wijtmans wrote: >>>>> Hi, my apologies if