| Age | Commit message (Collapse) | Author |
|---|
|
|
|
I'm going to pass back a list of blob ids and lengths in the getproperty.
will need another ioctl to return the blob data as it is variable length.
|
|
This also starts to add blob property support.
someone needs to check this work for other things like ppc/x86 alignment diffs
|
|
|
|
so really want to get a list of modes per output not the global hammer list.
also we remove the mode ids and let the user pass back the full mode description
need to fix up add/remove mode for user modes now
|
|
This allow the user to retrieve a list of properties for an output.
Properties can either be 32-bit values or an enum with an associated name.
Range properties are to be supported.
This API is probably not all correct, I may make properties part of the general
resource get when I think about it some more.
So basically you can create properties and attached them to whatever outputs you want,
so it should be possible to create some generics and just attach them to every output.
|
|
|
|
|
|
This allows userspace to specify modes and add them to the modesetting
system and attach modes to outputs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This still isn't perfect but it fixes a few oopses and cleans up
some of the tabs and bugs in the original fb limit code
|
|
Originally from Jakob, cleaned up by airlied.
|
|
This adds the user interfaces from Jakob and hooks them up for 3 ioctls
GetResources, GetCrtc and GetOutput.
I've made the ids for everything fbs, crtcs, outputs and modes go via idr as
per krh's suggestion on irc as it make the code nice and consistent.
|
