mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 03:01:39 -04:00
Merge git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial
* git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial: (25 commits) sound: convert "sound" subdirectory to UTF-8 MAINTAINERS: Add cxacru website/mailing list include files: convert "include" subdirectory to UTF-8 general: convert "kernel" subdirectory to UTF-8 documentation: convert the Documentation directory to UTF-8 Convert the toplevel files CREDITS and MAINTAINERS to UTF-8. remove broken URLs from net drivers' output Magic number prefix consistency change to Documentation/magic-number.txt trivial: s/i_sem /i_mutex/ fix file specification in comments drivers/base/platform.c: fix small typo in doc misc doc and kconfig typos Remove obsolete fat_cvf help text Fix occurrences of "the the " Fix minor typoes in kernel/module.c Kconfig: Remove reference to external mqueue library Kconfig: A couple of grammatical fixes in arch/i386/Kconfig Correct comments in genrtc.c to refer to correct /proc file. Fix more "deprecated" spellos. Fix "deprecated" typoes. ... Fix trivial comment conflict in kernel/relay.c.
This commit is contained in:
Linus Torvalds
commit
9a9136e270
302 changed files with 438 additions and 444 deletions
|
|
@ -6,7 +6,7 @@ Description:
|
|||
races, contains a naming policy within the kernel that is
|
||||
against the LSB, and can be replaced by using udev.
|
||||
The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
|
||||
along with the the assorted devfs function calls throughout the
|
||||
along with the assorted devfs function calls throughout the
|
||||
kernel tree.
|
||||
|
||||
Users:
|
||||
|
|
|
|||
|
|
@ -84,6 +84,10 @@ X!Iinclude/linux/kobject.h
|
|||
!Ekernel/rcupdate.c
|
||||
</sect1>
|
||||
|
||||
<sect1><title>Device Resource Management</title>
|
||||
!Edrivers/base/devres.c
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="adt">
|
||||
|
|
|
|||
|
|
@ -480,8 +480,8 @@ The PCI stack provides 3 possible levels of MSI disabling:
|
|||
|
||||
6.1. Disabling MSI on a single device
|
||||
|
||||
Under some circumstances, it might be required to disable MSI on a
|
||||
single device, It may be achived by either not calling pci_enable_msi()
|
||||
Under some circumstances it might be required to disable MSI on a
|
||||
single device. This may be achieved by either not calling pci_enable_msi()
|
||||
or all, or setting the pci_dev->no_msi flag before (most of the time
|
||||
in a quirk).
|
||||
|
||||
|
|
@ -492,7 +492,7 @@ being able to route MSI between busses. In this case, MSI have to be
|
|||
disabled on all devices behind this bridge. It is achieves by setting
|
||||
the PCI_BUS_FLAGS_NO_MSI flag in the pci_bus->bus_flags of the bridge
|
||||
subordinate bus. There is no need to set the same flag on bridges that
|
||||
are below the broken brigde. When pci_enable_msi() is called to enable
|
||||
are below the broken bridge. When pci_enable_msi() is called to enable
|
||||
MSI on a device, pci_msi_supported() takes care of checking the NO_MSI
|
||||
flag in all parent busses of the device.
|
||||
|
||||
|
|
|
|||
|
|
@ -149,7 +149,7 @@ So, what's changed?
|
|||
|
||||
3. set_GPIO_IRQ_edge() is obsolete, and should be replaced by set_irq_type.
|
||||
|
||||
4. Direct access to SA1111 INTPOL is depreciated. Use set_irq_type instead.
|
||||
4. Direct access to SA1111 INTPOL is deprecated. Use set_irq_type instead.
|
||||
|
||||
5. A handler is expected to perform any necessary acknowledgement of the
|
||||
parent IRQ via the correct chip specific function. For instance, if
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ Support
|
|||
|
||||
http://handhelds.org/moin/moin.cgi/HpIpaqH1940
|
||||
|
||||
Herbert Pötzl pages:
|
||||
Herbert Pötzl pages:
|
||||
|
||||
http://vserver.13thfloor.at/H1940/
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ Maintainers
|
|||
-----------
|
||||
|
||||
This project is being maintained and developed by a variety
|
||||
of people, including Ben Dooks, Arnaud Patard, and Herbert Pötzl.
|
||||
of people, including Ben Dooks, Arnaud Patard, and Herbert Pötzl.
|
||||
|
||||
Thanks to the many others who have also provided support.
|
||||
|
||||
|
|
|
|||
|
|
@ -78,9 +78,9 @@ Select (17)------------------------------(16) Data / Instruction
|
|||
Ground (18)---[GND] [+5v]---(19) LED +
|
||||
Ground (19)---[GND]
|
||||
Ground (20)---[GND] E A Values:
|
||||
Ground (21)---[GND] [GND]---[P1]---(18) Vee · R = Resistor = 22 ohm
|
||||
Ground (22)---[GND] | · P1 = Preset = 10 Kohm
|
||||
Ground (23)---[GND] ---- S ------( 3) V0 · P2 = Preset = 1 Kohm
|
||||
Ground (21)---[GND] [GND]---[P1]---(18) Vee - R = Resistor = 22 ohm
|
||||
Ground (22)---[GND] | - P1 = Preset = 10 Kohm
|
||||
Ground (23)---[GND] ---- S ------( 3) V0 - P2 = Preset = 1 Kohm
|
||||
Ground (24)---[GND] | |
|
||||
Ground (25)---[GND] [GND]---[P2]---[R]---(20) LED -
|
||||
|
||||
|
|
|
|||
|
|
@ -113,4 +113,4 @@ cause unexpected behaviour and can be a security hazard.
|
|||
There is a web page about binfmt_misc at
|
||||
http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html
|
||||
|
||||
Richard Günther <[email protected]>
|
||||
Richard Günther <[email protected]>
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@ Intro
|
|||
-----
|
||||
|
||||
With the introduction of cfq v3 (aka cfq-ts or time sliced cfq), basic io
|
||||
priorities is supported for reads on files. This enables users to io nice
|
||||
processes or process groups, similar to what has been possible to cpu
|
||||
scheduling for ages. This document mainly details the current possibilites
|
||||
with cfq, other io schedulers do not support io priorities so far.
|
||||
priorities are supported for reads on files. This enables users to io nice
|
||||
processes or process groups, similar to what has been possible with cpu
|
||||
scheduling for ages. This document mainly details the current possibilities
|
||||
with cfq; other io schedulers do not support io priorities thus far.
|
||||
|
||||
Scheduling classes
|
||||
------------------
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Contents
|
|||
|
||||
1. Introduction
|
||||
|
||||
cpufreq-stats is a driver that provices CPU frequency statistics for each CPU.
|
||||
cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
|
||||
These statistics are provided in /sysfs as a bunch of read_only interfaces. This
|
||||
interface (when configured) will appear in a separate directory under cpufreq
|
||||
in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
|
||||
|
|
|
|||
|
|
@ -177,7 +177,7 @@ Portions of this API were derived from the following projects:
|
|||
and;
|
||||
|
||||
Nettle (http://www.lysator.liu.se/~nisse/nettle/)
|
||||
Niels Möller
|
||||
Niels Möller
|
||||
|
||||
Original developers of the crypto algorithms:
|
||||
|
||||
|
|
@ -200,8 +200,8 @@ SHA1 algorithm contributors:
|
|||
|
||||
DES algorithm contributors:
|
||||
Raimar Falke
|
||||
Gisle Sælensminde
|
||||
Niels Möller
|
||||
Gisle Sælensminde
|
||||
Niels Möller
|
||||
|
||||
Blowfish algorithm contributors:
|
||||
Herbert Valerio Riedel
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ host bridges to peripheral buses, and most controllers integrated
|
|||
into system-on-chip platforms. What they usually have in common
|
||||
is direct addressing from a CPU bus. Rarely, a platform_device will
|
||||
be connected through a segment of some other kind of bus; but its
|
||||
registers will still be directly addressible.
|
||||
registers will still be directly addressable.
|
||||
|
||||
Platform devices are given a name, used in driver binding, and a
|
||||
list of resources such as addresses and IRQs.
|
||||
|
|
@ -125,7 +125,7 @@ three different ways to find such a match:
|
|||
usually register later during booting, or by module loading.
|
||||
|
||||
- Registering a driver using platform_driver_probe() works just like
|
||||
using platform_driver_register(), except that the the driver won't
|
||||
using platform_driver_register(), except that the driver won't
|
||||
be probed later if another device registers. (Which is OK, since
|
||||
this interface is only for use with non-hotpluggable devices.)
|
||||
|
||||
|
|
|
|||
|
|
@ -228,5 +228,5 @@ Patches, comments and suggestions are very very welcome.
|
|||
|
||||
Ulf Hermenau for helping me out with traditional chinese.
|
||||
|
||||
André Smoktun and Christian Frömmel for supporting me with
|
||||
André Smoktun and Christian Frömmel for supporting me with
|
||||
hardware and listening to my problems very patiently.
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ Michael Dreher <[email protected]>
|
|||
Andreas 'randy' Weinberger
|
||||
for the support of the Fujitsu-Siemens Activy budget DVB-S
|
||||
|
||||
Kenneth Aafløy <[email protected]>
|
||||
Kenneth Aafløy <[email protected]>
|
||||
for adding support for Typhoon DVB-S budget card
|
||||
|
||||
Ernst Peinlich <[email protected]>
|
||||
|
|
|
|||
|
|
@ -54,8 +54,8 @@ Accepted options:
|
|||
|
||||
noaccel - do not use acceleration engine. It is default.
|
||||
accel - use acceleration engine. Not finished.
|
||||
vmode:x - chooses PowerMacintosh video mode <x>. Depreciated.
|
||||
cmode:x - chooses PowerMacintosh colour mode <x>. Depreciated.
|
||||
vmode:x - chooses PowerMacintosh video mode <x>. Deprecated.
|
||||
cmode:x - chooses PowerMacintosh colour mode <x>. Deprecated.
|
||||
<XxX@X> - selects startup videomode. See modedb.txt for detailed
|
||||
explanation. Default is 640x480x8bpp.
|
||||
|
||||
|
|
|
|||
|
|
@ -215,11 +215,11 @@ vertical retrace time is the sum of the upper margin, the lower margin and the
|
|||
vsync length.
|
||||
|
||||
+----------+---------------------------------------------+----------+-------+
|
||||
| | ^ | | |
|
||||
| | ↑ | | |
|
||||
| | |upper_margin | | |
|
||||
| | ･ | | |
|
||||
| | ↓ | | |
|
||||
+----------###############################################----------+-------+
|
||||
| # ^ # | |
|
||||
| # ↑ # | |
|
||||
| # | # | |
|
||||
| # | # | |
|
||||
| # | # | |
|
||||
|
|
@ -238,15 +238,15 @@ vsync length.
|
|||
| # | # | |
|
||||
| # | # | |
|
||||
| # | # | |
|
||||
| # ･ # | |
|
||||
| # ↓ # | |
|
||||
+----------###############################################----------+-------+
|
||||
| | ^ | | |
|
||||
| | ↑ | | |
|
||||
| | |lower_margin | | |
|
||||
| | ･ | | |
|
||||
| | ↓ | | |
|
||||
+----------+---------------------------------------------+----------+-------+
|
||||
| | ^ | | |
|
||||
| | ↑ | | |
|
||||
| | |vsync_len | | |
|
||||
| | ･ | | |
|
||||
| | ↓ | | |
|
||||
+----------+---------------------------------------------+----------+-------+
|
||||
|
||||
The frame buffer device expects all horizontal timings in number of dotclocks
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ How to use it?
|
|||
==============
|
||||
|
||||
Imacfb does not have any kind of autodetection of your machine.
|
||||
You have to add the fillowing kernel parameters in your elilo.conf:
|
||||
You have to add the following kernel parameters in your elilo.conf:
|
||||
Macbook :
|
||||
video=imacfb:macbook
|
||||
MacMini :
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
Introduction
|
||||
|
||||
This is a frame buffer device driver for 3dfx' Voodoo Graphics
|
||||
(aka voodoo 1, aka sst1) and Voodoo² (aka Voodoo 2, aka CVG) based
|
||||
(aka voodoo 1, aka sst1) and Voodoo² (aka Voodoo 2, aka CVG) based
|
||||
video boards. It's highly experimental code, but is guaranteed to work
|
||||
on my computer, with my "Maxi Gamer 3D" and "Maxi Gamer 3d²" boards,
|
||||
on my computer, with my "Maxi Gamer 3D" and "Maxi Gamer 3d²" boards,
|
||||
and with me "between chair and keyboard". Some people tested other
|
||||
combinations and it seems that it works.
|
||||
The main page is located at <http://sstfb.sourceforge.net>, and if
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ ata *);
|
|||
|
||||
locking rules:
|
||||
all may block, none have BKL
|
||||
i_sem(inode)
|
||||
i_mutex(inode)
|
||||
lookup: yes
|
||||
create: yes
|
||||
link: yes (both)
|
||||
|
|
@ -74,7 +74,7 @@ setxattr: yes
|
|||
getxattr: no
|
||||
listxattr: no
|
||||
removexattr: yes
|
||||
Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_sem on
|
||||
Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_mutex on
|
||||
victim.
|
||||
cross-directory ->rename() has (per-superblock) ->s_vfs_rename_sem.
|
||||
->truncate() is never called directly - it's a callback, not a
|
||||
|
|
@ -461,7 +461,7 @@ doesn't take the BKL.
|
|||
->read on directories probably must go away - we should just enforce -EISDIR
|
||||
in sys_read() and friends.
|
||||
|
||||
->fsync() has i_sem on inode.
|
||||
->fsync() has i_mutex on inode.
|
||||
|
||||
--------------------------- dquot_operations -------------------------------
|
||||
prototypes:
|
||||
|
|
|
|||
|
|
@ -290,7 +290,7 @@ History
|
|||
2.07 More fixes for Warp Server. Now it really works
|
||||
2.08 Creating new files is not so slow on large disks
|
||||
An attempt to sync deleted file does not generate filesystem error
|
||||
2.09 Fixed error on extremly fragmented files
|
||||
2.09 Fixed error on extremely fragmented files
|
||||
|
||||
|
||||
vim: set textwidth=80:
|
||||
|
|
|
|||
|
|
@ -349,7 +349,7 @@ end of the line.
|
|||
Note the "Should sync?" parameter "nosync" means that the two mirrors are
|
||||
already in sync which will be the case on a clean shutdown of Windows. If the
|
||||
mirrors are not clean, you can specify the "sync" option instead of "nosync"
|
||||
and the Device-Mapper driver will then copy the entirey of the "Source Device"
|
||||
and the Device-Mapper driver will then copy the entirety of the "Source Device"
|
||||
to the "Target Device" or if you specified multipled target devices to all of
|
||||
them.
|
||||
|
||||
|
|
|
|||
|
|
@ -229,7 +229,7 @@ Table 1-3: Kernel info in /proc
|
|||
mounts Mounted filesystems
|
||||
net Networking info (see text)
|
||||
partitions Table of partitions known to the system
|
||||
pci Depreciated info of PCI bus (new way -> /proc/bus/pci/,
|
||||
pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
|
||||
decoupled by lspci (2.4)
|
||||
rtc Real time clock
|
||||
scsi SCSI info (see text)
|
||||
|
|
|
|||
|
|
@ -351,7 +351,7 @@ If the current buffer is full, i.e. all sub-buffers remain unconsumed,
|
|||
the callback returns 0 to indicate that the buffer switch should not
|
||||
occur yet, i.e. until the consumer has had a chance to read the
|
||||
current set of ready sub-buffers. For the relay_buf_full() function
|
||||
to make sense, the consumer is reponsible for notifying the relay
|
||||
to make sense, the consumer is responsible for notifying the relay
|
||||
interface when sub-buffers have been consumed via
|
||||
relay_subbufs_consumed(). Any subsequent attempts to write into the
|
||||
buffer will again invoke the subbuf_start() callback with the same
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ completely. With execute-in-place, read&write type operations are performed
|
|||
directly from/to the memory backed storage device. For file mappings, the
|
||||
storage device itself is mapped directly into userspace.
|
||||
|
||||
This implementation was initialy written for shared memory segments between
|
||||
This implementation was initially written for shared memory segments between
|
||||
different virtual machines on s390 hardware to allow multiple machines to
|
||||
share the same binaries and libraries.
|
||||
|
||||
|
|
|
|||
|
|
@ -126,5 +126,5 @@ GDB stub and the debugger:
|
|||
|
||||
Furthermore, the GDB stub will intercept a number of exceptions automatically
|
||||
if they are caused by kernel execution. It will also intercept BUG() macro
|
||||
invokation.
|
||||
invocation.
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ temperature sensor inputs. Both the PWM output and the DAC output can be
|
|||
used to control fan speed. Usually only one of these two outputs will be
|
||||
used. Write the minimum PWM or DAC value to the appropriate control
|
||||
register. Then set the low temperature limit in the tmin values for each
|
||||
temperature sensor. The range of control is fixed at 20 °C, and the
|
||||
temperature sensor. The range of control is fixed at 20 °C, and the
|
||||
largest difference between current and tmin of the temperature sensors sets
|
||||
the control output. See the datasheet for several example circuits for
|
||||
controlling fan speed with the PWM and DAC outputs. The fan speed sensors
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Supported chips:
|
|||
|
||||
Authors:
|
||||
Frodo Looijaard <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>
|
||||
Kyösti Mälkki <[email protected]>
|
||||
Hong-Gunn Chew <[email protected]>
|
||||
Jean Delvare <[email protected]>
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ Unconfirmed motherboards:
|
|||
The LM82 is confirmed to have been found on most AMD Geode reference
|
||||
designs and test platforms.
|
||||
|
||||
The driver has been successfully tested by Magnus Forsström, who I'd
|
||||
The driver has been successfully tested by Magnus Forsström, who I'd
|
||||
like to thank here. More testers will be of course welcome.
|
||||
|
||||
The fact that the LM83 is only scarcely used can be easily explained.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Supported chips:
|
|||
Datasheet: Publicly available at the Silicon Integrated Systems Corp. site.
|
||||
|
||||
Authors:
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Mark D. Studebaker <[email protected]>,
|
||||
Aurelien Jarno <[email protected]> 2.6 port
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Supported chips:
|
|||
Datasheet: On request through web form (http://www.via.com.tw/en/support/datasheets/)
|
||||
|
||||
Authors:
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Mark D. Studebaker <[email protected]>
|
||||
Bob Dougherty <[email protected]>
|
||||
(Some conversion-factor data were contributed by
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ Known problems:
|
|||
by CR[0x49h].
|
||||
- The function of vid and vrm has not been finished, because I'm NOT
|
||||
very familiar with them. Adding support is welcome.
|
||||
- The function of chassis open detection needs more tests.
|
||||
- The function of chassis open detection needs more tests.
|
||||
- If you have ASUS server board and chip was not found: Then you will
|
||||
need to upgrade to latest (or beta) BIOS. If it does not help please
|
||||
contact us.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Supported adapters:
|
|||
Authors:
|
||||
Frodo Looijaard <[email protected]>,
|
||||
Philip Edelbrock <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Ralph Metzler <[email protected]>,
|
||||
Mark D. Studebaker <[email protected]>
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ Mark D. Studebaker <[email protected]>
|
|||
- design hints and bug fixes
|
||||
Alexander Maylsh <[email protected]>
|
||||
- ditto, plus an important datasheet... almost the one I really wanted
|
||||
Hans-Günter Lütke Uphues <[email protected]>
|
||||
Hans-Günter Lütke Uphues <[email protected]>
|
||||
- patch for SiS735
|
||||
Robert Zwerus <[email protected]>
|
||||
- testing for SiS645DX
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Supported adapters:
|
|||
* VIA Technologies, InC. VT82C586B
|
||||
Datasheet: Publicly available at the VIA website
|
||||
|
||||
Author: Kyösti Mälkki <[email protected]>
|
||||
Author: Kyösti Mälkki <[email protected]>
|
||||
|
||||
Description
|
||||
-----------
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Supported adapters:
|
|||
Datasheet: available on request and under NDA from VIA
|
||||
|
||||
Authors:
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Kyösti Mälkki <[email protected]>,
|
||||
Mark D. Studebaker <[email protected]>,
|
||||
Jean Delvare <[email protected]>
|
||||
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ We have found some I2C devices that needs the following modifications:
|
|||
|
||||
Flags I2C_M_IGNORE_NAK
|
||||
Normally message is interrupted immediately if there is [NA] from the
|
||||
client. Setting this flag treats any [NA] as [A], and all of
|
||||
client. Setting this flag treats any [NA] as [A], and all of
|
||||
message is sent.
|
||||
These messages may still fail to SCL lo->hi timeout.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,13 +30,13 @@ Juha Sievanen, University of Helsinki Finland
|
|||
Bug fixes
|
||||
Core code extensions
|
||||
|
||||
Auvo Häkkinen, University of Helsinki Finland
|
||||
Auvo Häkkinen, University of Helsinki Finland
|
||||
LAN OSM code
|
||||
/Proc interface to LAN class
|
||||
Bug fixes
|
||||
Core code extensions
|
||||
|
||||
Taneli Vähäkangas, University of Helsinki Finland
|
||||
Taneli Vähäkangas, University of Helsinki Finland
|
||||
Fixes to i2o_config
|
||||
|
||||
CREDITS
|
||||
|
|
|
|||
|
|
@ -179,9 +179,9 @@ reporting mode for joystick 1, with both buttons being logically assigned to
|
|||
the mouse. After any joystick command, the ikbd assumes that joysticks are
|
||||
connected to both Joystick0 and Joystick1. Any mouse command (except MOUSE
|
||||
DISABLE) then causes port 0 to again be scanned as if it were a mouse, and
|
||||
both buttons are logically connected to it. If a mouse diable command is
|
||||
both buttons are logically connected to it. If a mouse disable command is
|
||||
received while port 0 is presumed to be a mouse, the button is logically
|
||||
assigned to Joystick1 ( until the mouse is reenabled by another mouse command).
|
||||
assigned to Joystick1 (until the mouse is reenabled by another mouse command).
|
||||
|
||||
9. ikbd Command Set
|
||||
|
||||
|
|
|
|||
|
|
@ -65,15 +65,15 @@ of buttons, see section 0.3 - Unknown Controllers
|
|||
I've tested this with Stepmania, and it works quite well.
|
||||
|
||||
|
||||
0.3 Unkown Controllers
|
||||
0.3 Unknown Controllers
|
||||
----------------------
|
||||
If you have an unkown xbox controller, it should work just fine with
|
||||
If you have an unknown xbox controller, it should work just fine with
|
||||
the default settings.
|
||||
|
||||
HOWEVER if you have an unknown dance pad not listed below, it will not
|
||||
work UNLESS you set "dpad_to_buttons" to 1 in the module configuration.
|
||||
|
||||
PLEASE if you have an unkown controller, email Dom <[email protected]> with
|
||||
PLEASE, if you have an unknown controller, email Dom <[email protected]> with
|
||||
a dump from /proc/bus/usb and a description of the pad (manufacturer, country,
|
||||
whether it is a dance pad or normal controller) so that we can add your pad
|
||||
to the list of supported devices, ensuring that it will work out of the
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
I want to thank all who contributed to this project and especially to:
|
||||
(in alphabetical order)
|
||||
|
||||
Thomas Bogendörfer ([email protected])
|
||||
Thomas Bogendörfer ([email protected])
|
||||
Tester, lots of bugfixes and hints.
|
||||
|
||||
Alan Cox ([email protected])
|
||||
|
|
@ -11,7 +11,7 @@ Alan Cox ([email protected])
|
|||
Henner Eisen ([email protected])
|
||||
For X.25 implementation.
|
||||
|
||||
Volker Götz ([email protected])
|
||||
Volker Götz ([email protected])
|
||||
For contribution of man-pages, the imontty-tool and a perfect
|
||||
maintaining of the mailing-list at hub-wue.
|
||||
|
||||
|
|
|
|||
|
|
@ -402,7 +402,7 @@ README for the ISDN-subsystem
|
|||
the script tools/tcltk/isdnmon. You can add actions for line-status
|
||||
changes. See the comments at the beginning of the script for how to
|
||||
do that. There are other tty-based tools in the tools-subdirectory
|
||||
contributed by Michael Knigge (imon), Volker Götz (imontty) and
|
||||
contributed by Michael Knigge (imon), Volker Götz (imontty) and
|
||||
Andreas Kool (isdnmon).
|
||||
|
||||
l) For initial testing, you can set the verbose-level to 2 (default: 0).
|
||||
|
|
|
|||
|
|
@ -3,8 +3,8 @@ $Id: README.icn,v 1.7 2000/08/06 09:22:51 armin Exp $
|
|||
You can get the ICN-ISDN-card from:
|
||||
|
||||
Thinking Objects Software GmbH
|
||||
Versbacher Röthe 159
|
||||
97078 Würzburg
|
||||
Versbacher Röthe 159
|
||||
97078 Würzburg
|
||||
Tel: +49 931 2877950
|
||||
Fax: +49 931 2877951
|
||||
|
||||
|
|
|
|||
|
|
@ -390,7 +390,7 @@ the execution bit, then just do
|
|||
|
||||
|
||||
originally by Brian A. Lantz, [email protected]
|
||||
heavily edited for binfmt_misc by Richard Günther
|
||||
heavily edited for binfmt_misc by Richard Günther
|
||||
new scripts by Colin J. Watson <[email protected]>
|
||||
added executable Jar file support by Kurt Huwig <[email protected]>
|
||||
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@
|
|||
|
||||
* Title: "Design and Implementation of the Second Extended
|
||||
Filesystem"
|
||||
Author: Rémy Card, Theodore Ts'o, Stephen Tweedie.
|
||||
Author: Rémy Card, Theodore Ts'o, Stephen Tweedie.
|
||||
URL: http://web.mit.edu/tytso/www/linux/ext2intro.html
|
||||
Keywords: ext2, linux fs history, inode, directory, link, devices,
|
||||
VFS, physical structure, performance, benchmarks, ext2fs library,
|
||||
|
|
|
|||
|
|
@ -204,7 +204,7 @@ always shows a "no IRQ here" on the Buddha, and accesses to
|
|||
the third IDE port are going into data's Nirwana on the
|
||||
Buddha.
|
||||
|
||||
Jens Schönfeld february 19th, 1997
|
||||
Jens Schönfeld february 19th, 1997
|
||||
updated may 27th, 1997
|
||||
eMail: [email protected]
|
||||
|
||||
|
|
|
|||
|
|
@ -129,7 +129,7 @@ SAVEKMSG_MAGIC1 0x53415645 savekmsg arch/*/amiga/config.c
|
|||
GDA_MAGIC 0x58464552 gda include/asm-mips64/sn/gda.h
|
||||
RED_MAGIC1 0x5a2cf071 (any) mm/slab.c
|
||||
STL_PORTMAGIC 0x5a7182c9 stlport include/linux/stallion.h
|
||||
EEPROM_MAGIC_VALUE 0X5ab478d2 lanai_dev drivers/atm/lanai.c
|
||||
EEPROM_MAGIC_VALUE 0x5ab478d2 lanai_dev drivers/atm/lanai.c
|
||||
HDLCDRV_MAGIC 0x5ac6e778 hdlcdrv_state include/linux/hdlcdrv.h
|
||||
EPCA_MAGIC 0x5c6df104 channel include/linux/epca.h
|
||||
PCXX_MAGIC 0x5c6df104 channel drivers/char/pcxx.h
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ The communication layer exists to allow NetLabel configuration and monitoring
|
|||
from user space. The NetLabel communication layer uses a message based
|
||||
protocol built on top of the Generic NETLINK transport mechanism. The exact
|
||||
formatting of these NetLabel messages as well as the Generic NETLINK family
|
||||
names can be found in the the 'net/netlabel/' directory as comments in the
|
||||
names can be found in the 'net/netlabel/' directory as comments in the
|
||||
header files as well as in 'include/net/netlabel.h'.
|
||||
|
||||
* Security Module API
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This is the 6pack-mini-HOWTO, written by
|
||||
|
||||
Andreas Könsgen DG3KQ
|
||||
Andreas Könsgen DG3KQ
|
||||
Internet: [email protected]
|
||||
AMPR-net: [email protected]
|
||||
AX.25: dg3kq@db0ach.#nrw.deu.eu
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ on current cpu. This primitive is called by dev->poll(), when
|
|||
it completes its work. The device cannot be out of poll list at this
|
||||
call, if it is then clearly it is a BUG(). You'll know ;->
|
||||
|
||||
All these above nethods are used below. So keep reading for clarity.
|
||||
All of the above methods are used below, so keep reading for clarity.
|
||||
|
||||
Device driver changes to be made when porting NAPI
|
||||
==================================================
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ You can find the latest version of this document at
|
|||
|
||||
Please send me your comments to
|
||||
|
||||
Ulisses Alonso Camaró <[email protected]>
|
||||
Ulisses Alonso Camaró <[email protected]>
|
||||
|
||||
-------------------------------------------------------------------------------
|
||||
+ Why use PACKET_MMAP
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
|
||||
SliceCOM adapter felhasznaloi dokumentacioja - 0.51 verziohoz
|
||||
|
||||
Bartók István <[email protected]>
|
||||
Bartók István <[email protected]>
|
||||
Utolso modositas: Wed Aug 29 17:26:58 CEST 2001
|
||||
|
||||
-----------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
|
||||
SliceCOM adapter user's documentation - for the 0.51 driver version
|
||||
|
||||
Written by Bartók István <[email protected]>
|
||||
Written by Bartók István <[email protected]>
|
||||
|
||||
English translation: Lakatos György <[email protected]>
|
||||
English translation: Lakatos György <[email protected]>
|
||||
Mon Dec 11 15:28:42 CET 2000
|
||||
|
||||
Last modified: Wed Aug 29 17:25:37 CEST 2001
|
||||
|
|
|
|||
|
|
@ -71,24 +71,24 @@ Below find attached the setting for the SK NET TR 4/16 ISA adapters
|
|||
CHAPTER 1 LOCATION OF DIP-SWITCH
|
||||
==============================================================
|
||||
|
||||
UÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
|
||||
þUÄÄÄÄÄÄ¿ UÄÄÄÄÄ¿ UÄÄÄ¿ þ
|
||||
þAÄÄÄÄÄÄU W1 AÄÄÄÄÄU UÄÄÄÄ¿ þ þ þ
|
||||
þUÄÄÄÄÄÄ¿ þ þ þ þ UÄÄÅ¿
|
||||
þAÄÄÄÄÄÄU UÄÄÄÄÄÄÄÄÄÄÄ¿ AÄÄÄÄU þ þ þ þþ
|
||||
þUÄÄÄÄÄÄ¿ þ þ UÄÄÄ¿ AÄÄÄU AÄÄÅU
|
||||
þAÄÄÄÄÄÄU þ TMS380C26 þ þ þ þ
|
||||
þUÄÄÄÄÄÄ¿ þ þ AÄÄÄU AÄ¿
|
||||
þAÄÄÄÄÄÄU þ þ þ þ
|
||||
þ AÄÄÄÄÄÄÄÄÄÄÄU þ þ
|
||||
þ þ þ
|
||||
þ AÄU
|
||||
þ þ
|
||||
þ þ
|
||||
þ þ
|
||||
þ þ
|
||||
AÄÄÄÄÄÄÄÄÄÄÄÄAÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄAÄÄAÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄAÄÄÄÄÄÄÄÄÄU
|
||||
AÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄU AÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄU
|
||||
UÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
|
||||
þUÄÄÄÄÄÄ¿ UÄÄÄÄÄ¿ UÄÄÄ¿ þ
|
||||
þAÄÄÄÄÄÄU W1 AÄÄÄÄÄU UÄÄÄÄ¿ þ þ þ
|
||||
þUÄÄÄÄÄÄ¿ þ þ þ þ UÄÄÅ¿
|
||||
þAÄÄÄÄÄÄU UÄÄÄÄÄÄÄÄÄÄÄ¿ AÄÄÄÄU þ þ þ þþ
|
||||
þUÄÄÄÄÄÄ¿ þ þ UÄÄÄ¿ AÄÄÄU AÄÄÅU
|
||||
þAÄÄÄÄÄÄU þ TMS380C26 þ þ þ þ
|
||||
þUÄÄÄÄÄÄ¿ þ þ AÄÄÄU AÄ¿
|
||||
þAÄÄÄÄÄÄU þ þ þ þ
|
||||
þ AÄÄÄÄÄÄÄÄÄÄÄU þ þ
|
||||
þ þ þ
|
||||
þ AÄU
|
||||
þ þ
|
||||
þ þ
|
||||
þ þ
|
||||
þ þ
|
||||
AÄÄÄÄÄÄÄÄÄÄÄÄAÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄAÄÄAÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄAÄÄÄÄÄÄÄÄÄU
|
||||
AÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄU AÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄU
|
||||
|
||||
==============================================================
|
||||
CHAPTER 2 DEFAULT SETTINGS
|
||||
|
|
@ -108,9 +108,9 @@ A
|
|||
CHAPTER 3 DIP SWITCH W1 DESCRIPTION
|
||||
==============================================================
|
||||
|
||||
UÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄ¿ ON
|
||||
þ 1 þ 2 þ 3 þ 4 þ 5 þ 6 þ 7 þ 8 þ
|
||||
AÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄU OFF
|
||||
UÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄ¿ ON
|
||||
þ 1 þ 2 þ 3 þ 4 þ 5 þ 6 þ 7 þ 8 þ
|
||||
AÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄAÄÄÄU OFF
|
||||
|AD | BootROM Addr. | I/O |
|
||||
+-+-+-------+-------+-----+-----+
|
||||
| | |
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@
|
|||
3) Disabling the Checksum Computation
|
||||
|
||||
On both sender and receiver, checksumming will always be performed
|
||||
and can not be disabled using SO_NO_CHECK. Thus
|
||||
and cannot be disabled using SO_NO_CHECK. Thus
|
||||
|
||||
setsockopt(sockfd, SOL_SOCKET, SO_NO_CHECK, ... );
|
||||
|
||||
|
|
|
|||
|
|
@ -335,7 +335,7 @@ REVISION HISTORY
|
|||
creating applications using BiSync
|
||||
streaming.
|
||||
|
||||
2.0.5 Aug 04, 1999 CHDLC initializatin bug fix.
|
||||
2.0.5 Aug 04, 1999 CHDLC initialization bug fix.
|
||||
PPP interrupt driven driver:
|
||||
Fix to the PPP line hangup problem.
|
||||
New PPP firmware
|
||||
|
|
@ -372,7 +372,7 @@ REVISION HISTORY
|
|||
o cfgft1 GUI csu/dsu configurator
|
||||
o wancfg GUI configuration file
|
||||
configurator.
|
||||
o Architectual directory changes.
|
||||
o Architectural directory changes.
|
||||
|
||||
beta-2.1.4 Jul 2000 o Dynamic interface configuration:
|
||||
Network interfaces reflect the state
|
||||
|
|
|
|||
|
|
@ -373,7 +373,7 @@ E.g. clearing pending interrupts.
|
|||
|
||||
3.6 Register IRQ handler
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
While calling request_irq() is the the last step described here,
|
||||
While calling request_irq() is the last step described here,
|
||||
this is often just another intermediate step to initialize a device.
|
||||
This step can often be deferred until the device is opened for use.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Reporting (AER) driver and provides information on how to use it, as
|
|||
well as how to enable the drivers of endpoint devices to conform with
|
||||
PCI Express AER driver.
|
||||
|
||||
1.2 Copyright © Intel Corporation 2006.
|
||||
1.2 Copyright © Intel Corporation 2006.
|
||||
|
||||
1.3 What is the PCI Express AER Driver?
|
||||
|
||||
|
|
|
|||
|
|
@ -140,7 +140,7 @@ Plug and Play but it is planned to be in the near future.
|
|||
Requirements for a Linux PnP protocol:
|
||||
1.) the protocol must use EISA IDs
|
||||
2.) the protocol must inform the PnP Layer of a devices current configuration
|
||||
- the ability to set resources is optional but prefered.
|
||||
- the ability to set resources is optional but preferred.
|
||||
|
||||
The following are PnP protocol related functions:
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ before suspend (it is limited to 500 MB by default).
|
|||
|
||||
Article about goals and implementation of Software Suspend for Linux
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Author: G‚ábor Kuti
|
||||
Author: Gábor Kuti
|
||||
Last revised: 2003-10-20 by Pavel Machek
|
||||
|
||||
Idea and goals to achieve
|
||||
|
|
|
|||
|
|
@ -1444,7 +1444,7 @@ platforms are moved over to use the flattened-device-tree model.
|
|||
Basically, it is a bus of devices, that could act more or less
|
||||
as a complete entity (UCC, USB etc ). All of them should be siblings on
|
||||
the "root" qe node, using the common properties from there.
|
||||
The description below applies to the the qe of MPC8360 and
|
||||
The description below applies to the qe of MPC8360 and
|
||||
more nodes and properties would be extended in the future.
|
||||
|
||||
i) Root QE device
|
||||
|
|
@ -1633,7 +1633,7 @@ platforms are moved over to use the flattened-device-tree model.
|
|||
- assignment : function number of the pin according to the Pin Assignment
|
||||
tables in User Manual. Each pin can have up to 4 possible functions in
|
||||
QE and two options for CPM.
|
||||
- has_irq : indicates if the pin is used as source of exteral
|
||||
- has_irq : indicates if the pin is used as source of external
|
||||
interrupts.
|
||||
|
||||
Example:
|
||||
|
|
|
|||
|
|
@ -2209,7 +2209,7 @@ Breakpoint 2 at 0x4d87a4: file top.c, line 2609.
|
|||
#3 0x5167e6 in readline_internal_char () at readline.c:454
|
||||
#4 0x5168ee in readline_internal_charloop () at readline.c:507
|
||||
#5 0x51692c in readline_internal () at readline.c:521
|
||||
#6 0x5164fe in readline (prompt=0x7ffff810 "\177<EFBFBD>ÿ<EFBFBD>øx\177<37>ÿ<EFBFBD>÷<EFBFBD>Ø\177<37>ÿ<EFBFBD>øx<C3B8>À")
|
||||
#6 0x5164fe in readline (prompt=0x7ffff810 "\177ÿøx\177ÿ÷Ø\177ÿøxÀ")
|
||||
at readline.c:349
|
||||
#7 0x4d7a8a in command_line_input (prrompt=0x564420 "(gdb) ", repeat=1,
|
||||
annotation_suffix=0x4d6b44 "prompt") at top.c:2091
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
$Id: README.aha152x,v 1.2 1999/12/25 15:32:30 fischer Exp fischer $
|
||||
Adaptec AHA-1520/1522 SCSI driver for Linux (aha152x)
|
||||
|
||||
Copyright 1993-1999 Jürgen Fischer <[email protected]>
|
||||
Copyright 1993-1999 Jürgen Fischer <[email protected]>
|
||||
TC1550 patches by Luuk van Dijk ([email protected])
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ The following information is available in this file:
|
|||
2. Multi-function Twin Channel Device - Two controllers on one chip.
|
||||
3. Command Channel Secondary DMA Engine - Allows scatter gather list
|
||||
and SCB prefetch.
|
||||
4. 64 Byte SCB Support - Allows disconnected, unttagged request table
|
||||
4. 64 Byte SCB Support - Allows disconnected, untagged request table
|
||||
for all possible target/lun combinations.
|
||||
5. Block Move Instruction Support - Doubles the speed of certain
|
||||
sequencer operations.
|
||||
|
|
|
|||
|
|
@ -356,7 +356,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
|
|||
or enable Tagged Command Queueing (TCQ) on specific devices. As of
|
||||
driver version 5.1.11, TCQ is now either on or off by default
|
||||
according to the setting you choose during the make config process.
|
||||
In order to en/disable TCQ for certian devices at boot time, a user
|
||||
In order to en/disable TCQ for certain devices at boot time, a user
|
||||
may use this boot param. The driver will then parse this message out
|
||||
and en/disable the specific device entries that are present based upon
|
||||
the value given. The param line is parsed in the following manner:
|
||||
|
|
|
|||
|
|
@ -1260,7 +1260,7 @@ then the request of the IRQ obviously will not succeed for all the drivers.
|
|||
15.1 Problem tracking
|
||||
|
||||
Most SCSI problems are due to a non conformant SCSI bus or to buggy
|
||||
devices. If infortunately you have SCSI problems, you can check the
|
||||
devices. If unfortunately you have SCSI problems, you can check the
|
||||
following things:
|
||||
|
||||
- SCSI bus cables
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This file contains brief information about the SCSI tape driver.
|
||||
The driver is currently maintained by Kai Mäkisara (email
|
||||
The driver is currently maintained by Kai Mäkisara (email
|
||||
[email protected])
|
||||
|
||||
Last modified: Mon Mar 7 21:14:44 2005 by kai.makisara
|
||||
|
|
|
|||
|
|
@ -587,7 +587,7 @@ devices, ... may cause a SCSI signal to be wrong when te driver reads it.
|
|||
15.1 Problem tracking
|
||||
|
||||
Most SCSI problems are due to a non conformant SCSI bus or too buggy
|
||||
devices. If infortunately you have SCSI problems, you can check the
|
||||
devices. If unfortunately you have SCSI problems, you can check the
|
||||
following things:
|
||||
|
||||
- SCSI bus cables
|
||||
|
|
|
|||
|
|
@ -426,7 +426,7 @@ Thanks to Linus Torvalds, Alan Cox, the FSF people, the XFree86 team and
|
|||
all the others for the wonderful OS and software.
|
||||
Thanks to C.L. Huang and Philip Giang (Tekram) for the initial driver
|
||||
release and support.
|
||||
Thanks to Doug Ledford, Gérard Roudier for support with SCSI coding.
|
||||
Thanks to Doug Ledford, Gérard Roudier for support with SCSI coding.
|
||||
Thanks to a lot of people (espec. Chiaki Ishikawa, Andreas Haumer, Hubert
|
||||
Tonneau) for intensively testing the driver (and even risking data loss
|
||||
doing this during early revisions).
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Sony Programmable I/O Control Device Driver Readme
|
||||
--------------------------------------------------
|
||||
Copyright (C) 2001-2004 Stelian Pop <[email protected]>
|
||||
Copyright (C) 2001-2002 Alcôve <www.alcove.com>
|
||||
Copyright (C) 2001-2002 Alcôve <www.alcove.com>
|
||||
Copyright (C) 2001 Michael Ashley <[email protected]>
|
||||
Copyright (C) 2001 Junichi Morita <[email protected]>
|
||||
Copyright (C) 2000 Takaya Kinjo <[email protected]>
|
||||
|
|
|
|||
|
|
@ -163,7 +163,7 @@ OR the Default= line COULD be
|
|||
Default=SBPRO
|
||||
|
||||
Reboot to Windows 95 and choose Linux. When booted, use sndconfig to configure
|
||||
the sound modules and voilà - ThinkPad sound with Linux.
|
||||
the sound modules and voilà - ThinkPad sound with Linux.
|
||||
|
||||
Now the gotchas - you can either have CD sound OR Mixers but not both. That's a
|
||||
problem with the SB1.5 (CD sound) or SBPRO (Mixers) settings. No one knows why
|
||||
|
|
|
|||
|
|
@ -221,14 +221,14 @@ Controls the kernel's behaviour when an oops or BUG is encountered.
|
|||
|
||||
0: try to continue operation
|
||||
|
||||
1: panic immediatly. If the `panic' sysctl is also non-zero then the
|
||||
1: panic immediately. If the `panic' sysctl is also non-zero then the
|
||||
machine will be rebooted.
|
||||
|
||||
==============================================================
|
||||
|
||||
pid_max:
|
||||
|
||||
PID allocation wrap value. When the kenrel's next PID value
|
||||
PID allocation wrap value. When the kernel's next PID value
|
||||
reaches this value, it wraps back to a minimum PID value.
|
||||
PIDs of value pid_max or larger are not allocated.
|
||||
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ THANKS file in Inaky's driver):
|
|||
will sell keyboards to some of the 3 million (at least)
|
||||
Linux users.
|
||||
|
||||
- Many thanks to ing büro h doran [http://www.ibhdoran.com]!
|
||||
- Many thanks to ing büro h doran [http://www.ibhdoran.com]!
|
||||
It was almost impossible to get a PC backplate USB connector
|
||||
for the motherboard here at Europe (mine, home-made, was
|
||||
quite lousy :). Now I know where to acquire nice USB stuff!
|
||||
|
|
|
|||
|
|
@ -45,9 +45,9 @@ ConnectTech WhiteHEAT 4 port converter
|
|||
Connect Tech's Support Department at [email protected]
|
||||
|
||||
|
||||
HandSpring Visor, Palm USB, and Clié USB driver
|
||||
HandSpring Visor, Palm USB, and Clié USB driver
|
||||
|
||||
This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
|
||||
This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
|
||||
devices.
|
||||
|
||||
Only when the device tries to connect to the host, will the device show
|
||||
|
|
@ -69,7 +69,7 @@ HandSpring Visor, Palm USB, and Cli
|
|||
the port to use for the HotSync transfer. The "Generic" port can be used
|
||||
for other device communication, such as a PPP link.
|
||||
|
||||
For some Sony Clié devices, /dev/ttyUSB0 must be used to talk to the
|
||||
For some Sony Clié devices, /dev/ttyUSB0 must be used to talk to the
|
||||
device. This is true for all OS version 3.5 devices, and most devices
|
||||
that have had a flash upgrade to a newer version of the OS. See the
|
||||
kernel system log for information on which is the correct port to use.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Background:
|
|||
|
||||
This driver is intended for the "Hauppauge WinTV PVR USB 2.0", which
|
||||
is a USB 2.0 hosted TV Tuner. This driver is a work in progress.
|
||||
Its history started with the reverse-engineering effort by Björn
|
||||
Its history started with the reverse-engineering effort by Björn
|
||||
Danielsson <[email protected]> whose web page can be found here:
|
||||
|
||||
http://pvrusb2.dax.nu/
|
||||
|
|
|
|||
|
|
@ -242,7 +242,7 @@ can generate: PAL , NTSC , SECAM
|
|||
|
||||
Conexant bt866 TV encoder
|
||||
is used in AVS6EYES, and
|
||||
can generate: NTSC/PAL, PALM, PALN
|
||||
can generate: NTSC/PAL, PALM, PALN
|
||||
|
||||
The adv717x, should be able to produce PAL N. But you find nothing PAL N
|
||||
specific in the registers. Seem that you have to reuse a other standard
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Vaio Picturebook Motion Eye Camera Driver Readme
|
||||
------------------------------------------------
|
||||
Copyright (C) 2001-2004 Stelian Pop <[email protected]>
|
||||
Copyright (C) 2001-2002 Alcôve <www.alcove.com>
|
||||
Copyright (C) 2001-2002 Alcôve <www.alcove.com>
|
||||
Copyright (C) 2000 Andrew Tridgell <[email protected]>
|
||||
|
||||
This driver enable the use of video4linux compatible applications with the
|
||||
|
|
|
|||
|
|
@ -195,11 +195,11 @@ MODULE PARAMETERS:
|
|||
NAME: bandingfilter
|
||||
TYPE: integer (Boolean)
|
||||
DEFAULT: 0 (off)
|
||||
DESC: Enables the sensor´s banding filter exposure algorithm. This reduces
|
||||
DESC: Enables the sensor´s banding filter exposure algorithm. This reduces
|
||||
or stabilizes the "banding" caused by some artificial light sources
|
||||
(especially fluorescent). You might have to set lightfreq correctly for
|
||||
this to work right. As an added bonus, this sometimes makes it
|
||||
possible to capture your monitor´s output.
|
||||
possible to capture your monitor´s output.
|
||||
|
||||
NAME: fastset
|
||||
TYPE: integer (Boolean)
|
||||
|
|
|
|||
Loading…
Reference in a new issue