linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: dri and udev
Date: Sat, 27 Dec 2003 20:57:38 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107260218131950@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107251004911161@msgid-missing>

The new DRM module has other changes in it so it has to be sync'd with a
DRI/Xfree86 release.  I also have to get the changes coordinated with the BSD
DRI people. DRM development happens out of the DRI tree not the kernel tree. So
after there is a DRI/Xfree86 Linus moves the changes over to the copy in the
kernel.

Another issue is the current conflict between fbdev and dri. Both device drivers
are trying to take overship of the graphics hardware. Right now fbdev owns the
hardware and DRI operates as a stealth module. For sysfs/udev to work DRI has to
have a PCI ID table and own the hardware. Doing this prevents fbdev and DRI from
simultaneously being loaded. 

This conflict has not been resolved. We did a previous version of DRM which
registered with the kernel as owning the hardware and got a lot of vocal
complaints from fbdev developers. DRM was backed off into steath mode again.

Stealth mode looks like this. It never calls pci_register_driver so the kernel
never knows that DRM has attached to the device.

static int __init drm_init( void )
{
	struct pci_dev *pdev = NULL;

	DRM(parse_options)( drm_opts );
	DRM(mem_init)();

	while ((pdev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, pdev)) != NULL) {
		DRM(probe)(pdev);
	}
	return 0;
}

My personal opinion on this is that it is insane for two device drivers to be
trying to share the same same piece of hardware - it's multitasking for device
drivers. I also don't think udev/sysfs are set up to deal with two device
drivers claiming the same piece of hardware.


==Jon Smirl
jonsmirl@yahoo.com

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2003-12-27 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-27  7:24 dri and udev Jon Smirl
2003-12-27 16:36 ` Kay Sievers
2003-12-27 17:08 ` Jon Smirl
2003-12-27 19:13 ` Greg KH
2003-12-27 19:13 ` Greg KH
2003-12-27 19:13 ` Greg KH
2003-12-27 19:14 ` Greg KH
2003-12-27 20:57 ` Jon Smirl
2003-12-27 20:57 ` Jon Smirl [this message]
2003-12-28  1:23 ` Marco d'Itri
2003-12-28  1:23 ` Marco d'Itri
2003-12-30  0:36 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-107260218131950@msgid-missing \
    --to=jonsmirl@yahoo.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).