From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@infradead.org>,
Alexander Kern <alex.kern@gmx.de>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: fbdev cursor part 1.
Date: Tue, 24 Feb 2004 09:53:20 +1100 [thread overview]
Message-ID: <1077576800.28487.80.camel@gaston> (raw)
In-Reply-To: <Pine.GSO.4.58.0402231343270.14277@waterleaf.sonytel.be>
>
> That's OK, as long as entries <= 15.
>
> Using this register you cannot check for more than 15. There's another register
> for that, and the difference between PRO and older is in that second register.
Ok. But we never wait for more than 15. when filling the HOST_DATA, we wait
for 1 for each long word (maybe that is wrong, it's definitely sub optimal),
and we wait for at most 6 afiak when setting up.
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 23:09 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
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 [this message]
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=1077576800.28487.80.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=alex.kern@gmx.de \
--cc=geert@linux-m68k.org \
--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.