From: Otto Solares <solca@guug.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: fbdev proposed change
Date: Thu, 27 Nov 2003 12:16:07 -0600 [thread overview]
Message-ID: <20031127181607.GA10773@guug.org> (raw)
Hi!
Is there any way to know the bus topology of a framebuffer
device?, i want to get this info from fbdev so i can integrate
this info from the info libhal provides me, explicitly
having something like fb_fix_screeninfo.bus_id will be a
good idea IMO.
bus_id should be something like this for pci:
fb_fix_screeninfo.bus_id = "PCI:1.5.0"
or for sbus:
fb_fix_screeninfo.bus_id = "SBUS:cgsix"
Is just a few bytes and all drivers already know their bus
topology, this info is extremelly useful for detecting the
exact device a fbdev is attached.
-solca
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
reply other threads:[~2003-11-27 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031127181607.GA10773@guug.org \
--to=solca@guug.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 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).