re: Xorg on Blade 150

> Maybe you need a kernel with options INSECURE? I am not sure when that
> requirement sneaked into our in-tree X (and for what hardware exactly),
> it went unnoticed for some time.

it happened when some kauth code was pushed into a bunch more
drivers, pretty much correctly rejecting attempts to map device
memory when secure.  i forget the change itself..

> We need to update documentation + default kernel configs.

it kind of sucks that we have to turn INSECURE on just for X,
maybe we can have a GENERIC_GRAPHICS that does?  i won't object
whatever you choose.


.mrg.