linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Anholt <eta@lclark.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-fbdev-devel@lists.sf.net
Subject: DRM and pci_driver conversion
Date: Mon, 20 Oct 2003 19:31:56 -0700	[thread overview]
Message-ID: <1066703516.646.24.camel@leguin> (raw)

I recently committed a change to the DRM for Linux in DRI CVS that
converted it to use pci_driver and that probe system.  Unfortunately,
we've found that there is a conflict between the DRM now and at least
the radeon framebuffer.  Both want to attach to the same device, and
with pci_driver, the second one to come along doesn't get probe called
for that device.  Is there any way to mark things shared, or in some
other way get the DRM to attach to a device that's already attached to,
in the new model?

Please CC me on replies as I'm not subscribed to these lists.

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org



             reply	other threads:[~2003-10-21  2:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  2:31 Eric Anholt [this message]
2003-10-23 19:04 ` [Linux-fbdev-devel] DRM and pci_driver conversion Kronos
2003-10-23 21:10   ` Eric Anholt
2003-10-23 21:31     ` Jon Smirl
2003-10-23 23:23       ` [Dri-devel] " Linus Torvalds
2003-10-23 23:46         ` Eric Anholt
2003-10-24  1:19         ` Jeff Garzik
2003-10-24  1:52           ` Jon Smirl
2003-10-24  3:47           ` Multiple drivers for same hardware:, was: " Jon Smirl
2003-10-24  4:40             ` Linus Torvalds
2003-10-28 18:00               ` James Simmons
2003-10-24 16:44           ` [Dri-devel] Re: [Linux-fbdev-devel] " Linus Torvalds
2003-10-24 16:57             ` Petr Vandrovec
2003-10-24 17:59               ` Linus Torvalds
2003-10-24 18:34                 ` Jon Smirl
2003-10-24 19:45                   ` Ivan Kokshaysky
2003-10-24 19:08               ` Ivan Kokshaysky
2003-10-24 17:06             ` Jeff Garzik
2003-10-24  1:50         ` Jon Smirl
2003-10-25 17:29         ` Egbert Eich
2003-10-25 18:37           ` Linus Torvalds
2003-10-25 19:17             ` Jeff Garzik
2003-10-27 14:37               ` Ingo Oeser
2003-10-27 15:43                 ` Jeff Garzik
2003-10-28 10:53                   ` Ingo Oeser
2003-10-27 15:14               ` Keith Whitwell
2003-10-27 15:38                 ` Jeff Garzik
2003-10-27 15:50                   ` Keith Whitwell
2003-10-25 21:02             ` Jon Smirl
2003-10-25 22:07             ` Benjamin Herrenschmidt
2003-10-27 14:01             ` jlnance
2003-10-27 15:10             ` Eric W. Biederman
2003-10-27 15:10             ` Keith Whitwell

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=1066703516.646.24.camel@leguin \
    --to=eta@lclark.edu \
    --cc=linux-fbdev-devel@lists.sf.net \
    --cc=linux-kernel@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).