| Summary: | i915 DRM needs to be ported to FreeBSD | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Sune Wettersteen <forexs> |
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | high | CC: | eric |
| Version: | XOrg 6.7.0 | ||
| Hardware: | All | ||
| OS: | FreeBSD | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Sune Wettersteen
2005-11-19 16:44:52 UTC
Yes, the driver needs to be ported. It's also one of the most annoying drivers (second only to i810, I'd say), because it needs to attach to the same device that the agp driver does. This should be a little bit of newbus play for someone that understands how that works (the current code works in theory, but not in practice). Keith Whitwell has had this working, I think, and perhaps also John Baldwin, but it didn't for me while I had the hardware. I won't be attacking this myself. As far as I understand intel released a linux driver for this, shouldn't that make it easier get to gribs with it? (I'm not really comfertable with a how all this works. However I develop with openGL which is why I'm so interested in the driver). Okay, but thanks for your reply. Do you know someone else you could refer to this bug that may look into it? Sure, there's an open-source driver written by Tungsten Graphics, which is the one we're talking about here. The question is how to make it work on FreeBSD. There are no people currently working on this. If you want it fixed, it's probably going to mean experimenting and figuring it out yourself. That probably means looking at the probe/attach stuff in the core drm, figuring out why i915 DRM isn't attaching to the special drmsub device that the intel AGP driver is creating just for the drm to attach to. i915 DRM has been committed to -current and merged to RELENG_6. Wow, great!! Thanks a lot man.. If I could only get it to work now :) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.