From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Framebuffer and non-PCI devices
Date: Sat, 19 Feb 2005 13:25:38 -0500 [thread overview]
Message-ID: <9e47339105021910257461d4cc@mail.gmail.com> (raw)
Are any of the framebuffers non-PCI devices?
Looking through the code fb_info->device appears to be filled in by
only a subset of the drivers. Can fb_info->device be converted to a
pci device? I would also add it as a parameter to register_fb() in
order to make sure it gets filled in. Are all of the drivers converted
to register_fb()?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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
next reply other threads:[~2005-02-19 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:25 Jon Smirl [this message]
2005-02-19 18:40 ` Framebuffer and non-PCI devices 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
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=9e47339105021910257461d4cc@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).