From: Michel "D?nzer" <mdaenzer@yahoo.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: LongTrail PCI resource assignment
Date: Fri, 24 Mar 2000 07:42:47 -0800 (PST) [thread overview]
Message-ID: <20000324154247.10557.qmail@web120.yahoomail.com> (raw)
--- Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Bug in X: the big endian frame buffer is at base + 0x800000.
It doesn't know about the meaning behind the regions.
> Besides, why does X need this? If it uses fbdev, all it should notice is
> that the reported fix.smem_start lies within the 16 MB for this PCI device,
> so it should not touch that PCI directly, only through the fbdev API
> (ioctl+mmap).
You should discuss that on the X-devel list, in particular with Egbert Eich
(and Jeff Garzik, and ... :).
Michel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-24 15:42 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 15:42 Michel D?nzer [this message]
2000-03-24 16:30 ` LongTrail PCI resource assignment Michael Schmitz
2000-03-24 17:17 ` Benjamin Herrenschmidt
2000-03-24 18:27 ` Michael Schmitz
2000-03-25 13:31 ` Geert Uytterhoeven
2000-03-25 14:28 ` Michel Dänzer
2000-03-25 14:49 ` Geert Uytterhoeven
2000-03-26 8:45 ` Michel Dänzer
2000-03-25 15:39 ` Michael Schmitz
2000-03-26 8:58 ` Michel Dänzer
2000-03-27 9:43 ` Michael Schmitz
2000-03-27 11:27 ` Michel Dänzer
[not found] <Pine.GSO.4.10.10003220927550.29557-100000@dandelion.sonytel.be>
2000-03-27 21:12 ` Martin Mares
-- strict thread matches above, loose matches on Subject: below --
2000-03-22 8:27 Geert Uytterhoeven
2000-03-22 10:24 ` Michel Lanners
2000-03-22 10:43 ` Geert Uytterhoeven
2000-03-22 13:15 ` Benjamin Herrenschmidt
2000-03-23 7:41 ` Michel Lanners
2000-03-23 10:13 ` Benjamin Herrenschmidt
2000-03-23 19:22 ` Michel Lanners
2000-03-24 8:49 ` Timothy A. Seufert
2000-03-24 9:02 ` Geert Uytterhoeven
2000-03-24 9:54 ` Benjamin Herrenschmidt
2000-03-24 10:56 ` Michael Schmitz
2000-03-24 12:26 ` Geert Uytterhoeven
2000-03-24 13:36 ` Michael Schmitz
2000-03-24 13:48 ` Geert Uytterhoeven
2000-03-24 12:37 ` Geert Uytterhoeven
2000-03-24 13:27 ` Michael Schmitz
2000-03-24 13:34 ` Geert Uytterhoeven
2000-03-24 16:07 ` Michael Schmitz
2000-03-24 13:35 ` Gabriel Paubert
2000-03-24 13:48 ` Michael Schmitz
2000-03-24 14:10 ` Benjamin Herrenschmidt
2000-03-24 15:56 ` Gabriel Paubert
2000-03-24 17:40 ` Michael Schmitz
2000-03-24 17:51 ` Gabriel Paubert
2000-03-24 18:43 ` Michael Schmitz
2000-03-24 20:03 ` Gabriel Paubert
2000-03-24 21:37 ` Michael Schmitz
2000-03-25 13:35 ` Geert Uytterhoeven
2000-03-25 15:13 ` Michael Schmitz
2000-03-27 8:57 ` Michael Schmitz
2000-03-27 9:43 ` Michel Dänzer
2000-03-27 9:58 ` Michael Schmitz
2000-03-27 10:38 ` Geert Uytterhoeven
2000-03-29 20:05 ` Geert Uytterhoeven
2000-03-30 20:59 ` Michael Schmitz
2000-04-03 8:58 ` Michel Lanners
2000-04-03 18:42 ` Michael Schmitz
2000-04-04 6:01 ` Michel Lanners
2000-03-27 11:33 ` Kostas Gewrgiou
2000-03-27 11:46 ` Michael Schmitz
2000-03-27 12:04 ` Geert Uytterhoeven
2000-03-27 11:51 ` Geert Uytterhoeven
2000-03-27 11:58 ` Michael Schmitz
2000-03-27 12:04 ` Michel Dänzer
2000-03-27 11:41 ` Michel Dänzer
2000-03-27 9:50 ` Geert Uytterhoeven
2000-03-27 10:01 ` Michael Schmitz
2000-03-27 10:35 ` Geert Uytterhoeven
2000-03-27 11:34 ` Michael Schmitz
2000-03-27 11:54 ` Geert Uytterhoeven
2000-03-27 16:55 ` Michael Schmitz
2000-03-27 18:58 ` Michel Lanners
2000-03-27 20:03 ` Michael Schmitz
2000-03-27 21:03 ` Michel Lanners
2000-03-27 11:46 ` Michel Lanners
2000-03-25 14:15 ` Michel Dänzer
2000-03-25 13:28 ` Geert Uytterhoeven
2000-03-25 14:36 ` Michael Schmitz
2000-03-24 22:16 ` Michel Lanners
2000-03-24 9:43 ` Benjamin Herrenschmidt
2000-03-24 22:13 ` Michel Lanners
2000-03-24 13:12 ` Benjamin Herrenschmidt
2000-03-24 22:41 ` Michel Lanners
2000-03-22 13:18 ` Benjamin Herrenschmidt
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=20000324154247.10557.qmail@web120.yahoomail.com \
--to=mdaenzer@yahoo.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/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.