On Sat, Sep 24, 2005 at 11:03:41AM +0100, Mark Adams wrote: > > I believe the problem here is that the hardware revision can only be > > obtained > > by root so this is hard-coded by Marks patch to 0x11 which works for VT1622A > > but I'm not sure how much the hwrev is used in the code. It looks like the > > main is is to test whether it is 0x10 or greater. Not sure of hte best way > > of > > getting round this: I don't like running stuff as root unless it _really_ > > needs to! > > OK, some confusion here. This is an issue with the DirectFB unichrome > gfxdriver code, not with viafb. > > DirectFB tries to read a byte from the PCI config that is only > available to processes running as root. It does this in trying to get > the version of the north bridge chip (not the TV encoder).
Actually what it's reading is some hw specific register (revision of the gfx core maybe?). Normal users can read the standard PCI config space registers including chip revision. AFAIK this is because some broken hardware doesn't like it if you attempt to access an unused part of the PCI config space. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
