Subject: Re: Problems with new radeonfb and XFree86
To: None <tls@rek.tjls.com>
From: Michael Lorenz <macallan@netbsd.org>
List: port-macppc
Date: 11/16/2006 23:59:59
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Nov 16, 2006, at 23:07, Thor Lancelot Simon wrote:

> On Thu, Nov 16, 2006 at 06:24:16PM -0500, Michael Lorenz wrote:
>>
>> Argh, I knew I forgot something.
>> The original radeonfb didn't allow mmap()ing any PCI resources, so I
>> added support for that but made it optional to avoid breaking the
>> behaviour the author intended.
>> So what's missing in GENERIC is
>> options		RADEONFB_MMAP_BARS
>
> Will Xwsfb work without this option?

Supposedly it does, although I never tried it.

>   If I understand what it does correctly, it is wildly insecure.

Depends - the BAR mappings should be restricted to processes with root 
credentials, only the 'canonical' framebuffer mapping at offset 0 
should be accessible to everyone who can play with ttyE0.
To avoid misunderstanding - we're talking about mmap()ing PCI resources 
belonging to the console wsdisplay device - and only those - via ttyE0, 
not /dev/mem or something.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRV1Bz8pnzkX8Yg2nAQJeaAgAn1Xef6mQUS7l9wXzB+2P04eTKghXiSdp
y3ibaGM9y2aIDrM5o+ti/gVUovsJBCk+w6ToZjWLc7OMK5EKIUHxeJjnmdRNAVow
jHiBLj4bwGUrySm0EFx8s+npKJaXN5tQHTOzvSdkJxiMPgoovuickAnmJKGAPOcJ
qCzc4WFDCIVjuw5AWZNC/wEilFN2f9FaJighmF7KYyMJBHMQnS6TLlxmMeZagGUK
nUb0u9QdWF7K4558ZqQIIcUPbN9K5P1F09qJoHdcC4B3WHj6XKR3Ki/pesYnoWzy
VyYLcVY4o+sflfdSAtNN3kp9zJfJ9O8mSS32saqn+FD0Wi8vkgYtKg==
=b70w
-----END PGP SIGNATURE-----