Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Arnaud Patard <apatard@mandriva.com>
Cc: linux-mips@linux-mips.org
Subject: Re: xorg-server-1.5.2 doesn't work because of missing sysfs pci resource files
Date: Fri, 5 Dec 2008 18:08:06 +0000	[thread overview]
Message-ID: <20081205180806.GA19217@linux-mips.org> (raw)
In-Reply-To: <m3ljuumrjs.fsf@anduin.mandriva.com>

On Fri, Dec 05, 2008 at 06:59:35PM +0100, Arnaud Patard wrote:

Arnaud,

> > Then I tried to read kernel code. I found it seems that for mips linux to have
> > this file, HAVE_PCI_MMAP must be defined. However, it is currently not defined.
> >
> > Since I am not familiar with PCI, yet.
> > So could someone please shed some light on this?
> > Why HAVE_PCI_MMAP is not defined?
> 
> HAVE_PCI_MMAP must be defined when you have a pci_mmap_page_range()
> function (see Documentation/filesystems/sysfs-pci.txt) and we don't have
> a pci_mmap_page_range() on mips.

Correct - but if the code is not present the kernel does not use an
alternative implementation.  I just looked into implementing that and it
seems nothing that I could do quickly to still get it into 2.6.28, sorry ...

  Ralf

  reply	other threads:[~2008-12-05 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 15:43 xorg-server-1.5.2 doesn't work because of missing sysfs pci resource files Zhang Le
2008-12-05 17:59 ` Arnaud Patard
2008-12-05 18:08   ` Ralf Baechle [this message]
2008-12-06 10:20 ` Ralf Baechle
2008-12-06 16:47   ` Zhang Le
2008-12-09 17:22     ` Zhang Le
2008-12-09 17:39       ` Zhang Le
2008-12-09 17:57         ` Ralf Baechle
2008-12-09 18:17   ` Arnaud Patard
2008-12-09 18:36     ` Ralf Baechle
2008-12-09 19:01       ` Arnaud Patard

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=20081205180806.GA19217@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=apatard@mandriva.com \
    --cc=linux-mips@linux-mips.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