Re: Pending MFC of drm updates
On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 I tested your patch on 2 different machines: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. 2) dual-Opteron 285/amd64 with a Radeon X1600 (RV530) Works, but no direct rendering yet. I guess this would eventually work with a newer xorg?! If it helps somehow I could test again with xorg-7.4. Thanks again for your work! Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 14:47 +0100, Uwe Laverenz wrote: On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 I tested your patch on 2 different machines: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. 2) dual-Opteron 285/amd64 with a Radeon X1600 (RV530) Works, but no direct rendering yet. I guess this would eventually work with a newer xorg?! If it helps somehow I could test again with xorg-7.4. new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch robert. Thanks again for your work! Uwe signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. --- Gary Jennejohn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 17:22 +0100, Gary Jennejohn wrote: On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. what is the pci id? Probably not, I think that is an r600 chipset, but AMD has released preliminary code, so it shouldn't be too much longer. robert. --- Gary Jennejohn signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 17:22 +0100, Gary Jennejohn wrote: On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. It should however support the latest Intel chipsets, and R500 and below AMD/ATI including the IGP chips (rs690 and rs485). If you have the garbled screen with pci based radeons, I have a patch for that also that isn't part of this MFC yet. The newer chips may also need the newer Xorg / Mesa bits, coming to a ports collection near you very soon. robert. --- Gary Jennejohn signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 robert. I've pulled this down and patched my install of FreeBSD 7.1-RELEASE. Whilst using a Radeon 9250 (R280?), I have no problems. There is also no apparent performance difference. The only issue I have seen occurs with my dual-monitor setup. Occasionally a window on the second monitor will decide to render its drop-down menus or other (overlay-based?) graphics on the primary monitor instead of where it should be. Restarting the application seems to clear this up. I have not seen this previously before applying your patch. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 11:57 -0500, Steve Polyack wrote: Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 robert. I've pulled this down and patched my install of FreeBSD 7.1-RELEASE. Whilst using a Radeon 9250 (R280?), I have no problems. There is also no apparent performance difference. The only issue I have seen occurs with my dual-monitor setup. Occasionally a window on the second monitor will decide to render its drop-down menus or other (overlay-based?) graphics on the primary monitor instead of where it should be. Restarting the application seems to clear this up. I have not seen this previously before applying your patch. Hrm, I'm not sure how that could be related... You might try rebuilding graphics/libdrm. That sounds like an framebuffer offset issue. robert. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Excellent! Thanks for your hard work on this, Robert! After updating my source to 7.1-RELEASE, I applied this patch and built and installed a new kernel and world. This went without problems. Starting X on a Sapphire Radeon X1650Pro works OK. XAA 2D accelleration works OK. The X logfile says that direct rendering is enabled, as is Xv. Mplayer works with Xv. But whenever I try to start a program that uses OpenGL (i.e. glxgears) I get the following message: unknown chip id 0x71c1, can't guess. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering :-( The same number shows in Xorg.0.log: snip (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x71c1) rev 158, Mem @ 0xe000/28, 0xfe9e/16, I/O @ 0xd000/8, BIOS @ 0xfe9c/17 snip (II) Loading extension XFree86-DGA snip (--) Chipset RV535 found snip (II) RADEONHD(0): Unknown card detected: 0x71C1:0x174B:0x0880. If - and only if - your card does not work or does not work optimally please contact radeo...@opensuse.org to help rectify this. Use the subject: 0x71C1:0x174B:0x0880: name of board and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV535 on an unidentified card (==) RADEONHD(0): Write-combining range (0xfe9e,0x1) was already clear (II) RADEONHD(0): Mapped IO @ 0xfe9e to 0x8006a2000 (size 0x0001) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0x0880 IOBaseAddress: 0xd000 Filename: 8C88GCSA.003 BIOS Bootup Message: A67120 RV535XT VO BIOS GDDR3 600E/700M snip (II) RADEONHD(0): Found libdri 5.4.0. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEONHD(0): Found libdrm 1.3.0. (II) RADEONHD(0): Found radeon drm 1.29.0. snip (II) RADEONHD(0): Output DVI-I_2/digital using initial mode 1280x1024 (II) RADEONHD(0): RandR 1.2 support enabled (==) RADEONHD(0): RGB weight 888 (==) RADEONHD(0): Default visual is TrueColor (==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEONHD(0): Using 1280x1280 Framebuffer with 1280 pitch (II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x8000 (size = 0x0064) (**) RADEONHD(0): Display dimensions: (376, 301) mm (**) RADEONHD(0): DPI set to (86, 108) snip (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync I wonder if the framebuffer size is OK? The screen is 1280x1024. That is probably why the DPI is wacky (should both be 86). Should I write the card in to opensuse.org? The card is a Sapphire Radeon X1650Pro. Additionally (but maybe unrelated), when I try to start tyr-glquake, it bombs with an X error: Callback: in_dgamouse ON X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 117 Current serial number in output stream: 118 The library libXxf86dga-1.0.2 is installed. I see Xorg loading the extension. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpi4zSgaW1tj.pgp Description: PGP signature
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 22:26 +0100, Roland Smith wrote: On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Excellent! Thanks for your hard work on this, Robert! After updating my source to 7.1-RELEASE, I applied this patch and built and installed a new kernel and world. This went without problems. Starting X on a Sapphire Radeon X1650Pro works OK. XAA 2D accelleration works OK. The X logfile says that direct rendering is enabled, as is Xv. Mplayer works with Xv. But whenever I try to start a program that uses OpenGL (i.e. glxgears) I get the following message: unknown chip id 0x71c1, can't guess. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering Yep, you need the updated xorg and mesa. We are getting ready to update the ports collection. I may build up a new patch in a little while. robert. :-( The same number shows in Xorg.0.log: snip (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x71c1) rev 158, Mem @ 0xe000/28, 0xfe9e/16, I/O @ 0xd000/8, BIOS @ 0xfe9c/17 snip (II) Loading extension XFree86-DGA snip (--) Chipset RV535 found snip (II) RADEONHD(0): Unknown card detected: 0x71C1:0x174B:0x0880. If - and only if - your card does not work or does not work optimally please contact radeo...@opensuse.org to help rectify this. Use the subject: 0x71C1:0x174B:0x0880: name of board and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV535 on an unidentified card (==) RADEONHD(0): Write-combining range (0xfe9e,0x1) was already clear (II) RADEONHD(0): Mapped IO @ 0xfe9e to 0x8006a2000 (size 0x0001) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0x0880 IOBaseAddress: 0xd000 Filename: 8C88GCSA.003 BIOS Bootup Message: A67120 RV535XT VO BIOS GDDR3 600E/700M snip (II) RADEONHD(0): Found libdri 5.4.0. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEONHD(0): Found libdrm 1.3.0. (II) RADEONHD(0): Found radeon drm 1.29.0. snip (II) RADEONHD(0): Output DVI-I_2/digital using initial mode 1280x1024 (II) RADEONHD(0): RandR 1.2 support enabled (==) RADEONHD(0): RGB weight 888 (==) RADEONHD(0): Default visual is TrueColor (==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEONHD(0): Using 1280x1280 Framebuffer with 1280 pitch (II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x8000 (size = 0x0064) (**) RADEONHD(0): Display dimensions: (376, 301) mm (**) RADEONHD(0): DPI set to (86, 108) snip (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync I wonder if the framebuffer size is OK? The screen is 1280x1024. That is probably why the DPI is wacky (should both be 86). Should I write the card in to opensuse.org? The card is a Sapphire Radeon X1650Pro. Additionally (but maybe unrelated), when I try to start tyr-glquake, it bombs with an X error: Callback: in_dgamouse ON X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 117 Current serial number in output stream: 118 The library libXxf86dga-1.0.2 is installed. I see Xorg loading the extension. Roland signature.asc Description: This is a digitally signed message part
Pending MFC of drm updates
I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 robert. -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Tue, 06 Jan 2009 12:36:20 -0500 Robert Noland rnol...@freebsd.org wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Applied fine to my RELENG_7 / amd64 system (freshly cvsup'ed and built yesterday): r...@kg-v2# uname -a FreeBSD kg-v2.kg4.no 7.1-STABLE FreeBSD 7.1-STABLE #1: Tue Jan 6 21:49:31 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 - except for the patch to sys/modules/drm/i915/Makefile: The text leading up to this was: -- |diff -uNrp -x .svn |sys/modules/drm/i915/Makefile /home/rnoland/freebsd/base/stable/7/sys/modules/drm/i915/Makefile |--- sys/modules/drm/i915/Makefile 2009-01-06 10:58:41.0 |-0500 ++ |+ /home/rnoland/freebsd/base/stable/7/sys/modules/drm/i915/Makefile |2008-12-10 21:48:19.0 -0500 -- Patching file Makefile using Plan A... Hunk #1 failed at 2. 1 out of 1 hunks failed--saving rejects to Makefile.rej Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/drm/drm/../../../dev/drm/ati_pcigart.c /usr/src/sys/modules/drm/drm/.. /../../dev/drm/drm_agpsupport.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_auth.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_bufs.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_context.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_dma.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drawable.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_fops.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_ioctl.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_irq.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_lock.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_memory.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_pci.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_scatter.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_sysctl.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_vm.c In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/ati_pcigart.c:37: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_agpsupport.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_auth.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_bufs.c:40: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_context.c:38: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_dma.c:42: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drawable.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c:41: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_fops.c:40: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_ioctl.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_irq.c:36: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_lock.c:53: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_memory.c:42: @/dev/drm/drmP.h:96:34: error:
Re: Pending MFC of drm updates
On Tue, Jan 6, 2009 at 6:24 PM, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: On Tue, 06 Jan 2009 12:36:20 -0500 Robert Noland rnol...@freebsd.org wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. : I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Applied fine to my RELENG_7 / amd64 system (freshly cvsup'ed and built yesterday): r...@kg-v2# uname -a FreeBSD kg-v2.kg4.no 7.1-STABLE FreeBSD 7.1-STABLE #1: Tue Jan 6 21:49:31 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 - except for the patch to sys/modules/drm/i915/Makefile: : Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile use: patch -p0 /dir/name/patchfile See the man page on patch. Scot. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Wed, 07 Jan 2009 01:24:57 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: I forgot to tell that I fixed the Makefile in sys/modules/drm/i915 manually. Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: Which is no wonder, because patch misplaced more files: r...@kg-v2# pwd /usr/src r...@kg-v2# ll *.c *c.orig *.h *h.orig -rw-r--r-- 1 root wheel 1650 Jan 7 01:09 drm_internal.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 drm_internal.h.orig -rw-r--r-- 1 root wheel 16455 Jan 7 01:09 i915_suspend.c -rw-r--r-- 1 root wheel 0 Jan 7 01:09 i915_suspend.c.orig -rw-r--r-- 1 root wheel 59118 Jan 7 01:09 radeon_microcode.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 radeon_microcode.h.orig Is ther a secret handshake to make patch put the files in their correct place? (Except for reading through the whole patchfile to determine if all touched filews are in the same directory.) For now I just mv'ed the files into place. Anyway, now the new kernel builds, installs and works correctly. It didn't pick up any drm, but I'm not sure that it should either. This machine[1] has a GeForce 8200 chipset. More info about FreeBSD on this machine here[2], including dmesgs before and after, etc. HTH References: 1) http://tingox.googlepages.com/asus_v2-m3n8200 2) http://tingox.googlepages.com/asus_v2-m3n8200_freebsd -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, Jan 6, 2009 at 7:17 PM, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: Is ther a secret handshake to make patch put the files in their correct place? (Except for reading through the whole patchfile to determine if all touched filews are in the same directory.) patch -p0 patchfile This will place the files into the correct locations. Patch with no '-p' option will first try to put the files in the path provided in the patch file, if the path exists, otherwise it places the files in the current directory. See the man page for patch. Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, 2009-01-06 at 12:36 -0500, Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 On the hardware below, I see no ill effects after applying the patch. Is there anything specific you would like tested or any additional information that I can provide? vgap...@pci0:0:2:0: class=0x03 card=0x201a17aa chip=0x27a28086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GU Express Integrated Graphics Controller' class = display subclass = VGA vgap...@pci0:0:2:1: class=0x038000 card=0x201a17aa chip=0x27a68086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GU Express Integrated Graphics Controller' class = display -- Alexandre Sunny Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, Jan 6, 2009 at 7:20 PM, Bernt Hansson be...@bah.homeip.net wrote: Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. Digital Rights Management. See: http://en.wikipedia.org/wiki/DRM_(computing). Cheers, -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Wed, 2009-01-07 at 04:20 +0100, Bernt Hansson wrote: Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. drm being the direct rendering kernel modules, required for most hardware acceleration. 3870 with radeonhd driver? robert. signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Tue, 2009-01-06 at 22:13 -0500, Alexandre Sunny Kovalenko wrote: On Tue, 2009-01-06 at 12:36 -0500, Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 On the hardware below, I see no ill effects after applying the patch. Is there anything specific you would like tested or any additional information that I can provide? Not really, the code has been running in -CURRENT for a while now, just looking to make sure that no new issues show up. thanks for testing. robert. vgap...@pci0:0:2:0: class=0x03 card=0x201a17aa chip=0x27a28086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GU Express Integrated Graphics Controller' class = display subclass = VGA vgap...@pci0:0:2:1: class=0x038000 card=0x201a17aa chip=0x27a68086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GU Express Integrated Graphics Controller' class = display signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Tue, 2009-01-06 at 19:49 -0800, Garrett Cooper wrote: On Tue, Jan 6, 2009 at 7:20 PM, Bernt Hansson be...@bah.homeip.net wrote: Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. Digital Rights Management. See: http://en.wikipedia.org/wiki/DRM_(computing). not at all. Direct Rendering Modules... robert. Cheers, -Garrett signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Wed, 2009-01-07 at 02:17 +0100, Torfinn Ingolfsen wrote: On Wed, 07 Jan 2009 01:24:57 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: I forgot to tell that I fixed the Makefile in sys/modules/drm/i915 manually. Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: Which is no wonder, because patch misplaced more files: r...@kg-v2# pwd /usr/src r...@kg-v2# ll *.c *c.orig *.h *h.orig -rw-r--r-- 1 root wheel 1650 Jan 7 01:09 drm_internal.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 drm_internal.h.orig -rw-r--r-- 1 root wheel 16455 Jan 7 01:09 i915_suspend.c -rw-r--r-- 1 root wheel 0 Jan 7 01:09 i915_suspend.c.orig -rw-r--r-- 1 root wheel 59118 Jan 7 01:09 radeon_microcode.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 radeon_microcode.h.orig Is ther a secret handshake to make patch put the files in their correct place? (Except for reading through the whole patchfile to determine if all touched filews are in the same directory.) For now I just mv'ed the files into place. Anyway, now the new kernel builds, installs and works correctly. It didn't pick up any drm, but I'm not sure that it should either. This machine[1] has a GeForce 8200 chipset. More info about FreeBSD on this machine here[2], including dmesgs before and after, etc. Nope, sorry no Nvidia support yet. nouveau is on my list to work on, but it's a long list... robert. HTH References: 1) http://tingox.googlepages.com/asus_v2-m3n8200 2) http://tingox.googlepages.com/asus_v2-m3n8200_freebsd signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Wed, 2009-01-07 at 01:24 +0100, Torfinn Ingolfsen wrote: On Tue, 06 Jan 2009 12:36:20 -0500 Robert Noland rnol...@freebsd.org wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Applied fine to my RELENG_7 / amd64 system (freshly cvsup'ed and built yesterday): r...@kg-v2# uname -a FreeBSD kg-v2.kg4.no 7.1-STABLE FreeBSD 7.1-STABLE #1: Tue Jan 6 21:49:31 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 patch is being uncooperative... I've rebuilt the patchfile to simplify this. With the updated patchfile you need to: cd /usr/src bzcat patchfile | patch -p0 robert. - except for the patch to sys/modules/drm/i915/Makefile: The text leading up to this was: -- |diff -uNrp -x .svn |sys/modules/drm/i915/Makefile /home/rnoland/freebsd/base/stable/7/sys/modules/drm/i915/Makefile |--- sys/modules/drm/i915/Makefile2009-01-06 10:58:41.0 |-0500 ++ |+ /home/rnoland/freebsd/base/stable/7/sys/modules/drm/i915/Makefile |2008-12-10 21:48:19.0 -0500 -- Patching file Makefile using Plan A... Hunk #1 failed at 2. 1 out of 1 hunks failed--saving rejects to Makefile.rej Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/drm/drm/../../../dev/drm/ati_pcigart.c /usr/src/sys/modules/drm/drm/.. /../../dev/drm/drm_agpsupport.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_auth.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_bufs.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_context.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_dma.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drawable.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_fops.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_ioctl.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_irq.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_lock.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_memory.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_pci.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_scatter.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_sysctl.c /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_vm.c In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/ati_pcigart.c:37: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_agpsupport.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_auth.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_bufs.c:40: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_context.c:38: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_dma.c:42: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drawable.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c:41: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_fops.c:40: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_ioctl.c:39: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or directory In file included from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_irq.c:36: @/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h:
Re: Pending MFC of drm updates
Robert Noland said the following on 2009-01-07 04:52: On Wed, 2009-01-07 at 04:20 +0100, Bernt Hansson wrote: Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. drm being the direct rendering kernel modules, required for most hardware acceleration. 3870 with radeonhd driver? Yes. Radeonhd. Tried radeon but then xfce didn't work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, Jan 06, 2009 at 11:09:58PM -0500, Robert Noland wrote: On Wed, 2009-01-07 at 02:17 +0100, Torfinn Ingolfsen wrote: On Wed, 07 Jan 2009 01:24:57 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: I forgot to tell that I fixed the Makefile in sys/modules/drm/i915 manually. Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: Which is no wonder, because patch misplaced more files: r...@kg-v2# pwd /usr/src r...@kg-v2# ll *.c *c.orig *.h *h.orig -rw-r--r-- 1 root wheel 1650 Jan 7 01:09 drm_internal.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 drm_internal.h.orig -rw-r--r-- 1 root wheel 16455 Jan 7 01:09 i915_suspend.c -rw-r--r-- 1 root wheel 0 Jan 7 01:09 i915_suspend.c.orig -rw-r--r-- 1 root wheel 59118 Jan 7 01:09 radeon_microcode.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 radeon_microcode.h.orig Is ther a secret handshake to make patch put the files in their correct place? (Except for reading through the whole patchfile to determine if all touched filews are in the same directory.) For now I just mv'ed the files into place. Anyway, now the new kernel builds, installs and works correctly. It didn't pick up any drm, but I'm not sure that it should either. This machine[1] has a GeForce 8200 chipset. More info about FreeBSD on this machine here[2], including dmesgs before and after, etc. Nope, sorry no Nvidia support yet. nouveau is on my list to work on, but it's a long list... robert. Any help that we mere mortals can provide other than sending you hardware? HTH References: 1) http://tingox.googlepages.com/asus_v2-m3n8200 2) http://tingox.googlepages.com/asus_v2-m3n8200_freebsd Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, 6 Jan 2009, Garrett Cooper wrote: On Tue, Jan 6, 2009 at 7:20 PM, Bernt Hansson be...@bah.homeip.net wrote: Robert Noland said the following on 2009-01-06 18:36: I am planning to merge most all of the drm from -CURRENT to releng_7 And what is DRM? My ATI HD 3870 works. Digital Rights Management. See: http://en.wikipedia.org/wiki/DRM_(computing). Not that DRM, this DRM: http://dri.freedesktop.org/wiki/DRM -Warren Block * Rapid City, South Dakota USA ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Wed, 2009-01-07 at 07:21 +0300, Yuri Pankov wrote: On Tue, Jan 06, 2009 at 11:09:58PM -0500, Robert Noland wrote: On Wed, 2009-01-07 at 02:17 +0100, Torfinn Ingolfsen wrote: On Wed, 07 Jan 2009 01:24:57 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: I forgot to tell that I fixed the Makefile in sys/modules/drm/i915 manually. Apparently patch gets confuseed when it finds a file with the same name in the current directory (which was /usr/src), or perhaps I don't know how to tell patch how to find the right file. I just did: cd /usr/src patch /dir/name/patchfile Anyway, a 'make kernel' fails: Which is no wonder, because patch misplaced more files: r...@kg-v2# pwd /usr/src r...@kg-v2# ll *.c *c.orig *.h *h.orig -rw-r--r-- 1 root wheel 1650 Jan 7 01:09 drm_internal.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 drm_internal.h.orig -rw-r--r-- 1 root wheel 16455 Jan 7 01:09 i915_suspend.c -rw-r--r-- 1 root wheel 0 Jan 7 01:09 i915_suspend.c.orig -rw-r--r-- 1 root wheel 59118 Jan 7 01:09 radeon_microcode.h -rw-r--r-- 1 root wheel 0 Jan 7 01:09 radeon_microcode.h.orig Is ther a secret handshake to make patch put the files in their correct place? (Except for reading through the whole patchfile to determine if all touched filews are in the same directory.) For now I just mv'ed the files into place. Anyway, now the new kernel builds, installs and works correctly. It didn't pick up any drm, but I'm not sure that it should either. This machine[1] has a GeForce 8200 chipset. More info about FreeBSD on this machine here[2], including dmesgs before and after, etc. Nope, sorry no Nvidia support yet. nouveau is on my list to work on, but it's a long list... robert. Any help that we mere mortals can provide other than sending you hardware? I have a donated 6800 gt, I think it is. Don't have a pci-e board to put it on yet... nouveau isn't really ready on linux yet either, so I couldn't even offer a real timeline at this point. The nouveau guys are generally good to work with, but it is entirely a reverse engineering effort. Nvidia is about the only major vendor that isn't releasing docs and code now. ATI/AMD is releasing docs and code, so r6/7xx won't be hard. I have the base code building now, but it isn't complete yet. We will have this code in the tree as soon as or before linux. The AMD guys are good to work with and are pretty happy to have FreeBSD support. They have also indicated that they might be able to help with hardware for development. I'm also talking with VIA and it looks like they might send me hardware also. If they do, they will make the short list as well. robert. HTH References: 1) http://tingox.googlepages.com/asus_v2-m3n8200 2) http://tingox.googlepages.com/asus_v2-m3n8200_freebsd Yuri signature.asc Description: This is a digitally signed message part
