| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 10 The author wishes to express his appreciation and thanks to:
12 improvements. Thanks to IBM for allowing me time and test resources to pursue
13 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
16 side of the original CIFS Unix extensions and reviewing and implementing
21 Newbigin and others for their work on the Linux smbfs module. Thanks to
23 Workgroup for their work specifying this highly complex protocol and finally
24 thanks to the Samba team for their technical advice and encouragement.
39 - Vince Negri and Dave Stahl (for finding an important caching bug)
44 - Shaggy (Dave Kleikamp) for innumerable small fs suggestions and some good cleanup
45 - Gunter Kukkukk (testing and suggestions for support of old servers)
[all …]
|
| D | todo.rst | 12 is a partial list of the known problems and missing features:
14 a) SMB3 (and SMB3.1.1) missing optional features:
18 - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
21 b) improved sparse file support (fiemap and SEEK_HOLE are implemented
31 open/query/close and open/setinfo/close) to reduce the number of
32 roundtrips to the server and improve performance. Various cases
36 handle caching leases) and better using reference counters on file
39 f) Finish inotify support so kde and gnome file list windows
43 g) Add GUI tool to configure /proc/fs/cifs settings and for display of
46 h) implement support for security and trusted categories of xattrs
[all …]
|
| /Documentation/timers/ |
| D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision
10 features into the existing timer framework, and after testing various
14 to solve this'), and spent a considerable effort trying to integrate
18 - the forced handling of low-resolution and high-resolution timers in
19 the same way leads to a lot of compromises, macro magic and #ifdef
20 mess. The timers.c code is very "tightly coded" around jiffies and
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
25 code is very good and tight code, there's zero problems with it in its
45 error conditions in various I/O paths, such as networking and block
[all …]
|
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes
6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
15 design of the Linux time(r) system before hrtimers and other building blocks
18 Note: the paper and the slides are talking about "clock event source", while we
24 - timeofday and clock source management
44 timeofday and clock source management
51 sources, which are registered in the framework and selected on a quality based
52 decision. The low level code provides hardware setup and readout routines and
63 The paper "We Are Not Getting Any Younger: A New Approach to Time and
75 period defined at compile time. The setup and selection of the event device
[all …]
|
| /Documentation/usb/ |
| D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver.
35 and offering suggestions and sharing implementation experiences.
37 Additional thanks to the following companies and people for donations
38 of hardware, support, time and development (this is from the original
44 - 3Com GmbH for donating a ISDN Pro TA and supporting me
45 in technical questions and with test equipment. I'd never
52 Operating System and supports this project with
74 protocol. They've also donated a F-23 digital joystick and a
79 leading manufacturer for active and passive ISDN Controllers
80 and CAPI 2.0-based software. The active design of the AVM B1
[all …]
|
| /Documentation/scsi/ |
| D | FlashPoint.txt | 15 drivers and information will be available on October 15th at
20 development and provided technical support for our host adapters for several
21 years, and are pleased to now make our FlashPoint products available to this
27 SPARC, SGI MIPS, Motorola 68k, Digital Alpha AXP and Motorola PowerPC
29 System, Emacs, and TCP/IP networking. Further information is available at
30 http://www.linux.org and http://www.ssc.com/.
35 and file server environments, are available in narrow, wide, dual channel,
36 and dual channel wide versions. These adapters feature SeqEngine
37 automation technology, which minimizes SCSI command overhead and reduces
43 producer of RAID technology and network management products. The company
[all …]
|
| D | BusLogic.txt | 1 BusLogic MultiMaster and FlashPoint SCSI Driver for Linux
19 BusLogic, Inc. designed and manufactured a variety of high performance SCSI
23 supported by this driver originated under the BusLogic name and so that name is
24 retained in the source code and documentation.
26 This driver supports all present BusLogic MultiMaster Host Adapters, and should
29 costly and rely on the host CPU, rather than including an onboard processor.
31 well and have very low command latency. BusLogic has recently provided me with
32 the FlashPoint Driver Developer's Kit, which comprises documentation and freely
34 is the library of code that runs on the host CPU and performs functions
40 to achieve the full performance that BusLogic SCSI Host Adapters and modern
[all …]
|
| D | LICENSE.qla4xxx | 5 You may modify and redistribute the device driver code under the
17 Everyone is permitted to copy and distribute verbatim copies
23 freedom to share and change it. By contrast, the GNU General Public
24 License is intended to guarantee your freedom to share and change free
27 Foundation's software and to any other program whose authors commit to
34 have the freedom to distribute copies of free software (and charge for
37 in new free programs; and that you know you can do these things.
47 source code. And you must show them these terms so they know their
50 We protect your rights with two steps: (1) copyright the software, and
52 distribute and/or modify the software.
[all …]
|
| D | LICENSE.qla2xxx | 5 You may modify and redistribute the device driver code under the
18 Everyone is permitted to copy and distribute verbatim copies
24 freedom to share and change it. By contrast, the GNU General Public
25 License is intended to guarantee your freedom to share and change free
28 Foundation's software and to any other program whose authors commit to
35 have the freedom to distribute copies of free software (and charge for
38 in new free programs; and that you know you can do these things.
48 source code. And you must show them these terms so they know their
51 We protect your rights with two steps: (1) copyright the software, and
53 distribute and/or modify the software.
[all …]
|
| D | ufs.txt | 25 embedded and removable flash memory based storage in mobile
26 devices such as smart phones and tablet computers. The specification
29 physical layer and MIPI Unipro as the link layer.
33 For UFS version 1.0 and 1.1 the target performance is as follows,
39 * High random IOPs and low latency
53 Task Manager and Device manager. The UFS interface is designed to be
55 protocol for versions 1.0 and 1.1 of UFS protocol layer.
56 UFS supports subset of SCSI commands defined by SPC-4 and SBC-3.
60 * Device manager: It handles device level operations and device
62 device power management operations and commands to Interconnect
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | v4l2.rst | 1 .. Permission is granted to copy, distribute and/or modify this
5 .. and no Back-Cover Texts. A copy of the license is included at
46 Revision and Copyright
57 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
61 - Original author of the V4L2 API and documentation.
69 - Original author of the V4L2 API and documentation.
81 - Designed and documented the multi-planar API.
89 - Introduce HSV formats and other minor changes.
93 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
101 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
[all …]
|
| D | hist-v4l2.rst | 1 .. Permission is granted to copy, distribute and/or modify this
5 .. and no Back-Cover Texts. A copy of the license is included at
18 and began to work on documentation, example drivers and applications.
21 another four years and two stable kernel releases until the new API was
35 meaningless ``O_TRUNC`` :ref:`open() <func-open>` flag, and the
36 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set
39 identifiers are now ordinals instead of flags, and the
40 ``video_std_construct()`` helper function takes id and
47 struct ``video_standard`` and the color subcarrier fields were
60 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
[all …]
|
| D | dev-overlay.rst | 1 .. Permission is granted to copy, distribute and/or modify this
5 .. and no Back-Cover Texts. A copy of the license is included at
21 This can be considerable more efficient than capturing images and
35 The driver may support simultaneous overlay and capturing using the
36 read/write and streaming I/O methods. If so, operation at the nominal
39 overlay and the other for capture if the capture parameters permit this.
41 Applications should use different file descriptors for capturing and
43 capturing and overlay. Optionally these drivers may also permit
44 capturing and overlay with a single file descriptor for compatibility
45 with V4L and earlier versions of V4L2. [#f1]_
[all …]
|
| /Documentation/fb/ |
| D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame
16 behaviours differ in subtle (and not so subtle) ways. This document describes
24 Device and driver capabilities are reported in the fixed screen information
34 expect from the device and driver.
43 2. Types and visuals
50 Formats are described by frame buffer types and visuals. Some visuals require
52 bits_per_pixel, grayscale, red, green, blue and transp fields.
54 Visuals describe how color information is encoded and assembled to create
56 types and visuals are supported.
64 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 8 open-source community is unique and the Linux kernel is no exception.
11 to be static over time, and will adjust it as needed.
14 to "traditional" ways of developing software. Your contributions and
16 critique and criticism. The review will almost always require
21 system kernel ever, and we do not want to do anything to cause the
22 quality of submission and eventual result to ever decrease.
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
35 The Code of Conduct mentions rights and responsibilities for
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
[all …]
|
| D | code-of-conduct.rst | 9 In the interest of fostering an open and welcoming environment, we as
10 contributors and maintainers pledge to making participation in our project and
12 size, disability, ethnicity, sex characteristics, gender identity and
14 personal appearance, race, religion, or sexual identity and orientation.
22 * Using welcoming and inclusive language
23 * Being respectful of differing viewpoints and experiences
31 * The use of sexualized language or imagery and unwelcome sexual attention or
33 * Trolling, insulting/derogatory comments, and personal or political attacks
45 and are expected to take appropriate and fair corrective action in response to
48 Maintainers have the right and responsibility to remove, edit, or reject
[all …]
|
| /Documentation/core-api/ |
| D | workqueue.rst | 14 is needed and the workqueue (wq) API is the most commonly used
20 queue is called workqueue and the thread is called worker.
32 worker thread per CPU and a single threaded (ST) wq had one worker
35 wq users over the years and with the number of CPU cores continuously
40 provided was unsatisfactory. The limitation was common to both ST and
47 The tension between the provided level of concurrency and resource
49 choosing to use ST wq for polling PIOs and accepting an unnecessary
64 * Automatically regulate worker pool and level of concurrency so that
77 item pointing to that function and queue that work item on a
86 subsystems and drivers queue work items on and the backend mechanism
[all …]
|
| /Documentation/x86/ |
| D | intel_txt.rst | 15 - Measurement and verification of launched environment
17 Intel TXT is part of the vPro(TM) brand and is also available some
19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
21 PM45, and GS45 Express chipsets.
47 uses Intel TXT to perform a measured and verified launch of an OS
55 w/ TXT support since v3.2), and now Linux kernels.
61 While there are many products and technologies that attempt to
64 Measurement Architecture (IMA) and Linux Integrity Module interface
69 starting at system reset and requires measurement of all code
[all …]
|
| /Documentation/vm/ |
| D | frontswap.rst | 11 (Note, frontswap -- and :ref:`cleancache` (merged at 3.0) -- are the "frontends"
12 and the only necessary changes to the core kernel for transcendent memory;
15 for a detailed overview of frontswap and related kernel parts)
25 kernel and is of unknown and possibly time-varying size. The driver
27 frontswap_ops funcs appropriately and the functions it provides must
32 copy the page to transcendent memory and associate it with the type and
36 from transcendent memory and an "invalidate_area" will remove ALL pages
37 associated with the swap type (e.g., like swapoff) and notify the "device"
43 success, the data has been successfully saved to transcendent memory and
44 a disk write and, if the data is later read back, a disk read are avoided.
[all …]
|
| D | cleancache.rst | 19 that is not directly accessible or addressable by the kernel and is
20 of unknown and possibly time-varying size.
25 and a disk access is avoided.
28 in Xen (using hypervisor memory) and zcache (using in-kernel compressed
29 memory) and other implementations are in development.
43 by the kernel and so may or may not still be in cleancache at any later time.
45 Cleancache has complete discretion over what pages to preserve and what
46 pages to discard and when.
51 (presumably about-to-be-evicted) page into cleancache and associate it with
52 the pool id, a file key, and a page index into the file. (The combination
[all …]
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 19 which has 0x81 family ID integrated chip and DS2490
22 Notes and limitations.
24 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
33 a write buffer and a read buffer (along with sizes) as arguments.
35 buffer, and strong pullup all in one command, instead of the current
36 1 reset bus, 2 write the match rom command and slave rom id, 3 block
37 write and read data. The write buffer needs to have the match rom
38 command and slave rom id prepended to the front of the requested
40 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 7 pxa2xx, au1x00, iMX, etc) and portable audio codecs. Prior to the ASoC
12 CPU. This is not ideal and leads to code duplication - for example,
17 event). These are quite common events on portable devices and often require
30 The ASoC layer is designed to address these issues and provide the following
34 and machines.
36 * Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
37 interface and codec registers its audio interface capabilities with the
38 core and are subsequently matched and configured when the application
43 internal power blocks depending on the internal codec audio routing and any
46 * Pop and click reduction. Pops and clicks can be reduced by powering the
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | soc-camera.rst | 13 of connecting to a variety of systems and interfaces, typically uses i2c for
14 control and configuration, and a parallel or a serial bus for data.
16 specialised interface, present on many SoCs, e.g. PXA27x and PXA3xx, SuperH,
18 - camera host bus - a connection between a camera host and a camera. Can be
19 parallel or serial, consists of data and control lines, e.g. clock, vertical
20 and horizontal synchronization signals.
26 drivers and camera sensor drivers. Later the soc-camera sensor API has been
35 The subsystem has been designed to support multiple camera host interfaces and
44 omap1_camera.c, pxa_camera.c, sh_mobile_ceu_camera.c, and multiple sensor
84 .add and .remove methods are called when a sensor is attached to or detached
[all …]
|
| /Documentation/networking/device_drivers/qlogic/ |
| D | LICENSE.qlge | 4 You may modify and redistribute the device driver code under the
16 Everyone is permitted to copy and distribute verbatim copies
22 freedom to share and change it. By contrast, the GNU General Public
23 License is intended to guarantee your freedom to share and change free
26 Foundation's software and to any other program whose authors commit to
33 have the freedom to distribute copies of free software (and charge for
36 in new free programs; and that you know you can do these things.
46 source code. And you must show them these terms so they know their
49 We protect your rights with two steps: (1) copyright the software, and
51 distribute and/or modify the software.
[all …]
|
| D | LICENSE.qlcnic | 4 You may modify and redistribute the device driver code under the
16 Everyone is permitted to copy and distribute verbatim copies
22 freedom to share and change it. By contrast, the GNU General Public
23 License is intended to guarantee your freedom to share and change free
26 Foundation's software and to any other program whose authors commit to
33 have the freedom to distribute copies of free software (and charge for
36 in new free programs; and that you know you can do these things.
46 source code. And you must show them these terms so they know their
49 We protect your rights with two steps: (1) copyright the software, and
51 distribute and/or modify the software.
[all …]
|