- 05 Jul, 2011 39 commits
-
-
Alan Cox authored
Move this over. In actual fact there are some underlying differences as some devices have more MMU contexts, but for our 2D purposes we don't actually care. Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Alan Cox authored
We've now sorted them out so they can go into the generic code. In actual fact only the non MID devices use the functions but they are small and having the name match i915 is going to help any future merging type work. Signed-off-by:
-
Alan Cox authored
This is leaking an io mapping and also referencing stuff directly that should not be directly accessed. Sort it out Signed-off-by:
-
Alan Cox authored
This is generic for the PC class devices and also very similar to the i915 intel_bios.c so rename it. That way the commonality will be obvious and we can look at merging them one day, or at least synching them up. Signed-off-by:
-
Alan Cox authored
We don't want to carry all the extra gunk around on every device so use the splitting work so far to tidy this up. Poulsbo is still mandatory as it is used in bits by the other drivers and not neatly modularised. Signed-off-by:
-
Alan Cox authored
Rename the gem and gtt files accordingly. Signed-off-by:
-
Alan Cox authored
Rename Signed-off-by:
-
Alan Cox authored
The framebuffer code is now clean of device specific code, and passes checkpatch. Move it to its new name Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Shuffle the naming so this reflects better and we can try and build some sort of ordering to the naming scheme. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
We can stuff things like the number of pipes and the SGX offset away in here as well and clean up more conditional code. Signed-off-by:
-
Alan Cox authored
This is a Medfield only path Signed-off-by:
-
Alan Cox authored
Split the 2d properties, name, and various function vectors out so that we can get rid of more conditional gloop in favour of a per device structure. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Missed in the original merge work Signed-off-by:
-
Alan Cox authored
We need to initialise the DBI interface and the code for it got missed in the original merge as it's in a daft place. This will need moving but lets get it added first. Signed-off-by:
-
Alan Cox authored
Next obvious target - backlight support Signed-off-by:
-
Alan Cox authored
We really want to move towards a completely abstracted interface rather than having tons of per chip junk in the same files. Begin with the power code which is probably the worst offender. Add a set of methods, initialise a dev_priv->ops pointer and rip the chip specifics out of the power code. While we are it pick up the display init bits. So we know it's now chip specifics clean remove the psb_ naming from it. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
We also pull out the undo side of the mmap offset processing so we can later push it into GEM where it belongs Signed-off-by:
-
Alan Cox authored
Eliminate unused stuff and clean up the code ordering. Signed-off-by:
-
Alan Cox authored
This is too big already so lets rip out more of the device specific crud. It also means we pull the ugly stuff that needs work out of our main line of cleanup. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
This large patch adds all the basics for Medfield support. Lots of clean up needed in this area still. Signed-off-by:
-
Alan Cox authored
Tidy up the 2D bits. For the fill case the CPU seems to be able to outperform the graphics engine for the cases we get, so don't bother fixing it but throw it out. Signed-off-by:
-
Alan Cox authored
Start the style cleanup Signed-off-by:
-
Alan Cox authored
We can now make our system frame buffer a GEM object. Signed-off-by:
-
Alan Cox authored
Add this temporarily so we can keep making progress and also bundle all the GEM bits we need together in our staging driver while we get them into GEM itself. Signed-off-by:
-
Alan Cox authored
We are using the underlying kref in the GEM object so we don't need our own Signed-off-by:
-
Alan Cox authored
Lose all the PSB debug gunge. We can replace it with dev_dbg() like normal drivers if and when we need debug on stuff. Signed-off-by:
-
Alan Cox authored
We don't seem to need this for our task. Signed-off-by:
-
Alan Cox authored
We have a FIXME to do the power management for which the framework now exists, and we also need to deal with an erratum. Some operations exactly 8 pixels wide or high fail. The work around is to do two smaller ones (see the Intel released X driver bits) but for console quite frankly if it's 8bits wide and/or high its not worth it so fall back. Signed-off-by:
-
Alan Cox authored
Give the driver its own proper DRM name, clean up copyright headers and so forth Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
If we get a user frame buffer destroyed which is being displayed then clean up the mess nicely. We can now run a slightly modified modetest including setting modes, and handling crashes. Modetest still blows up but this is because libdrm 2.4.25 is busted. Signed-off-by:
-
Alan Cox authored
Restructure this to work the same way as the i915 frame buffer does. That cleans up various chunks of code. We can now set a mode in modetest but mode restore is a bit iffy Signed-off-by:
-
Alan Cox authored
We need this for the framebuffer in order to ensure that the kernel framebuffer layer can handle it when using KMS. Except for the base framebuffer this isn't a concern. Add an npage field to the gtt as too many copies of the page calculation are getting spread around the code. Signed-off-by:
-
Greg Kroah-Hartman authored
This handles the merge conflicts with the drivers/staging/brcm80211/Kconfig file due to changes on the two different branches. Signed-off-by:
-
- 04 Jul, 2011 1 commit
-
-
Linus Torvalds authored
-
