Re: [Nouveau] [nouveau-drm] failed to set mode on crtc
Yes, your patch works with current nouveau-drm very well. Thank you. -- Najlepsza wyszukiwarka tanich lotow! Sprawdz http://linkint.pl/f27c3 ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] Optimus and Nvidia
I need to buy a Sager 5125 laptop immediately and I am concerned about the Optimus setup in this model. It comes with a Nvidia 330M/Intel Hybrid. I want to use this with Fedora 13. I do not care if I can switch. I just want it to work. I can also deal with only the onboard graphics working in linux. Do you think the HDMI output will work or I will need the 330M driver for that? I see nvidia has support for the 330M in their driver? Will this work? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] [patch v2] nouveau: unwind on load errors
Marcin Slusarz marcin.slus...@gmail.com writes:
On Fri, Jul 30, 2010 at 05:04:32PM +0200, Dan Carpenter wrote:
nuveau_load() just returned directly if there was an error instead of
^^ typo
releasing resources.
Signed-off-by: Dan Carpenter erro...@gmail.com
---
V2: updated to the nouveau git tree.
Thanks.
Reviewed-by: Marcin Slusarz marcin.slus...@gmail.com
Thanks, pushed to the nouveau kernel tree.
diff --git a/drivers/gpu/drm/nouveau/nouveau_state.c
b/drivers/gpu/drm/nouveau/nouveau_state.c
index ee3729e..cf16bfb 100644
--- a/drivers/gpu/drm/nouveau/nouveau_state.c
+++ b/drivers/gpu/drm/nouveau/nouveau_state.c
@@ -739,8 +739,10 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
int ret;
dev_priv = kzalloc(sizeof(*dev_priv), GFP_KERNEL);
-if (!dev_priv)
-return -ENOMEM;
+if (!dev_priv) {
+ret = -ENOMEM;
+goto err_out;
+}
dev-dev_private = dev_priv;
dev_priv-dev = dev;
@@ -750,8 +752,10 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
dev-pci_vendor, dev-pci_device, dev-pdev-class);
dev_priv-wq = create_workqueue(nouveau);
-if (!dev_priv-wq)
-return -EINVAL;
+if (!dev_priv-wq) {
+ret = -EINVAL;
+goto err_priv;
+}
/* resource 0 is mmio regs */
/* resource 1 is linear FB */
@@ -764,7 +768,8 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
if (!dev_priv-mmio) {
NV_ERROR(dev, Unable to initialize the mmio mapping.
Please report your setup to DRIVER_EMAIL \n);
-return -EINVAL;
+ret = -EINVAL;
+goto err_wq;
}
NV_DEBUG(dev, regs mapped ok at 0x%llx\n,
(unsigned long long)mmio_start_offs);
@@ -812,7 +817,8 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
break;
default:
NV_INFO(dev, Unsupported chipset 0x%08x\n, reg0);
-return -EINVAL;
+ret = -EINVAL;
+goto err_mmio;
}
NV_INFO(dev, Detected an NV%2x generation card (0x%08x)\n,
@@ -820,7 +826,7 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
ret = nouveau_remove_conflicting_drivers(dev);
if (ret)
-return ret;
+goto err_mmio;
/* Map PRAMIN BAR, or on older cards, the aperture withing BAR0 */
if (dev_priv-card_type = NV_40) {
@@ -834,7 +840,8 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
dev_priv-ramin_size);
if (!dev_priv-ramin) {
NV_ERROR(dev, Failed to PRAMIN BAR);
-return -ENOMEM;
+ret = -ENOMEM;
+goto err_mmio;
}
} else {
dev_priv-ramin_size = 1 * 1024 * 1024;
@@ -842,7 +849,8 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
dev_priv-ramin_size);
if (!dev_priv-ramin) {
NV_ERROR(dev, Failed to map BAR0 PRAMIN.\n);
-return -ENOMEM;
+ret = -ENOMEM;
+goto err_mmio;
}
}
@@ -857,9 +865,21 @@ int nouveau_load(struct drm_device *dev, unsigned long
flags)
/* For kernel modesetting, init card now and bring up fbcon */
ret = nouveau_card_init(dev);
if (ret)
-return ret;
+goto err_ramin;
return 0;
+
+err_ramin:
+iounmap(dev_priv-ramin);
+err_mmio:
+iounmap(dev_priv-mmio);
+err_wq:
+destroy_workqueue(dev_priv-wq);
+err_priv:
+kfree(dev_priv);
+dev-dev_private = NULL;
+err_out:
+return ret;
}
void nouveau_lastclose(struct drm_device *dev)
pgpoc4Uuc3uKd.pgp
Description: PGP signature
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 29415] New: Screen shutdown with Nvidia GeForce 9400M
https://bugs.freedesktop.org/show_bug.cgi?id=29415 Summary: Screen shutdown with Nvidia GeForce 9400M Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau@lists.freedesktop.org ReportedBy: saint...@gmail.com QAContact: xorg-t...@lists.x.org Created an attachment (id=37608) -- (https://bugs.freedesktop.org/attachment.cgi?id=37608) Xorg.0.log Attempting to use the latest nouveau driver with my Nvidia GeForce 9400M results in my screen switching off and/or displaying garbage. I use a Mac Mini (model late 2009) on an up-to-date Debian Testing with the latest (git) nouveau driver (as of today). The video card is a Nvidia GeForce 9400M (nVidia Corporation C79 [GeForce 9400] (rev b1)) connected via mini-diplayport - VGA to a CRT Iiyama Vision Master Pro 410. The minidisplay-port - VGA connector is apparently an active connector. The video card and the screen work fine under Mac OS X or with the vesa driver. In attachment is my syslog, Xorg.0.log, lspci, myvga.rom (card's BIOS dump) and because it is quite big, a link to the POST trace. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 29415] Screen shutdown with Nvidia GeForce 9400M
https://bugs.freedesktop.org/show_bug.cgi?id=29415 --- Comment #1 from saint...@gmail.com 2010-08-05 18:14:46 PDT --- Created an attachment (id=37609) -- (https://bugs.freedesktop.org/attachment.cgi?id=37609) syslog -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 29415] Screen shutdown with Nvidia GeForce 9400M
https://bugs.freedesktop.org/show_bug.cgi?id=29415 --- Comment #2 from saint...@gmail.com 2010-08-05 18:15:21 PDT --- Created an attachment (id=37610) -- (https://bugs.freedesktop.org/attachment.cgi?id=37610) lspci dump -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 29415] Screen shutdown with Nvidia GeForce 9400M
https://bugs.freedesktop.org/show_bug.cgi?id=29415 --- Comment #4 from saint...@gmail.com 2010-08-05 18:21:46 PDT --- Here is the link to the POST trace (logfile-deloopd.gz): http://dl.free.fr/d1hBw3kb9 This link will be valid for 30 days. After that I can re-upload it or send it to whoever is interested. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 29415] Screen shutdown with Nvidia GeForce 9400M
https://bugs.freedesktop.org/show_bug.cgi?id=29415 --- Comment #5 from Ben Skeggs skeg...@gmail.com 2010-08-05 18:31:15 PDT --- Can I see a nouveau kernel log with log_buf_len=1M drm.debug=14 nouveau.reg_debug=0x0200 3 in your boot options? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] nv vpe video decoder
Hello, I have my work on the nv vpe video decoder in a functional state. In case you didn't know this decoder accelerates mpeg2 video at the idct/mc level. I have verified that it works on nv40 hardware. I believe it works on nv30 hardware (and maybe some earlier hardware), but I cannot verify since I have none. I will reply with patches against the kernel, drm, ddx and mesa for your review. Any comments are welcome. An important note is that the performance isn't that great in my opinion. There is something preventing the nv vpe engine from rendering cmds at the same rate as the blob. Either caching or whatever. Jimmy Rentz ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH 2/4] drm: nv vpe
This patch includes all the relevant nv vpe drm support.
This patch applies against the latest drm.
The drm portion has a couple of classes that interface with the kernel
vpe layer:
* nouveau_vpe_channel class - Manages the drm vpe channel.
This includes open the vpe channel in the kernel, setting up the
pushbuf and each output surface. Right now I force the pushbuffer to be
allocated/managed from user-mode. This is performance reaons. However,
the kernel can always decline this.
* nouveau_vpe_pushbuf class - Manages the pushbuf.
This includes starting/ending cmd sequences, writing the cmds to the
pushbuf and firing.
Signed-off-by: Jimmy Rentz jb17bs...@gmail.com
diff --git a/include/drm/nouveau_drm.h b/include/drm/nouveau_drm.h
index a6a9f4a..c597c0a 100644
--- a/include/drm/nouveau_drm.h
+++ b/include/drm/nouveau_drm.h
@@ -79,6 +79,7 @@ struct drm_nouveau_gpuobj_free {
#define NOUVEAU_GETPARAM_CHIPSET_ID 11
#define NOUVEAU_GETPARAM_VM_VRAM_BASE12
#define NOUVEAU_GETPARAM_GRAPH_UNITS 13
+#define NOUVEAU_GETPARAM_PTIMER_TIME 14
struct drm_nouveau_getparam {
uint64_t param;
uint64_t value;
@@ -183,6 +184,52 @@ enum nouveau_bus_type {
struct drm_nouveau_sarea {
};
+/* VPE Supports mpeg2 only.*/
+struct drm_nouveau_vd_vpe_channel_alloc {
+ uint32_t width;
+ uint32_t height;
+ /* Used for user pushbuf access.
+* mmio access is not allowed so you still need to fire as normal.*/
+ uint32_t pushbuf_handle;
+};
+
+struct drm_nouveau_vd_vpe_channel_free {
+};
+
+#define NOUVEAU_VD_VPE_PUSHBUF_FIRE_FLAG_END_SEQUENCE 0x0001
+#define NOUVEAU_VD_VPE_PUSHBUF_FIRE_FLAG_UPDATE_DMA_POS 0x0002
+/* structure for surface.*/
+struct drm_nouveau_vd_vpe_surface {
+ uint32_t luma_handle;
+ uint32_t chroma_handle;
+ uint32_t surface_index;
+};
+
+/* This flag lets you turn off firing for a specific batch.
+ * This is needed in some cases to avoid locking up the decoder.*/
+#define NOUVEAU_VD_VPE_PUSHBUF_FIRE_BATCH_DO_NOT_FIRE 0x1000
+struct drm_nouveau_vd_vpe_pushbuf_fire {
+ /* [in] */
+ uint32_t nr_dwords;
+ uint64_t dwords;
+ uint32_t nr_batches;
+ uint64_t batches;
+ /* Surface[0] is always the target.*/
+ uint32_t nr_surfaces;
+ uint64_t surfaces;
+ uint32_t flags;
+ /* Needed when writing to the hw pushbuf from user space.
+* This also will perform a fire.*/
+ uint32_t dma_cur;
+ /* [out] */
+ uint32_t dma_free;
+};
+
+struct drm_nouveau_vd_vpe_surface_query {
+ uint32_t surface_index;
+ uint32_t is_busy;
+};
+
#define DRM_NOUVEAU_GETPARAM 0x00
#define DRM_NOUVEAU_SETPARAM 0x01
#define DRM_NOUVEAU_CHANNEL_ALLOC 0x02
@@ -195,5 +242,9 @@ struct drm_nouveau_sarea {
#define DRM_NOUVEAU_GEM_CPU_PREP 0x42
#define DRM_NOUVEAU_GEM_CPU_FINI 0x43
#define DRM_NOUVEAU_GEM_INFO 0x44
+#define DRM_NOUVEAU_VD_VPE_CHANNEL_ALLOC 0x49
+#define DRM_NOUVEAU_VD_VPE_CHANNEL_FREE 0x50
+#define DRM_NOUVEAU_VD_VPE_PUSHBUF_FIRE 0x51
+#define DRM_NOUVEAU_VD_VPE_SURFACE_QUERY 0x52
#endif /* __NOUVEAU_DRM_H__ */
diff --git a/nouveau/Makefile.am b/nouveau/Makefile.am
index de3f4df..5c148f1 100644
--- a/nouveau/Makefile.am
+++ b/nouveau/Makefile.am
@@ -19,7 +19,9 @@ libdrm_nouveau_la_SOURCES = \
nouveau_bo.c \
nouveau_resource.c \
nouveau_private.h \
- nouveau_reloc.c
+ nouveau_reloc.c \
+ nouveau_vpe_channel.c \
+ nouveau_vpe_pushbuf.c
libdrm_nouveaucommonincludedir = ${includedir}/nouveau
libdrm_nouveaucommoninclude_HEADERS = \
@@ -30,7 +32,10 @@ libdrm_nouveaucommoninclude_HEADERS = \
nouveau_pushbuf.h \
nouveau_bo.h \
nouveau_resource.h \
- nouveau_reloc.h
+ nouveau_reloc.h \
+ nouveau_vpe_channel.h \
+ nouveau_vpe_pushbuf.h \
+ nouveau_vpe_hw.h
libdrm_nouveauincludedir = ${includedir}/libdrm
diff --git a/nouveau/nouveau_vpe_channel.c b/nouveau/nouveau_vpe_channel.c
new file mode 100644
index 000..22092ae
--- /dev/null
+++ b/nouveau/nouveau_vpe_channel.c
@@ -0,0 +1,301 @@
+/*
+ * Copyright (C) 2010 Jimmy Rentz
+ * All Rights Reserved.
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining
+ * a copy of this software and associated documentation files (the
+ * Software), to deal in the Software without restriction, including
+ * without limitation the rights to use, copy, modify, merge, publish,
+ * distribute, sublicense, and/or sell copies of the Software, and to
+ * permit persons to whom the Software is furnished to do
[Nouveau] [PATCH 3/4] ddx: nv vpe
This patch includes all the relevant nv vpe ddx support.
This patch applies against the latest xf86-video-nouveau.
This is hooks up the XV blit adapter to be used for XvMC IDCT on
NV30/NV40 cards. This makes it possible to fallback to g3dvl XvMC
if nv vpe is in use.
Signed-off-by: Jimmy Rentz jb17bs...@gmail.com
diff --git a/src/nouveau_xv.c b/src/nouveau_xv.c
index d1f87c3..aa07193 100644
--- a/src/nouveau_xv.c
+++ b/src/nouveau_xv.c
@@ -2062,6 +2062,7 @@ NVInitVideo(ScreenPtr pScreen)
XF86VideoAdaptorPtr blitAdaptor = NULL;
XF86VideoAdaptorPtr textureAdaptor[2] = {NULL, NULL};
int num_adaptors;
+ bool create_vpe_xvmc = false;
/*
* Driving the blitter requires the DMA FIFO. Using the FIFO
@@ -2140,14 +2141,28 @@ NVInitVideo(ScreenPtr pScreen)
* associate with any/all adapters since VL doesn't depend on
Xv for color conversion. */
if (textureAdaptor[0]) {
- XF86MCAdaptorPtr *adaptorsXvMC =
xalloc(sizeof(XF86MCAdaptorPtr));
+ if (blitAdaptor ( (pNv-Architecture == NV_ARCH_30)
||
+ (pNv-Architecture == NV_ARCH_40) ) ) {
+ create_vpe_xvmc = true;
+ num_adaptors = 2;
+ }
+ else
+ num_adaptors = 1;
+
+ XF86MCAdaptorPtr *adaptorsXvMC = xalloc(num_adaptors *
sizeof(XF86MCAdaptorPtr));
if (adaptorsXvMC) {
adaptorsXvMC[0] = vlCreateAdaptorXvMC(pScreen,
textureAdaptor[0]-name);
+ if (create_vpe_xvmc)
+ adaptorsXvMC[1] =
vlCreateAdaptorXvMCVPE(pScreen, blitAdaptor-name);
+
if (adaptorsXvMC[0]) {
- vlInitXvMC(pScreen, 1, adaptorsXvMC);
+ vlInitXvMC(pScreen, num_adaptors,
adaptorsXvMC); vlDestroyAdaptorXvMC(adaptorsXvMC[0]);
+
+ if (num_adaptors 1)
+
vlDestroyAdaptorXvMC(adaptorsXvMC[1]); }
xfree(adaptorsXvMC);
diff --git a/src/vl_hwmc.c b/src/vl_hwmc.c
index d8d8860..800fc88 100644
--- a/src/vl_hwmc.c
+++ b/src/vl_hwmc.c
@@ -58,11 +58,30 @@ static XF86MCSurfaceInfoRec yv12_mpeg2_surface =
subpicture_list
};
+static XF86MCSurfaceInfoRec yv12_mpeg2_vpe_surface =
+{
+ FOURCC_YV12,
+ XVMC_CHROMA_FORMAT_420,
+ 0,
+ 2032,
+ 2032,
+ 2048,
+ 2048,
+ XVMC_IDCT | XVMC_MPEG_2,
+ XVMC_SUBPICTURE_INDEPENDENT_SCALING | XVMC_BACKEND_SUBPICTURE,
+ subpicture_list
+};
+
static XF86MCSurfaceInfoPtr surfaces[] =
{
(XF86MCSurfaceInfoPtr)yv12_mpeg2_surface
};
+static XF86MCSurfaceInfoPtr vpe_surfaces[] =
+{
+ (XF86MCSurfaceInfoPtr)yv12_mpeg2_vpe_surface
+};
+
static XF86ImageRec rgb_subpicture = XVIMAGE_RGB;
static XF86ImagePtr subpictures[] =
@@ -85,6 +104,21 @@ static XF86MCAdaptorRec adaptor_template =
(xf86XvMCDestroySubpictureProcPtr)NULL
};
+static XF86MCAdaptorRec vpe_adaptor_template =
+{
+ ,
+ 1,
+ vpe_surfaces,
+ 1,
+ subpictures,
+ (xf86XvMCCreateContextProcPtr)NULL,
+ (xf86XvMCDestroyContextProcPtr)NULL,
+ (xf86XvMCCreateSurfaceProcPtr)NULL,
+ (xf86XvMCDestroySurfaceProcPtr)NULL,
+ (xf86XvMCCreateSubpictureProcPtr)NULL,
+ (xf86XvMCDestroySubpictureProcPtr)NULL
+};
+
XF86MCAdaptorPtr vlCreateAdaptorXvMC(ScreenPtr pScreen, char
*xv_adaptor_name) {
XF86MCAdaptorPtradaptor;
@@ -110,6 +144,31 @@ XF86MCAdaptorPtr vlCreateAdaptorXvMC(ScreenPtr
pScreen, char *xv_adaptor_name) return adaptor;
}
+XF86MCAdaptorPtr vlCreateAdaptorXvMCVPE(ScreenPtr pScreen, char
*xv_adaptor_name) +{
+ XF86MCAdaptorPtradaptor;
+ ScrnInfoPtr pScrn;
+
+ assert(pScreen);
+ assert(xv_adaptor_name);
+
+ pScrn = xf86Screens[pScreen-myNum];
+ adaptor = xf86XvMCCreateAdaptorRec();
+
+ if (!adaptor)
+ {
+ xf86DrvMsg(pScrn-scrnIndex, X_ERROR, [XvMC.VPE]
Memory allocation failed.\n);
+ return NULL;
+ }
+
+ *adaptor = vpe_adaptor_template;
+ adaptor-name = xv_adaptor_name;
+
+ xf86DrvMsg(pScrn-scrnIndex, X_INFO, [XvMC.VPE] Associated
with %s.\n, xv_adaptor_name);
+
+ return adaptor;
+}
+
void vlDestroyAdaptorXvMC(XF86MCAdaptorPtr adaptor)
{
assert(adaptor);
diff --git a/src/vl_hwmc.h b/src/vl_hwmc.h
index 715120d..efb2d56 100644
--- a/src/vl_hwmc.h
+++ b/src/vl_hwmc.h
@@ -4,6 +4,7 @@
#include xf86xvmc.h
XF86MCAdaptorPtr vlCreateAdaptorXvMC(ScreenPtr pScreen, char
*xv_adaptor_name); +XF86MCAdaptorPtr vlCreateAdaptorXvMCVPE(ScreenPtr
pScreen, char *xv_adaptor_name); void
vlDestroyAdaptorXvMC(XF86MCAdaptorPtr adaptor); void
Re: [Nouveau] Optimus and Nvidia
On Thu, Aug 5, 2010 at 4:38 PM, Jason Long mailing.li...@octgsoftware.com wrote: I need to buy a Sager 5125 laptop immediately and I am concerned about the Optimus setup in this model. It comes with a Nvidia 330M/Intel Hybrid. I want to use this with Fedora 13. I do not care if I can switch. I just want it to work. I can also deal with only the onboard graphics working in linux. Do you think the HDMI output will work or I will need the 330M driver for that? I see nvidia has support for the 330M in their driver? Will this work? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau Last I heard I don't think Nvidia will support Optimus on Linux with their driver. As far as Nouveau and DRM playing nice with Optimus I think Dave Airlie had some interest in that but no access to hardware? I don't remember the details myself, maybe someone else can tell you more. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Optimus and Nvidia
(Use reply-all if you want people on the list to see your emails, your last two were only to me.) Google nvidia optimus linux and you'll find some info on the matter. The Nvidia driver does not support Optimus. As far as I know this means that it will not work with the 330M in an Optimus chipset because the 330M is hooked up to the Intel chip, it doesn't matter that the Nvidia driver supports regular 330Ms, this is not a regular 330M. Nouveau doesn't support it either until someone figures out how it works. As far as the Intel chip is concerned I don't know if the Intel driver will support it and just ignore the Optimus-related stuff. Maybe you should ask that on the Intel list. What the sales guy told you about turning it off doesn't matter. On Thu, Aug 5, 2010 at 11:24 PM, Jason Long mailing.li...@octgsoftware.com wrote: The NVIDIA GeForce GT 330M is supported by the propriety driver, but I do not know how is will work with the integrated Intel. On Thu, Aug 5, 2010 at 10:22 PM, Jason Long mailing.li...@octgsoftware.com wrote: It is a http://www.pctorque.com/sager-5125-gaming-computers.php with NVIDIA GeForce GT 330M with integrated Intel 4500 GMA. I am not really concerned about if Optimus works. I am mainly concerned about using the latest Fedora release. I do not even care if I have to use either the Intel of Nvidia card. I just want 1080p under Linux. Does anyone know what the options are? The sales guys said there was a switch to turn Optimus off. On Thu, Aug 5, 2010 at 10:08 PM, Younes Manton youne...@gmail.com wrote: On Thu, Aug 5, 2010 at 4:38 PM, Jason Long mailing.li...@octgsoftware.com wrote: I need to buy a Sager 5125 laptop immediately and I am concerned about the Optimus setup in this model. It comes with a Nvidia 330M/Intel Hybrid. I want to use this with Fedora 13. I do not care if I can switch. I just want it to work. I can also deal with only the onboard graphics working in linux. Do you think the HDMI output will work or I will need the 330M driver for that? I see nvidia has support for the 330M in their driver? Will this work? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau Last I heard I don't think Nvidia will support Optimus on Linux with their driver. As far as Nouveau and DRM playing nice with Optimus I think Dave Airlie had some interest in that but no access to hardware? I don't remember the details myself, maybe someone else can tell you more. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Optimus and Nvidia
Which intel list is that? I am assuming I can still run Linux in Virtual Box on a Windows 7 host. Is this correct? I did Google quite a bit, but I could only find people that were thinking about fixing, but not solutions or serious progress. I can deal with running running Linux virtually for a while. What are the chances that I will end up with a laptop that will never run Fedora native? On Thu, Aug 5, 2010 at 10:46 PM, Younes Manton youne...@gmail.com wrote: (Use reply-all if you want people on the list to see your emails, your last two were only to me.) Google nvidia optimus linux and you'll find some info on the matter. The Nvidia driver does not support Optimus. As far as I know this means that it will not work with the 330M in an Optimus chipset because the 330M is hooked up to the Intel chip, it doesn't matter that the Nvidia driver supports regular 330Ms, this is not a regular 330M. Nouveau doesn't support it either until someone figures out how it works. As far as the Intel chip is concerned I don't know if the Intel driver will support it and just ignore the Optimus-related stuff. Maybe you should ask that on the Intel list. What the sales guy told you about turning it off doesn't matter. On Thu, Aug 5, 2010 at 11:24 PM, Jason Long mailing.li...@octgsoftware.com wrote: The NVIDIA GeForce GT 330M is supported by the propriety driver, but I do not know how is will work with the integrated Intel. On Thu, Aug 5, 2010 at 10:22 PM, Jason Long mailing.li...@octgsoftware.com wrote: It is a http://www.pctorque.com/sager-5125-gaming-computers.php with NVIDIA GeForce GT 330M with integrated Intel 4500 GMA. I am not really concerned about if Optimus works. I am mainly concerned about using the latest Fedora release. I do not even care if I have to use either the Intel of Nvidia card. I just want 1080p under Linux. Does anyone know what the options are? The sales guys said there was a switch to turn Optimus off. On Thu, Aug 5, 2010 at 10:08 PM, Younes Manton youne...@gmail.com wrote: On Thu, Aug 5, 2010 at 4:38 PM, Jason Long mailing.li...@octgsoftware.com wrote: I need to buy a Sager 5125 laptop immediately and I am concerned about the Optimus setup in this model. It comes with a Nvidia 330M/Intel Hybrid. I want to use this with Fedora 13. I do not care if I can switch. I just want it to work. I can also deal with only the onboard graphics working in linux. Do you think the HDMI output will work or I will need the 330M driver for that? I see nvidia has support for the 330M in their driver? Will this work? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau Last I heard I don't think Nvidia will support Optimus on Linux with their driver. As far as Nouveau and DRM playing nice with Optimus I think Dave Airlie had some interest in that but no access to hardware? I don't remember the details myself, maybe someone else can tell you more. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
