linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ryuichi Oikawa <roikawa@rr.iij4u.or.jp>
To: speedy@carboncode.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: C&T acceleration support, needs testers.
Date: Mon, 02 Aug 1999 03:07:22 GMT	[thread overview]
Message-ID: <19990802030722A.roikawa@rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Sat, 31 Jul 1999 18:56:20 -0700" <199907312248.QAA05182@carboncode.com>


Hi, 
Thank you for responses.

From: Don Lunder <speedy@carboncode.com>
Subject: Re: C&T acceleration support, needs testers.
> I'll keep playing with it, and tell you what I find, if you have any 
> specific requests, please do ask!

I'd like to further know,

- Difference between 8bp and 16bpp. 8bpp doesn't cause endiannes problem but
 may be more unstable.

- Vertical band problem, more precisely(ex. both 8 and 16bpp? happens
 at what X command? appearing location and size?, etc.)

- Difference between chipsfb and offb(BootX' "no video driver").
  When kernel booted with "no video driver", Xpmac with -ct6555 option
  does BitBLT origin offset calculation, color palette handling and aperture
  setting. I have report that reading color palette immediately causes
  machine check exception resulting in kernel panic(why??). And if aperture
  setting is failed, Xpmac goes into infinite loop.

> PS After Spell checking the email, I see that register has a typo in the 
> Xpmac out put. <shrug>
Oops! :-)

Anyway, I'll soon upload the source code(at the same place, please check)
so that anyone can try and fix it, before I'm on a vacation.

In the mean time, I had a advice that I should end it and spend time
for new XFree(4.0). I'd be glad if someone continued to work on this,
though I haven't decided anything yet.


Regards,

Ryuichi Oikawa
roikawa@rr.iij4u.or.jp

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-08-02  3:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-01  0:53 C&T acceleration support, needs testers Ryuichi Oikawa
1999-07-31 20:12 ` Vinai
1999-07-31 21:36   ` cesli
1999-08-01  1:56 ` Don Lunder
1999-08-01  1:03   ` Vinai
1999-08-01  3:23     ` Don Lunder
1999-08-02  3:07   ` Ryuichi Oikawa [this message]
1999-08-02  8:17     ` Geert Uytterhoeven
1999-08-01 23:48 ` Ryuichi Oikawa
1999-08-02  8:16   ` Geert Uytterhoeven

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=19990802030722A.roikawa@rr.iij4u.or.jp \
    --to=roikawa@rr.iij4u.or.jp \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=speedy@carboncode.com \
    /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;
as well as URLs for NNTP newsgroup(s).