From: Kronos <kronos@people.it>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Framebuffer and non-PCI devices
Date: Sun, 20 Feb 2005 01:05:19 +0100 [thread overview]
Message-ID: <20050220000519.GA7543@dreamland.darkstar.lan> (raw)
In-Reply-To: <9e473391050219135923cc6455@mail.gmail.com>
Il Sat, Feb 19, 2005 at 04:59:46PM -0500, Jon Smirl ha scritto:
> I started editing all of the drivers to make assigning fb_info->device
> explicit. Does this look like it is useful?
Look at framebuffer_alloc ;)
Luca
--
Home: http://kronoz.cjb.net
Windows NT: Designed for the Internet. The Internet: Designed for Unix.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-20 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:25 Framebuffer and non-PCI devices Jon Smirl
2005-02-19 18:40 ` Geert Uytterhoeven
2005-02-19 21:59 ` Jon Smirl
2005-02-19 23:38 ` Antonino A. Daplas
2005-02-20 1:17 ` Jon Smirl
2005-02-22 4:01 ` James Simmons
2005-02-20 0:05 ` Kronos [this message]
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=20050220000519.GA7543@dreamland.darkstar.lan \
--to=kronos@people.it \
--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).