1. 08 Nov, 2017 1 commit
  2. 04 Sep, 2017 1 commit
  3. 18 Aug, 2017 1 commit
    • David Lechner's avatar
      fbcon: add fbcon=margin:<color> command line option · 74c1c8b3
      David Lechner authored
      This adds a new command line option to select the fbcon margin color.
      The motivation for this is screens where black does not blend into the
      physical surroundings of the screen. For example, using an LCD (not the
      backlit kind), white text on a black background is hard to read, so
      inverting the colors is preferred. However, when you do this, most of the
      screen is filled with white but the margins are still filled with black.
      This makes a big, black, backwards 'L' on the screen. By setting
      fbcon=margin:7, the margins will be filled with white and the LCD looks as
      Signed-off-by: default avatarDavid Lechner <david@lechnology.com>
      [b.zolnierkie: ported over fbcon changes]
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
  4. 31 Jul, 2017 1 commit
    • Dave Airlie's avatar
      efifb: allow user to disable write combined mapping. · dd0c41f8
      Dave Airlie authored
      This patch allows the user to disable write combined mapping
      of the efifb framebuffer console using an nowc option.
      A customer noticed major slowdowns while logging to the console
      with write combining enabled, on other tasks running on the same
      CPU. (10x or greater slow down on all other cores on the same CPU
      as is doing the logging).
      I reproduced this on a machine with dual CPUs.
      Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz (6 core)
      I wrote a test that just mmaps the pci bar and writes to it in
      a loop, while this was running in the background one a single
      core with (taskset -c 1), building a kernel up to init/version.o
      (taskset -c 8) went from 13s to 133s or so. I've yet to explain
      why this occurs or what is going wrong I haven't managed to find
      a perf command that in any way gives insight into this.
          11,885,070,715      instructions              #    1.39  insns per cycle
          12,082,592,342      instructions              #    0.13  insns per cycle
      is the only thing I've spotted of interest, I've tried at least:
      For now it seems at least a good idea to allow a user to disable write
      combining if they see this until we can figure it out.
      Note also most users get a real framebuffer driver loaded when kms
      kicks in, it just happens on these machines the kernel didn't support
      the gpu specific driver.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      Acked-by: default avatarPeter Jones <pjones@redhat.com>
      Cc: Andy Lutomirski <luto@kernel.org>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
  5. 16 May, 2017 1 commit
  6. 10 May, 2016 1 commit
  7. 07 Aug, 2015 1 commit
  8. 05 May, 2014 1 commit
  9. 11 Feb, 2014 1 commit
    • Henrik Austad's avatar
      Documentation/: update 00-INDEX files · 3cf8ca1c
      Henrik Austad authored
      Some of the 00-INDEX files are somewhat outdated and some folders does
      not contain 00-INDEX at all.  Only outdated (with the notably exception
      of spi) indexes are touched here, the 169 folders without 00-INDEX has
      not been touched.
      New 00-INDEX
       - spi/* was added in a series of commits dating back to 2006
      Added files (missing in (*/)00-INDEX)
       - dmatest.txt was added by commit 851b7e16 ("dmatest: run test via
       - this_cpu_ops.txt was added by commit a1b2a555 ("percpu: add
         documentation on this_cpu operations")
       - ww-mutex-design.txt was added by commit 040a0a37 ("mutex: Add
         support for wound/wait style locks")
       - bcache.txt was added by commit cafe5635 ("bcache: A block layer
       - kernel-per-CPU-kthreads.txt was added by commit 49717cb4
         ("kthread: Document ways of reducing OS jitter due to per-CPU
       - phy.txt was added by commit ff764963 ("drivers: phy: add generic
         PHY framework")
       - block/null_blk was added by commit 12f8f4fc ("null_blk:
       - module-signing.txt was added by commit 3cafea30 ("Add
         Documentation/module-signing.txt file")
       - assoc_array.txt was added by commit 3cb98950 ("Add a generic
         associative array implementation.")
       - arm/IXP4xx was part of the initial repo
       - arm/cluster-pm-race-avoidance.txt was added by commit 7fe31d28
         ("ARM: mcpm: introduce helpers for platform coherency exit/setup")
       - arm/firmware.txt was added by commit 7366b92a ("ARM: Add
         interface for registering and calling firmware-specific operations")
       - arm/kernel_mode_neon.txt was added by commit 2afd0a05 ("ARM:
         7825/1: document the use of NEON in kernel mode")
       - arm/tcm.txt was added by commit bc581770 ("ARM: 5580/2: ARM TCM
         (Tightly-Coupled Memory) support v3")
       - arm/vlocks.txt was added by commit 9762f12d ("ARM: mcpm: Add
         baremetal voting mutexes")
       - blackfin/gptimers-example.c, Makefile was added by commit
         4b60779d ("Blackfin: add an example showing how to use the
         gptimers API")
       - devicetree/usage-model.txt was added by commit 31134efc ("dt:
         Linux DT usage model documentation")
       - fb/api.txt was added by commit fb21c2f4 ("fbdev: Add FOURCC-based
         format configuration API")
       - fb/sm501.txt was added by commit e6a04980 ("video, sm501: add
         edid and commandline support")
       - fb/udlfb.txt was added by commit 96f8d864 ("fbdev: move udlfb out
         of staging.")
       - filesystems/Makefile was added by commit 1e0051ae
         ("Documentation/fs/: split txt and source files")
       - filesystems/nfs/nfsd-admin-interfaces.txt was added by commit
         8a4c6e19 ("nfsd: document kernel interfaces for nfsd
       - ide/warm-plug-howto.txt was added by commit f74c9141 ("ide: add
         warm-plug support for IDE devices (take 2)")
       - laptops/Makefile was added by commit d49129ac
         ("Documentation/laptop/: split txt and source files")
       - leds/leds-blinkm.txt was added by commit b54cf35a ("LEDS: add
         BlinkM RGB LED driver, documentation and update MAINTAINERS")
       - leds/ledtrig-oneshot.txt was added by commit 5e417281 ("leds: add
         oneshot trigger")
       - leds/ledtrig-transient.txt was added by commit 44e1e9f8 ("leds:
         add new transient trigger for one shot timer activation")
       - m68k/README.buddha was part of the initial repo
       - networking/LICENSE.(qla3xxx|qlcnic|qlge) was added by commits
         40839129, c4e84bde, 5a4faa87
       - networking/Makefile was added by commit 3794f3e8 ("docsrc: build
         Documentation/ sources")
       - networking/i40evf.txt was added by commit 105bf2fe ("i40evf: add
         driver to kernel build system")
       - networking/ipsec.txt was added by commit b3c6efbc ("xfrm: Add
         file to document IPsec corner case")
       - networking/mac80211-auth-assoc-deauth.txt was added by commit
         3cd7920a ("mac80211: add auth/assoc/deauth flow diagram")
       - networking/netlink_mmap.txt was added by commit 5683264c
         ("netlink: add documentation for memory mapped I/O")
       - networking/nf_conntrack-sysctl.txt was added by commit c9f9e0e1
         ("netfilter: doc: add nf_conntrack sysctl api documentation") lan)
       - networking/team.txt was added by commit 3d249d4c ("net: introduce
         ethernet teaming device")
       - networking/vxlan.txt was added by commit d342894c ("vxlan:
         virtual extensible lan")
       - power/runtime_pm.txt was added by commit 5e928f77 ("PM: Introduce
         core framework for run-time PM of I/O devices (rev.  17)")
       - power/charger-manager.txt was added by commit 3bb3dbbd
         ("power_supply: Add initial Charger-Manager driver")
       - RCU/lockdep-splat.txt was added by commit d7bd2d68 ("rcu:
         Document interpretation of RCU-lockdep splats")
       - s390/kvm.txt was added by 5ecee4ba (KVM: s390: API documentation)
       - s390/qeth.txt was added by commit b4d72c08 ("qeth: bridgeport
         support - basic control")
       - scheduler/sched-bwc.txt was added by commit 88ebc08e ("sched: Add
         documentation for bandwidth control")
       - scsi/advansys.txt was added by commit 4bd6d7f3 ("[SCSI] advansys:
         Move documentation to Documentation/scsi")
       - scsi/bfa.txt was added by commit 1ec90174 ("[SCSI] bfa: add
         readme file")
       - scsi/bnx2fc.txt was added by commit 12b8fc10 ("[SCSI] bnx2fc: Add
         driver documentation")
       - scsi/cxgb3i.txt was added by commit c3673464 ("[SCSI] cxgb3i: Add
         cxgb3i iSCSI driver.")
       - scsi/hpsa.txt was added by commit 992ebcf1 ("[SCSI] hpsa: Add
         hpsa.txt to Documentation/scsi")
       - scsi/link_power_management_policy.txt was added by commit
         ca77329f ("[libata] Link power management infrastructure")
       - scsi/osd.txt was added by commit 78e0c621 ("[SCSI] osd:
         Documentation for OSD library")
       - scsi/scsi-parameter.txt was created/moved by commit 163475fb
         ("Documentation: move SCSI parameters to their own text file")
       - serial/driver was part of the initial repo
       - serial/n_gsm.txt was added by commit 323e8412 ("n_gsm: add a
       - timers/Makefile was added by commit 3794f3e8 ("docsrc: build
         Documentation/ sources")
       - virt/kvm/s390.txt was added by commit d9101fca ("KVM: s390:
         diagnose call documentation")
       - vm/split_page_table_lock was added by commit 49076ec2 ("mm:
         dynamically allocate page->ptl if it cannot be embedded to struct
       - w1/slaves/w1_ds28e04 was added by commit fbf7f7b4 ("w1: Add
         1-wire slave device driver for DS28E04-100")
       - w1/masters/omap-hdq was added by commit e0a29382 ("hdq:
         documentation for OMAP HDQ")
       - x86/early-microcode.txt was added by commit 0d91ea86 ("x86, doc:
         Documentation for early microcode loading")
       - x86/earlyprintk.txt was added by commit a1aade47 ("x86/doc:
         mini-howto for using earlyprintk=dbgp")
       - x86/entry_64.txt was added by commit 8b4777a4 ("x86-64: Document
         some of entry_64.S")
       - x86/pat.txt was added by commit d27554d8 ("x86: PAT
      Moved files
       - arm/kernel_user_helpers.txt was moved out of arch/arm/kernel by
         commit 37b83046 ("ARM: kuser: move interface documentation out of
         the source code")
       - efi-stub.txt was moved out of x86/ and down into Documentation/ in
         commit 4172fe2f ("EFI stub documentation updates")
       - laptops/hpfall.c was moved out of hwmon/ and into laptops/ in commit
         efcfed9b ("Move hp_accel to drivers/platform/x86")
       - commit 5616c23a ("x86: doc: move x86-generic documentation from
         * x86/usb-legacy-support.txt
         * x86/boot.txt
         * x86/zero_page.txt
       - power/video_extension.txt was moved to acpi in commit 70e66e4d
         ("ACPI / video: move video_extension.txt to Documentation/acpi")
      Removed files (left in 00-INDEX)
       - memory.txt was removed by commit 00ea8990 ("memory.txt: remove
         stray information")
       - gpio.txt was moved to gpio/ in commit fd8e198c ("Documentation:
         gpiolib: document new interface")
       - networking/DLINK.txt was removed by commit 168e06ae
         ("drivers/net: delete old parallel port de600/de620 drivers")
       - serial/hayes-esp.txt was removed by commit f53a2ade ("tty: esp:
         remove broken driver")
       - s390/TAPE was removed by commit 9e280f66 ("[S390] remove tape
         block docu")
       - vm/locking was removed by commit 57ea8171 ("mm: documentation:
         remove hopelessly out-of-date locking doc")
       - laptops/acer-wmi.txt was remvoed by commit 02003667 ("acer-wmi:
         Delete out-of-date documentation")
      Typos/misc issues
       - rpc-server-gss.txt was added as knfsd-rpcgss.txt in commit
         030d794b ("SUNRPC: Use gssproxy upcall for server RPCGSS
       - commit b88cf73d ("net: add missing entries to
         * generic-hdlc.txt was added as generic_hdlc.txt
         * spider_net.txt was added as spider-net.txt
       - w1/master/mxc-w1 was added as mxc_w1 by commit a5fd9139 ("w1: add
         1-wire master driver for i.MX27 / i.MX31")
       - s390/zfcpdump.txt was added as zfcpdump by commit 6920c12a
         ("[S390] Add Documentation/s390/00-INDEX.")
      Signed-off-by: default avatarHenrik Austad <henrik@austad.us>
      Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>	[rcu bits]
      Acked-by: default avatarRob Landley <rob@landley.net>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: Mark Brown <broonie@kernel.org>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Gleb Natapov <gleb@kernel.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Len Brown <len.brown@intel.com>
      Cc: James Bottomley <JBottomley@parallels.com>
      Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  10. 20 Aug, 2013 1 commit
  11. 25 Jul, 2013 1 commit
  12. 31 May, 2013 1 commit
    • Andy Lutomirski's avatar
      uvesafb: Clean up MTRR code · 63e28a7a
      Andy Lutomirski authored
      The old code allowed very strange memory types.  Now it works like
      all the other video drivers: ioremap_wc is used unconditionally,
      and MTRRs are set if PAT is unavailable (unless MTRR is disabled
      by a module parameter).
      UC, WB, and WT support is gone.  If there are MTRR conflicts that prevent
      addition of a WC MTRR, adding a non-conflicting MTRR is pointless; it's
      better to just turn off MTRR support entirely.
      As an added bonus, any MTRR added is freed on unload.
      Reviewed-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarAndy Lutomirski <luto@amacapital.net>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
  13. 28 May, 2013 1 commit
  14. 30 Mar, 2012 1 commit
  15. 07 Mar, 2012 1 commit
  16. 19 Dec, 2011 1 commit
  17. 24 Aug, 2011 3 commits
  18. 25 Jul, 2011 1 commit
    • Rolf Eike Beer's avatar
      DRM: clean up and document parsing of video= parameter · 04fee895
      Rolf Eike Beer authored
      The video= parameter of the DRM drivers supports some additional flags that
      the normal fb drivers do not have. They also allow to limit these flags to
      specific outputs. Both things were previously undocumented.
      Also the parsing of the line had some oddities:
      -A lot of misplaced options were silently ignored or partly rejected instead
       of stopping the parsing immediately
      -The 'R' option is documented to follow the 'M' option if specified. It is not
       documented that 'M' is needed to specify 'R' (also this is the case for normal
       fb drivers). In fact the code is correct for normal fb drivers but wrong for
       DRM ones.
       The old code allowed 'R' only _before_ 'M' (since it parses backwards) and only
       if 'M' is given at all which is not needed for the DRM drivers.
      -the margins option ('m') was parsed but later ignored even if the later
       functions support it.
      -specifying multiple enable options at the same time did not lead to an error.
      -specifying something bogus for horizontal resolution (i.e. other things as
       digits) did not lead to an error but an invalid resolution was used.
      If any errors are encountered the position of the faulting string is now
      printed to the user and the complete mode is ignored. This gives much
      more consistent error behaviour.
      I also removed some useless assignments and changed the local flag variables
      to be bool.
      Signed-off-by: default avatarRolf Eike Beer <eike-kernel@sf-tec.de>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
  19. 31 Mar, 2011 1 commit
  20. 22 Mar, 2011 1 commit
    • Heiko Schocher's avatar
      video, sm501: add edid and commandline support · e6a04980
      Heiko Schocher authored
      - add commandline options:
          Specify resolution as "<xres>x<yres>[-<bpp>][@<refresh>]"
          Specify bit-per-pixel if not specified mode
      - Add support for encoding display mode information
        in the device tree using verbatim EDID block.
        If the "edid" entry in the "smi,sm501" node is present,
        the driver will build mode database using EDID data
        and allow setting the display modes from this database.
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      cc: linux-fbdev@vger.kernel.org
      cc: devicetree-discuss@ozlabs.org
      cc: Ben Dooks <ben@simtec.co.uk>
      cc: Vincent Sanders <vince@simtec.co.uk>
      cc: Samuel Ortiz <sameo@linux.intel.com>
      cc: linux-kernel@vger.kernel.org
      cc: Randy Dunlap <rdunlap@xenotime.net>
      cc: Paul Mundt <lethal@linux-sh.org>
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
  21. 18 Nov, 2010 1 commit
  22. 16 Nov, 2010 1 commit
  23. 24 Sep, 2010 1 commit
  24. 04 Aug, 2010 1 commit
    • Justin P. Mattock's avatar
      Documentation: update broken web addresses. · 0ea6e611
      Justin P. Mattock authored
      Below you will find an updated version from the original series bunching all patches into one big patch
      updating broken web addresses that are located in Documentation/*
      Some of the addresses date as far far back as 1995 etc... so searching became a bit difficult,
      the best way to deal with these is to use web.archive.org to locate these addresses that are outdated.
      Now there are also some addresses pointing to .spec files some are located, but some(after searching
      on the companies site)where still no where to be found. In this case I just changed the address
      to the company site this way the users can contact the company and they can locate them for the users.
      Signed-off-by: default avatarJustin P. Mattock <justinmattock@gmail.com>
      Signed-off-by: default avatarThomas Weber <weber@corscience.de>
      Signed-off-by: default avatarMike Frysinger <vapier.adi@gmail.com>
      Cc: Paulo Marques <pmarques@grupopie.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Cc: Michael Neuling <mikey@neuling.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  25. 07 Apr, 2010 1 commit
  26. 16 Dec, 2009 1 commit
  27. 30 Nov, 2009 1 commit
  28. 23 Sep, 2009 2 commits
    • Jean Delvare's avatar
      matroxfb: make CONFIG_FB_MATROX_MULTIHEAD=y mandatory · 0728bacb
      Jean Delvare authored
      I would like to get rid of option CONFIG_FB_MATROX_MULTIHEAD and just
      always enable it.  There are many reasons for doing this:
      * CONFIG_FB_MATROX_MULTIHEAD=y is what all x86 distributions do, so it
        definitely works or we would know by now.
      * Building the matroxfb driver with CONFIG_FB_MATROX_MULTIHEAD not set
        results in the following build warning:
      drivers/video/matrox/matroxfb_crtc2.c: In function 'matroxfb_dh_open':
      drivers/video/matrox/matroxfb_crtc2.c:265: warning: the address of 'matroxfb_global_mxinfo' will always evaluate as 'true'
      drivers/video/matrox/matroxfb_crtc2.c: In function 'matroxfb_dh_release':
      drivers/video/matrox/matroxfb_crtc2.c:285: warning: the address of 'matroxfb_global_mxinfo' will always evaluate as 'true'
      This is nothing to be worried about, the driver will work fine, but build
      warnings are still annoying.
      * The trick to get multihead support without CONFIG_FB_MATROX_MULTIHEAD,
        which is described in the config help text, no longer works: you can't
        load the same kernel module more than once.
      * I fail to see how CONFIG_FB_MATROX_MULTIHEAD=y would make the code
        significantly slower, contrary to what the help text says.  A few extra
        parameters on the stack here and there can't really slow things down in
        comaprison to the rest of the code, and register access.
      * The driver built without CONFIG_FB_MATROX_MULTIHEAD is larger than the
        driver build with CONFIG_FB_MATROX_MULTIHEAD=y by 8%.
      * One less configuration option makes things simpler.  We add options
        all the time, being able to remove one for once is nice.  It improves
        testing coverage.  And I don't think the Matrox adapters are still
        popular enough to warrant overdetailed configuration settings.
      * We should be able to unobfuscate the driver code quite a bit after
        this change (patches follow.)
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarPetr Vandrovec <vandrove@vc.cvut.cz>
      Cc: Krzysztof Helt <krzysztof.h1@poczta.fm>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • Ryan Mallon's avatar
      ep93xx video driver · 88017bda
      Ryan Mallon authored
      EP93xx video driver plus documentation.
      Signed-off-by: default avatarRyan Mallon <ryan@bluewatersys.com>
      Acked-by: default avatarH Hartley Sweeten <hsweeten@visionengravers.com>
      Cc: Daniele Venzano <linux@brownhat.org>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Krzysztof Helt <krzysztof.h1@poczta.fm>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  29. 17 Jun, 2009 1 commit
  30. 12 Jun, 2009 1 commit
  31. 07 Apr, 2009 1 commit
  32. 01 Apr, 2009 1 commit
    • Krzysztof Helt's avatar
      fbdev: remove cyblafb driver · ddb53d48
      Krzysztof Helt authored
      A tridentfb driver has all the functionality of the cyblafb driver without
      the bugs of the latter.
      Changes to the tridentfb driver:
      - FBINFO_READS_FAST added to the tridentfb.  The cyblafb used a blitter
        for scrolling which is faster than color expansion on Cyberblade
        chipsets.  The blitter is slower on a discrete Blade3D core.  Use the
        blitter for scrolling in the tridentfb only for integrated Blade3D
        cores.  Now, scrolling speed is about equal for the tridentfb and the
      - a copyright notice addition is done on request of Jani Monoses (the
        first author of the tridentfb).
      Tested on AGP Blade3D card and PCChips
      M787CLR motherboard: VIA C3 cpu +
      VT8601 north  bridge (aka Cyberblade/i1).
      Signed-off-by: default avatarKrzysztof Helt <krzysztof.h1@wp.pl>
      Cc: "Jani Monoses" <jani@ubuntu.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  33. 29 Dec, 2008 2 commits
    • Eric Miao's avatar
      [ARM] pxafb: add support for overlay1 and overlay2 as framebuffer devices · 198fc108
      Eric Miao authored
      PXA27x and later processors support overlay1 and overlay2 on-top of the
      base framebuffer (although under-neath the base is also possible). They
      support palette and no-palette RGB formats, as well as YUV formats (only
      available on overlay2). These overlays have dedicated DMA channels and
      behave in a similar way as a framebuffer.
      This heavily simplified and re-structured work is based on the original
      pxafb_overlay.c (which is pending for mainline merge for a long time).
      The major problems with this pxafb_overlay.c are (if you are interested
      in the history):
        1. heavily redundant (the control logics for overlay1 and overlay2 are
           actually identical except for some small operations,  which are now
           abstracted into a 'pxafb_layer_ops' structure)
        2. a lot of useless and un-tested code (two workarounds which are now
           fixed on mature silicons)
        3. cursorfb is actually useless, hardware cursor should not be used
           this way, and the code was actually un-tested for a long time.
      The code in this patch should be self-explanatory, I tried to add minimum
      comments. As said, this is basically simplified, there are several things
      still on the pending list:
        1. palette mode is un-supported and un-tested (although re-using the
           palette code of the base framebuffer is actually very easy now with
           previous clean-up patches)
        2. fb_pan_display for overlay(s) is un-supported
        3. the base framebuffer can actually be abstracted by 'pxafb_layer' as
           well, which will help further re-use of the code and keep a better
           and consistent structure. (This is the reason I named it 'pxafb_layer'
           instead of 'pxafb_overlay' or something alike)
      See Documentation/fb/pxafb.txt for additional usage information.
      Signed-off-by: default avatarEric Miao <eric.miao@marvell.com>
      Cc: Rodolfo Giometti <giometti@linux.it>
      Signed-off-by: default avatarEric Miao <ycmiao@ycmiao-hp520.(none)>
    • Eric Miao's avatar
      [ARM] pxafb: allow video memory size to be configurable · 77e19675
      Eric Miao authored
      The amount of video memory size is decided according to the following
      1. <xres> x <yres> x <bits_per_pixel> by default, which is the backward
         compatible way
      2. size specified in platform data
      3. size specified in module parameter 'options' string or specified in
         kernel boot command line (see updated Documentation/fb/pxafb.txt)
      And now since the memory is allocated from system memory, the pxafb_mmap
      can be removed and the default fb_mmap() should be working all right.
      Also, since we now have introduced the 'struct pxafb_dma_buff' for DMA
      descriptors and palettes, the allocation can be separated cleanly.
      NOTE: the LCD DMA actually supports chained transfer (i.e. page-based
      transfers), to simplify the logic and keep the performance (with less
      TLB misses when accessing from memory mapped user space), the memory
      is allocated by alloc_pages_*() to ensures it's physical contiguous.
      Signed-off-by: default avatarEric Miao <eric.miao@marvell.com>
      Signed-off-by: default avatarEric Miao <ycmiao@ycmiao-hp520.(none)>
  34. 16 Oct, 2008 3 commits