From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128
Date: Fri, 10 Mar 2000 13:17:30 -0500 [thread overview]
Message-ID: <v03110700b4eeeb194579@[129.100.29.243]> (raw)
In-Reply-To: <Pine.LNX.4.21.0003101831430.19076-100000@idd-01.imbc.gr>
Hi Kostas,
>> So we should probably get some official patch out there that includes a few
>> elements:
>>
>
> What do you mean by official ? The next xfree86 update will have
>this fix what more official do you suggest ?
>
>> 1. Either:
>> - user defined cache line size during compile
>> or:
>> - flush a cache range in address increments of 8
>>
>> to handle the variable line cache size
I am confused. Now that XF 4.0 is out, will quick snapshots continue to be
released?
I just assumed that we would start getting incremental releases 4.0.1,
4.0.2 that would be long in coming (months or more...just like the 3.3.X
series). If snapshots will continue coming fast, then you are right. If
snapshots will not be coming (or minor updates will take a few months to
get working), then perhaps an official patch put on the www.linuxppc.org
site or something for Robert Shaw's page so that others who build XF 4.0
from source will have something to fix the cache problems with.
How about just a patch that fixes cache flushing for XFree 4.0 which
assumes cacke line sizes of 16 and ignores 601 problems then that we just
send to the linuxppc-dev mailing list so that it gets archived.
> Glibc assumes a line size of 16 so that will be ok, in any
>case the cache flush will be used only in the startup of the
>xserver not need to worry about a few extra instructions there
>so we can live even with 4byte increments, definitely better than
>a compile time option.
> Hmm i don't think that xfree86 4.0 will work under mklinux, there
>aren't any drivers that will work under mk anymore (xpmac is gone and
>the vgahw/fbdev based ones won't work).
Is this true? So we don't have to worry about 601 processors at all?
Thanks,
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-10 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0003041753480.1870-100000@idd-01.imbc.gr>
2000-03-04 18:55 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-05 13:42 ` Michel Dänzer
2000-03-05 16:43 ` Kostas Gewrgiou
2000-03-05 16:58 ` Kevin B. Hendricks
2000-03-05 21:04 ` Kostas Gewrgiou
2000-03-05 21:20 ` Geert Uytterhoeven
2000-03-05 22:25 ` Kostas Gewrgiou
2000-03-06 6:54 ` Geert Uytterhoeven
2000-03-09 3:11 ` Kevin Hendricks
[not found] ` <38C7A016.8C2ED4C8@iiic.ethz.ch>
[not found] ` <v03110701b562ab7246aa@[129.100.29.243]>
2000-03-10 15:33 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 Kevin B. Hendricks
2000-03-10 17:25 ` Kostas Gewrgiou
2000-03-10 18:17 ` Kevin B. Hendricks [this message]
2000-03-10 19:21 ` Michael Schmitz
2000-03-10 23:54 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on ppcwithr128 Michel Dänzer
2000-03-11 14:50 ` Michael Schmitz
2000-03-12 14:52 ` patch to get latest XFree 4.0 snapshot (xf3918) to work onppcwithr128 Michel Dänzer
2000-03-10 19:43 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 David A. Gatwood
2000-03-11 14:38 ` Help! Getting aty128fb.c to work with newest sawtooth machines Kevin Hendricks
2000-03-13 9:19 ` Kostas Gewrgiou
2000-03-14 1:12 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-09 2:41 ` Kevin Hendricks
2000-03-09 11:04 ` Gabriel Paubert
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='v03110700b4eeeb194579@[129.100.29.243]' \
--to=khendricks@ivey.uwo.ca \
--cc=gewrgiou@imbc.gr \
--cc=linuxppc-dev@lists.linuxppc.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