All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <adeucher@UU.NET>
To: vandrove@vc.cvut.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.4.x, drm, g400 and pci_set_master
Date: Thu, 08 Feb 2001 11:39:42 -0500	[thread overview]
Message-ID: <3A82CBCE.6926AFAF@uu.net> (raw)

I'm not sure about the mga source, but you can enable busmaster manually
as root.  See the dri-devel list for more.  I can't remember the exact
message off hand.  THere was also some discussion of this last week I
think.

Alex


----------------------------

Hi, 
  friend of mine bought g400 on my recommendation, and unfortunately, 
mga drm driver did not worked for me. I tracked it down to missing 
pci_enable_device and pci_set_master in mga* driver. But even after 
looking more than hour into that code I have no idea where I should 
place this call, as it looks like that mga driver is completely 
shielded from seeing pcidev structure :-( 
  Does anybody know where I should place pci_enable_device and 
pci_set_master into mga code? I worked around pci_enable_device by 
using matroxfb, but pci_set_master is not invoked by matroxfb, and 
adding this call into matroxfb just to get mga drm driver to work does 
not look correctly to me - although it is what I had done just now. 
                                    Thanks, 
                                            Petr Vandrovec 
                                            vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-02-08 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 16:39 Alex Deucher [this message]
2001-02-08 17:08 ` 2.4.x, drm, g400 and pci_set_master Jeff Hartmann
2001-02-08 17:15   ` Alex Deucher
  -- strict thread matches above, loose matches on Subject: below --
2001-02-08 18:36 Petr Vandrovec
2001-02-08 17:47 ` Jeff Hartmann
2001-02-08 18:14   ` Alex Deucher
2001-02-08 16:32 Petr Vandrovec

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=3A82CBCE.6926AFAF@uu.net \
    --to=adeucher@uu.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.