public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <adeucher@UU.NET>
To: Jeff Hartmann <jhartmann@valinux.com>
Cc: Petr Vandrovec <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 13:14:19 -0500	[thread overview]
Message-ID: <3A82E1FB.75361E04@uu.net> (raw)
In-Reply-To: <14E9CDBC07F1@vcnet.vc.cvut.cz> <3A82DB9B.3050008@valinux.com>



Jeff Hartmann wrote:
> 
> Petr Vandrovec wrote:
> 
> > On  8 Feb 01 at 12:15, Alex Deucher wrote:
> >
> >> I wasn't talking about the drm driver I was talking about programming
> >> the PCI controller directly using setpci 1.0.0 .... or some such
> >> command, I can't remember off hand.  Which turns on busmastering if it
> >> is off for a particular device.
> >
> >
> > OK.
> >
> >> Jeff Hartmann wrote:
> >>
> >>> The DRM drivers don't know about the pcidev structure at all.  All this
> >>> is done in the XFree86 ddx driver.  You can probably add something like
> >>> this to MGAPreInit (after pMga->PciTag is set, in my copy its
> >>> mga_driver.c:1232 yours might be at a slightly different line number
> >>> depending on the version your using):
> >>>
> >>> {
> >>>    CARD32 temp;
> >>>    temp = pciReadLong(pMga->PciTag, PCI_CMD_STAT_REG);
> >>>    pciWriteLong(pMga->PciTag, PCI_CMD_STAT_REG, temp |
> >>> PCI_CMD_MASTER_ENABLE);
> >>> }
> >>
> >
> > Jeff, do you say that drm code does not use dynamic DMA mapping, which is
> > specified as only busmastering interface for kernels 2.4.x, at all? Now
> > I understand what had one friend in the mind when he laughed when I said
> > that it must be easy to get it to work on Alpha...
> >                             Thanks anyway for all suggestions,
> >                                         Petr Vandrovec
> >                                         vandrove@vc.cvut.cz
> >
> >
> It does not use dynamic DMA mapping, because it doesn't do PCI DMA at
> all.  It uses AGP DMA.  Actually, it shouldn't be too hard to get it to
> work on the Alpha (just a few 32/64 bit issues probably.)  Someone just
> needs to get agpgart working on the Alpha, thats the big step.
> 
> -Jeff


That shouldn't be too hard since many (all?) AGP alpha boards (UP1000's
anyway) are based on the AMD 751 Northbridge? And there is already
support for that in the kernel for x86. 

Alex
-
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 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 18:36 2.4.x, drm, g400 and pci_set_master Petr Vandrovec
2001-02-08 17:47 ` Jeff Hartmann
2001-02-08 18:14   ` Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-08 16:39 Alex Deucher
2001-02-08 17:08 ` Jeff Hartmann
2001-02-08 17:15   ` 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=3A82E1FB.75361E04@uu.net \
    --to=adeucher@uu.net \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jhartmann@valinux.com \
    --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