linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kronos <kronos@kronoz.cjb.net>
To: Ian Romanick <idr@us.ibm.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Add three new IOCTLs to FB API
Date: Tue, 23 Sep 2003 18:36:10 +0200	[thread overview]
Message-ID: <20030923163610.GA5824@dreamland.darkstar.lan> (raw)
In-Reply-To: <3F6F8337.7050000@us.ibm.com>

Il Mon, Sep 22, 2003 at 04:18:15PM -0700, Ian Romanick ha scritto: 
> >>2) Get 3D driver name. Return the name of the DRM driver that is 
> >>associated
> >>with this fb device. For example aty128fb would return r128, radeonfb 
> >>would
> >>return radeon. Empty string if there is none. There are eight DRM drivers 
> >>and
> >>15 fb ones.
> >
> >I think this should be done using sysfs, too. I.e. symbolic links between 
> >the
> >fbdev and drm drivers in /sys.
> 
> I'm not that familiar with how sysfs works.  How would this look? 
> There'd be a tree like:
> 
>     /sys/
>         card0/
Actually it will be /sys/graphics/fb0

>             dri.so (link to client-side driver)

Userspace  library? We  can  put  the   name  here,  not  a  symlink  to
the  library. sysfs  deals  only  with kobjects  (ie.  things that  live
somewhere in the  kernel). We can create link between  two kobjects (see
sysfs_create_link) but not between a kobject and something else.

>             DRM_device (link to DRM device that will load kernel module)

Do you mean device under /dev? Can't do that, see above. We can put
module name, so a user can do:
modprobe `cat /sys/graphics/fb0/drm_module`

>             PCI_INFO (file containing PCI device information)

Under /sys/graphics/fb0 there will be a "device" symlink. This will take
you to the device dir:
root@dreamland:/sys/bus/pci/devices/0000:01:00.0# ls
class  config  detach_state  device  irq  power/  resource subsystem_device  subsystem_vendor  vendor
root@dreamland:/sys/bus/pci/devices/0000:01:00.0# cat vendor device subsystem_vendor subsystem_device
0x1002
0x4e45
0x1681
0x0002

You can get everything from here without the need to add another
attribute.

Luca
-- 
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Ci sono due cose che l'uomo non puo` nascondere:
essere ubriaco ed essere innamorato.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-23 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22  5:28 Add three new IOCTLs to FB API Jon Smirl
2003-09-22  6:13 ` Ian Romanick
2003-09-22  7:21 ` Geert Uytterhoeven
2003-09-22 20:25   ` Jon Smirl
2003-09-23  0:27     ` Michel Dänzer
2003-09-22 23:18   ` Ian Romanick
2003-09-23 16:36     ` Kronos [this message]
2003-09-22 10:23 ` Michel Dänzer
2003-09-23 15:45 ` Ville Syrjälä

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=20030923163610.GA5824@dreamland.darkstar.lan \
    --to=kronos@kronoz.cjb.net \
    --cc=idr@us.ibm.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).