10 May, 2016

1 commit


08 Aug, 2015

1 commit


05 May, 2014

1 commit


11 Feb, 2014

1 commit

  • 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 851b7e16a07d ("dmatest: run test via
    debugfs")
    - this_cpu_ops.txt was added by commit a1b2a555d637 ("percpu: add
    documentation on this_cpu operations")
    - ww-mutex-design.txt was added by commit 040a0a371005 ("mutex: Add
    support for wound/wait style locks")
    - bcache.txt was added by commit cafe56359144 ("bcache: A block layer
    cache")
    - kernel-per-CPU-kthreads.txt was added by commit 49717cb40410
    ("kthread: Document ways of reducing OS jitter due to per-CPU
    kthreads")
    - phy.txt was added by commit ff764963479a ("drivers: phy: add generic
    PHY framework")
    - block/null_blk was added by commit 12f8f4fc0314 ("null_blk:
    documentation")
    - module-signing.txt was added by commit 3cafea307642 ("Add
    Documentation/module-signing.txt file")
    - assoc_array.txt was added by commit 3cb989501c26 ("Add a generic
    associative array implementation.")
    - arm/IXP4xx was part of the initial repo
    - arm/cluster-pm-race-avoidance.txt was added by commit 7fe31d28e839
    ("ARM: mcpm: introduce helpers for platform coherency exit/setup")
    - arm/firmware.txt was added by commit 7366b92a77fc ("ARM: Add
    interface for registering and calling firmware-specific operations")
    - arm/kernel_mode_neon.txt was added by commit 2afd0a05241d ("ARM:
    7825/1: document the use of NEON in kernel mode")
    - arm/tcm.txt was added by commit bc581770cfdd ("ARM: 5580/2: ARM TCM
    (Tightly-Coupled Memory) support v3")
    - arm/vlocks.txt was added by commit 9762f12d3e05 ("ARM: mcpm: Add
    baremetal voting mutexes")
    - blackfin/gptimers-example.c, Makefile was added by commit
    4b60779d5ea7 ("Blackfin: add an example showing how to use the
    gptimers API")
    - devicetree/usage-model.txt was added by commit 31134efc681a ("dt:
    Linux DT usage model documentation")
    - fb/api.txt was added by commit fb21c2f42879 ("fbdev: Add FOURCC-based
    format configuration API")
    - fb/sm501.txt was added by commit e6a049807105 ("video, sm501: add
    edid and commandline support")
    - fb/udlfb.txt was added by commit 96f8d864afd6 ("fbdev: move udlfb out
    of staging.")
    - filesystems/Makefile was added by commit 1e0051ae48a2
    ("Documentation/fs/: split txt and source files")
    - filesystems/nfs/nfsd-admin-interfaces.txt was added by commit
    8a4c6e19cfed ("nfsd: document kernel interfaces for nfsd
    configuration")
    - ide/warm-plug-howto.txt was added by commit f74c91413ec6 ("ide: add
    warm-plug support for IDE devices (take 2)")
    - laptops/Makefile was added by commit d49129accc21
    ("Documentation/laptop/: split txt and source files")
    - leds/leds-blinkm.txt was added by commit b54cf35a7f65 ("LEDS: add
    BlinkM RGB LED driver, documentation and update MAINTAINERS")
    - leds/ledtrig-oneshot.txt was added by commit 5e417281cde2 ("leds: add
    oneshot trigger")
    - leds/ledtrig-transient.txt was added by commit 44e1e9f8e705 ("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
    40839129f779, c4e84bde1d59, 5a4faa873782
    - networking/Makefile was added by commit 3794f3e812ef ("docsrc: build
    Documentation/ sources")
    - networking/i40evf.txt was added by commit 105bf2fe6b32 ("i40evf: add
    driver to kernel build system")
    - networking/ipsec.txt was added by commit b3c6efbc36e2 ("xfrm: Add
    file to document IPsec corner case")
    - networking/mac80211-auth-assoc-deauth.txt was added by commit
    3cd7920a2be8 ("mac80211: add auth/assoc/deauth flow diagram")
    - networking/netlink_mmap.txt was added by commit 5683264c3981
    ("netlink: add documentation for memory mapped I/O")
    - networking/nf_conntrack-sysctl.txt was added by commit c9f9e0e1597f
    ("netfilter: doc: add nf_conntrack sysctl api documentation") lan)
    - networking/team.txt was added by commit 3d249d4ca7d0 ("net: introduce
    ethernet teaming device")
    - networking/vxlan.txt was added by commit d342894c5d2f ("vxlan:
    virtual extensible lan")
    - power/runtime_pm.txt was added by commit 5e928f77a09a ("PM: Introduce
    core framework for run-time PM of I/O devices (rev. 17)")
    - power/charger-manager.txt was added by commit 3bb3dbbd56ea
    ("power_supply: Add initial Charger-Manager driver")
    - RCU/lockdep-splat.txt was added by commit d7bd2d68aa2e ("rcu:
    Document interpretation of RCU-lockdep splats")
    - s390/kvm.txt was added by 5ecee4b (KVM: s390: API documentation)
    - s390/qeth.txt was added by commit b4d72c08b358 ("qeth: bridgeport
    support - basic control")
    - scheduler/sched-bwc.txt was added by commit 88ebc08ea9f7 ("sched: Add
    documentation for bandwidth control")
    - scsi/advansys.txt was added by commit 4bd6d7f35661 ("[SCSI] advansys:
    Move documentation to Documentation/scsi")
    - scsi/bfa.txt was added by commit 1ec90174bdb4 ("[SCSI] bfa: add
    readme file")
    - scsi/bnx2fc.txt was added by commit 12b8fc10eaf4 ("[SCSI] bnx2fc: Add
    driver documentation")
    - scsi/cxgb3i.txt was added by commit c3673464ebc0 ("[SCSI] cxgb3i: Add
    cxgb3i iSCSI driver.")
    - scsi/hpsa.txt was added by commit 992ebcf14f3c ("[SCSI] hpsa: Add
    hpsa.txt to Documentation/scsi")
    - scsi/link_power_management_policy.txt was added by commit
    ca77329fb713 ("[libata] Link power management infrastructure")
    - scsi/osd.txt was added by commit 78e0c621deca ("[SCSI] osd:
    Documentation for OSD library")
    - scsi/scsi-parameter.txt was created/moved by commit 163475fb111c
    ("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 323e84122ec6 ("n_gsm: add a
    documentation")
    - timers/Makefile was added by commit 3794f3e812ef ("docsrc: build
    Documentation/ sources")
    - virt/kvm/s390.txt was added by commit d9101fca3d57 ("KVM: s390:
    diagnose call documentation")
    - vm/split_page_table_lock was added by commit 49076ec2ccaf ("mm:
    dynamically allocate page->ptl if it cannot be embedded to struct
    page")
    - w1/slaves/w1_ds28e04 was added by commit fbf7f7b4e2ae ("w1: Add
    1-wire slave device driver for DS28E04-100")
    - w1/masters/omap-hdq was added by commit e0a29382c6f5 ("hdq:
    documentation for OMAP HDQ")
    - x86/early-microcode.txt was added by commit 0d91ea86a895 ("x86, doc:
    Documentation for early microcode loading")
    - x86/earlyprintk.txt was added by commit a1aade478862 ("x86/doc:
    mini-howto for using earlyprintk=dbgp")
    - x86/entry_64.txt was added by commit 8b4777a4b50c ("x86-64: Document
    some of entry_64.S")
    - x86/pat.txt was added by commit d27554d874c7 ("x86: PAT
    documentation")

    Moved files
    - arm/kernel_user_helpers.txt was moved out of arch/arm/kernel by
    commit 37b8304642c7 ("ARM: kuser: move interface documentation out of
    the source code")
    - efi-stub.txt was moved out of x86/ and down into Documentation/ in
    commit 4172fe2f8a47 ("EFI stub documentation updates")
    - laptops/hpfall.c was moved out of hwmon/ and into laptops/ in commit
    efcfed9bad88 ("Move hp_accel to drivers/platform/x86")
    - commit 5616c23ad9cd ("x86: doc: move x86-generic documentation from
    Doc/x86/i386"):
    * x86/usb-legacy-support.txt
    * x86/boot.txt
    * x86/zero_page.txt
    - power/video_extension.txt was moved to acpi in commit 70e66e4df191
    ("ACPI / video: move video_extension.txt to Documentation/acpi")

    Removed files (left in 00-INDEX)
    - memory.txt was removed by commit 00ea8990aadf ("memory.txt: remove
    stray information")
    - gpio.txt was moved to gpio/ in commit fd8e198cfcaa ("Documentation:
    gpiolib: document new interface")
    - networking/DLINK.txt was removed by commit 168e06ae26dd
    ("drivers/net: delete old parallel port de600/de620 drivers")
    - serial/hayes-esp.txt was removed by commit f53a2ade0bb9 ("tty: esp:
    remove broken driver")
    - s390/TAPE was removed by commit 9e280f669308 ("[S390] remove tape
    block docu")
    - vm/locking was removed by commit 57ea8171d2bc ("mm: documentation:
    remove hopelessly out-of-date locking doc")
    - laptops/acer-wmi.txt was remvoed by commit 020036678e81 ("acer-wmi:
    Delete out-of-date documentation")

    Typos/misc issues
    - rpc-server-gss.txt was added as knfsd-rpcgss.txt in commit
    030d794bf498 ("SUNRPC: Use gssproxy upcall for server RPCGSS
    authentication.")
    - commit b88cf73d9278 ("net: add missing entries to
    Documentation/networking/00-INDEX")
    * 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 a5fd9139f74c ("w1: add
    1-wire master driver for i.MX27 / i.MX31")
    - s390/zfcpdump.txt was added as zfcpdump by commit 6920c12a407e
    ("[S390] Add Documentation/s390/00-INDEX.")

    Signed-off-by: Henrik Austad
    Reviewed-by: Paul E. McKenney [rcu bits]
    Acked-by: Rob Landley
    Cc: Jiri Kosina
    Cc: Thomas Gleixner
    Cc: Rob Herring
    Cc: David S. Miller
    Cc: Mark Brown
    Cc: "H. Peter Anvin"
    Cc: Ingo Molnar
    Cc: Gleb Natapov
    Cc: Linus Torvalds
    Cc: Len Brown
    Cc: James Bottomley
    Cc: Jean-Christophe Plagniol-Villard
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Henrik Austad
     

20 Aug, 2013

1 commit


25 Jul, 2013

1 commit


10 Jul, 2013

1 commit

  • Pull drm updates from Dave Airlie:
    "Okay this is the big one, I was stalled on the fbdev pull req as I
    stupidly let fbdev guys merge a patch I required to fix a warning with
    some patches I had, they ended up merging the patch from the wrong
    place, but the warning should be fixed. In future I'll just take the
    patch myself!

    Outside drm:

    There are some snd changes for the HDMI audio interactions on haswell,
    they've been acked for inclusion via my tree. This relies on the
    wound/wait tree from Ingo which is already merged.

    Major changes:

    AMD finally released the dynamic power management code for all their
    GPUs from r600->present day, this is great, off by default for now but
    also a huge amount of code, in fact it is most of this pull request.

    Since it landed there has been a lot of community testing and Alex has
    sent a lot of fixes for any bugs found so far. I suspect radeon might
    now be the biggest kernel driver ever :-P p.s. radeon.dpm=1 to enable
    dynamic powermanagement for anyone.

    New drivers:

    Renesas r-car display unit.

    Other highlights:

    - core: GEM CMA prime support, use new w/w mutexs for TTM
    reservations, cursor hotspot, doc updates
    - dvo chips: chrontel 7010B support
    - i915: Haswell (fbc, ips, vecs, watermarks, audio powerwell),
    Valleyview (enabled by default, rc6), lots of pll reworking, 30bpp
    support (this time for sure)
    - nouveau: async buffer object deletion, context/register init
    updates, kernel vp2 engine support, GF117 support, GK110 accel
    support (with external nvidia ucode), context cleanups.
    - exynos: memory leak fixes, Add S3C64XX SoC series support, device
    tree updates, common clock framework support,
    - qxl: cursor hotspot support, multi-monitor support, suspend/resume
    support
    - mgag200: hw cursor support, g200 mode limiting
    - shmobile: prime support
    - tegra: fixes mostly

    I've been banging on this quite a lot due to the size of it, and it
    seems to okay on everything I've tested it on."

    * 'drm-next' of git://people.freedesktop.org/~airlied/linux: (811 commits)
    drm/radeon/dpm: implement vblank_too_short callback for si
    drm/radeon/dpm: implement vblank_too_short callback for cayman
    drm/radeon/dpm: implement vblank_too_short callback for btc
    drm/radeon/dpm: implement vblank_too_short callback for evergreen
    drm/radeon/dpm: implement vblank_too_short callback for 7xx
    drm/radeon/dpm: add checks against vblank time
    drm/radeon/dpm: add helper to calculate vblank time
    drm/radeon: remove stray line in old pm code
    drm/radeon/dpm: fix display_gap programming on rv7xx
    drm/nvc0/gr: fix gpc firmware regression
    drm/nouveau: fix minor thinko causing bo moves to not be async on kepler
    drm/radeon/dpm: implement force performance level for TN
    drm/radeon/dpm: implement force performance level for ON/LN
    drm/radeon/dpm: implement force performance level for SI
    drm/radeon/dpm: implement force performance level for cayman
    drm/radeon/dpm: implement force performance levels for 7xx/eg/btc
    drm/radeon/dpm: add infrastructure to force performance levels
    drm/radeon: fix surface setup on r1xx
    drm/radeon: add support for 3d perf states on older asics
    drm/radeon: set default clocks for SI when DPM is disabled
    ...

    Linus Torvalds
     

31 May, 2013

1 commit

  • 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: Daniel Vetter
    Signed-off-by: Andy Lutomirski
    Signed-off-by: Dave Airlie

    Andy Lutomirski
     

28 May, 2013

1 commit


31 Mar, 2012

1 commit

  • Usage of /etc/modprobe.conf file was deprecated by module-init-tools and
    is no longer parsed by new kmod tool. References to this file are
    replaced in Documentation, comments and Kconfig according to the
    context.

    There are also some references to the old /etc/modules.conf from 2.4
    kernels that are being removed.

    Signed-off-by: Lucas De Marchi
    Acked-by: Takashi Iwai
    Acked-by: Mauro Carvalho Chehab
    Signed-off-by: Randy Dunlap
    Signed-off-by: Linus Torvalds

    Lucas De Marchi
     

07 Mar, 2012

1 commit


20 Dec, 2011

1 commit


24 Aug, 2011

3 commits

  • Signed-off-by: Bernie Thompson
    Signed-off-by: Florian Tobias Schandinat

    Bernie Thompson
     
  • Enables page fault based detection of mmap writes to the framebuffer,
    which allows standard fbdev apps (like the generic fbdev xorg driver)
    to work on DisplayLink devices.

    Not all bugs are shaken out of the fb_defio path of udlfb, but it's
    tantalizingly close, so this seems a good time to enable by default.

    Alternatively, option can be disabled when running with an xorg driver
    that can more directly communicate damaged regions of the framebuffer
    via IOCTL. This is a simpler, higher perf option, when available.

    Signed-off-by: Bernie Thompson
    Signed-off-by: Florian Tobias Schandinat

    Bernie Thompson
     
  • By default, udlfb allocates a 2nd buffer to shadow what's across
    the bus on the USB device. It can operate without this shadow,
    but then it cannot tell which pixels have changed, and must send all.

    Saves host memory, but worsens the USB 2.0 bus bottleneck.

    This option allows users in very low memory situations (e.g.
    bifferboard) to optionally turn off this shadow framebuffer.

    Signed-off-by: Stuart Hopkins
    Signed-off-by: Bernie Thompson
    Signed-off-by: Florian Tobias Schandinat

    Stuart Hopkins
     

25 Jul, 2011

1 commit

  • 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: Rolf Eike Beer
    Signed-off-by: Dave Airlie

    Rolf Eike Beer
     

31 Mar, 2011

1 commit


22 Mar, 2011

1 commit

  • - add commandline options:
    sm501fb.mode:
    Specify resolution as "x[-][@]"
    sm501fb.bpp:
    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: Heiko Schocher
    cc: linux-fbdev@vger.kernel.org
    cc: devicetree-discuss@ozlabs.org
    cc: Ben Dooks
    cc: Vincent Sanders
    cc: Samuel Ortiz
    cc: linux-kernel@vger.kernel.org
    cc: Randy Dunlap
    cc: Paul Mundt
    Signed-off-by: Paul Mundt

    Heiko Schocher
     

06 Jan, 2011

1 commit


18 Nov, 2010

1 commit


16 Nov, 2010

1 commit

  • udlfb has undergone a fair bit of cleanup recently and is effectively at
    the point where it can be liberated from staging purgatory and promoted
    to a real driver.

    The outstanding cleanups are all minor, with some of them dependent on
    drivers/video headers, so these will be done incrementally from udlfb's
    new home.

    Requested-by: Bernie Thompson
    Signed-off-by: Paul Mundt

    Paul Mundt
     

28 Oct, 2010

1 commit

  • * 'viafb-next' of git://github.com/schandinat/linux-2.6: (29 commits)
    viafb: add initial VX900 support
    viafb: fix hardware acceleration for suspend & resume
    viafb: make suspend and resume work (on all machines?)
    viafb: restore display on resume
    Minimal support for viafb suspend/resume
    viafb: use proper register for colour when doing fill ops
    viafb: add documentation for proc interface
    viafb: rename output devices
    viafb: add a mapping of supported output devices
    viafb: set sync polarity for all output devices
    viafb: add function to change sync polarity per device
    viafb: reduce I2C timeout and delay
    viafb: enable I2C for CRT
    viafb: fix i2c_transfer error handling
    viafb: vt1636 cleanup
    viafb: introduce per output device power management
    viafb: limit LCD code impact
    viafb: add interface for output device configuration
    viafb: merge the remaining output path with enable functions
    viafb: use new device routing
    ...

    Linus Torvalds
     

24 Sep, 2010

1 commit


04 Aug, 2010

1 commit

  • 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: Justin P. Mattock
    Signed-off-by: Thomas Weber
    Signed-off-by: Mike Frysinger
    Cc: Paulo Marques
    Cc: Randy Dunlap
    Cc: Michael Neuling
    Signed-off-by: Jiri Kosina

    Justin P. Mattock
     

07 Apr, 2010

1 commit


16 Dec, 2009

1 commit

  • We now support the VX855, and the VX800 is no longer unaccellerated.
    viafb_video_dev was removed as it was useless.

    Signed-off-by: Harald Welte
    Signed-off-by: Florian Tobias Schandinat
    Cc: Joseph Chan
    Cc: Scott Fang
    Cc: Krzysztof Helt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Harald Welte
     

01 Dec, 2009

1 commit


23 Sep, 2009

2 commits

  • 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: Jean Delvare
    Acked-by: Petr Vandrovec
    Cc: Krzysztof Helt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jean Delvare
     
  • EP93xx video driver plus documentation.

    Signed-off-by: Ryan Mallon
    Acked-by: H Hartley Sweeten
    Cc: Daniele Venzano
    Cc: Russell King
    Cc: Krzysztof Helt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ryan Mallon
     

17 Jun, 2009

1 commit


13 Jun, 2009

1 commit


07 Apr, 2009

1 commit


01 Apr, 2009

1 commit

  • 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
    cyblafb.

    - 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: Krzysztof Helt
    Cc: "Jani Monoses"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Krzysztof Helt
     

29 Dec, 2008

2 commits

  • 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: Eric Miao
    Cc: Rodolfo Giometti
    Signed-off-by: Eric Miao

    Eric Miao
     
  • The amount of video memory size is decided according to the following
    order:

    1. x x 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: Eric Miao
    Signed-off-by: Eric Miao

    Eric Miao
     

17 Oct, 2008

3 commits

  • Document the change from the old "mode" parameter to the "mode_option"
    parameter.

    Signed-off-by: Mike Pagano
    Cc: Krzysztof Halasa
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Pagano
     
  • Add support for Intel's 945GME graphics chip to the intelfb driver. I
    have assumed that the 945GME is identical to the already-supported 945GM
    apart from its PCI IDs; this is based on a quick look at the X driver for
    these chips which seems to treat them identically.

    The 945GME is used in the ASUS Eee 901, and I coded this in the hope that
    I'd be able to use it to get a console at the native 1024x600 resolution
    which is not known to the BIOS. I realised too late that the intelfb
    driver does not support mode changing on laptops, so it won't be any
    use for me.

    Signed-off-by: Phil Endecott
    Acked-by: Krzysztof Helt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Phil Endecott
     
  • Correct via_fb_ to viafb_ and remove the Kconfig part in viafb.txt.

    viafb.modes: supported mode table
    viafb.txt: documentation of viafb driver

    Signed-off-by: Joseph Chan
    Cc: Krzysztof Helt
    Cc: Geert Uytterhoeven
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Joseph Chan
     

25 Jul, 2008

2 commits