renesas/drm.git - libdrm, cloned from git://anongit.freedesktop.org/mesa/drm

Age	Commit message (Collapse)	Author
2008-05-30	drm: add more encoder interfaces	Dave Airlie

2008-05-30	libdrm: add encoder retrival	Dave Airlie

2008-05-08	drm_mode: initial replacefb implemenation	Dave Airlie

2008-05-08	cursor: pass handle not BO.	Dave Airlie

2008-02-29	drm: change fb api to take a bo handle not the bo pointer.	Dave Airlie

2008-02-28	drm: add a check for if modesetting is supported.	Dave Airlie
	This is Linux only code, it just uses sysfs to see if a control device has been registered on the requested PCI ID
2008-02-07	Added userspace part of hotplug ioctl and demo	Jakob Bornecrantz

2008-02-05	consistency	Alan Hourihane

2008-01-28	Added cursor support	Jakob Bornecrantz

2007-12-18	remove output names	Dave Airlie

2007-12-11	modesetting: fixup property setting and add connector property	Dave Airlie

2007-12-06	add property blobs and edid reporting support	Dave Airlie

2007-12-05	more WIP on blobs..	Dave Airlie
	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.
2007-12-05	arrgggh.. make all ioctl structs 32/64-bit compatible hopefully.	Dave Airlie
	This also starts to add blob property support. someone needs to check this work for other things like ppc/x86 alignment diffs
2007-12-03	finish of mode add/remove, just have attach/detach modes	Dave Airlie

2007-12-03	modesetting API change for removing mode ids and making modes per output.	Dave Airlie
	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
2007-11-27	drm/modesetting: add initial gettable properites code.	Dave Airlie
	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.
2007-11-15	libdrm: add crtc/output ids to userspace interface	Dave Airlie

2007-05-05	Cleaned up userspace interface for modesetting.	Jakob Bornecrantz

2007-05-01	Add support for user defined modes	Dave Airlie
	This allows userspace to specify modes and add them to the modesetting system and attach modes to outputs
2007-04-12	use FB everywhere	Dave Airlie

2007-04-12	allow framebuffer changes on the crtc setup	Dave Airlie

2007-04-12	add getfb ioctl	Dave Airlie

2007-04-11	add support for setting a framebuffer depth	David Airlie

2007-04-11	add an fb count + id get to the get resources code path	David Airlie

2007-04-10	export output name to userspace	David Airlie

2007-04-10	fixup numerous issues with adding framebuffer support	David Airlie
	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
2007-04-10	add addfb/rmfb ioctls	Jakob Bornecrantz
	Originally from Jakob, cleaned up by airlied.
2007-04-05	checkpoint commit: added getresources, crtc and output	Dave Airlie
	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.