From: "Ville Syrjälä" <syrjala@sci.fi>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: fbdev cursor part 1.
Date: Tue, 24 Feb 2004 02:55:08 +0200 [thread overview]
Message-ID: <20040224005508.GD8088@sci.fi> (raw)
In-Reply-To: <Pine.GSO.4.58.0402231449040.14277@waterleaf.sonytel.be>
On Mon, Feb 23, 2004 at 02:51:07PM +0100, Geert Uytterhoeven wrote:
> On Mon, 23 Feb 2004, Ville [iso-8859-1] Syrjälä wrote:
> > BTW would it be possible to add a new accelerator type for Pro chips. I'd
> > like to identify Pro chips in my DirectFB driver because there are a few
> > important differences between Pro and older models. Othwerwise I'm going
> > to have to the same thing I did with matrox cards and use /proc/bus/pci :(
>
> Can't you just check CONFIG_CHIP_ID in your DirectFB driver?
Yes I can ;) I didn't realize the chip kept the device id in it's own
register. Thanks.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
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\x1356&alloc_id438&op=click
next prev parent reply other threads:[~2004-02-24 1:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 22:26 fbdev cursor part 1 James Simmons
2004-02-16 23:35 ` Benjamin Herrenschmidt
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ä [this message]
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=20040224005508.GD8088@sci.fi \
--to=syrjala@sci.fi \
--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 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).