From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Alexander Kern <alex.kern@gmx.de>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: fbdev cursor part 1.
Date: Mon, 23 Feb 2004 11:35:51 +1100 [thread overview]
Message-ID: <1077496550.5960.9.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402222234120.2390-100000@phoenix.infradead.org>
> ment ;-)
>
> I plan to submit the latets mach64 driver from BK to linus as soon as the
> first part of the cursor patch goes in. It gives enough of the new
> cursor api to do a dump of all the drivers in the 2.5 fbdev tree. Could you
> make your patch against the fbdev-2.5 bk tree? Try my patch
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
>
> If it doesn't work I will put a new one you there.
Note that I'm having some troubles with James current mach64 bk on a
wallstreet PowerBook (mach64 LT-G). There is an endian bug in the
imageblt implementation, I don't know if the chip can be instructed
to do the endian flip, so I modified the function storing to the
fifo, that appear to work, at least with 8 bits mode ;)
But I'm having lockups, very regular. I haven't been able to figure
out why though. Adding a wait_for_idle() at the end of both fillrect
and copyarea() seem to make them disappear (well, almost, I had _one_
still once). It's weird as those shouldn't be necessary.
Maybe we should add a timeout on the wait_* functions with an engine
reset, that would be sub-optimal, but at least we wouldn't lockup the
box (if that is possible of course).
Ben.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-23 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 22:26 fbdev cursor part 1 James Simmons
2004-02-16 22:26 ` James Simmons
2004-02-16 23:35 ` Benjamin Herrenschmidt
2004-02-16 23:35 ` Benjamin Herrenschmidt
2004-02-16 23:41 ` James Simmons
2004-02-16 23:41 ` James Simmons
2004-02-22 21:06 ` Alexander Kern
2004-02-22 22:37 ` James Simmons
2004-02-23 0:35 ` Benjamin Herrenschmidt [this message]
2004-02-23 10:57 ` Geert Uytterhoeven
2004-02-23 10:59 ` Benjamin Herrenschmidt
2004-02-23 12:44 ` Geert Uytterhoeven
2004-02-23 13:21 ` Ville Syrjälä
2004-02-23 13:51 ` Geert Uytterhoeven
2004-02-24 0:55 ` Ville Syrjälä
2004-02-23 22:53 ` Benjamin Herrenschmidt
2004-03-05 9:03 ` Alexander Kern
2004-03-10 17:49 ` James Simmons
2004-03-11 5:05 ` Benjamin Herrenschmidt
2004-03-11 17:05 ` James Simmons
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=1077496550.5960.9.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=alex.kern@gmx.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.