Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit add5b5ee authored by Len Brown's avatar Len Brown
Browse files

Auto-update from upstream

parents 25da0974 0aec63e6

.gitignore

+1 −0
Original line number Diff line number Diff line
@@ -10,6 +10,7 @@ 
*.a

*.s

*.ko

*.so

*.mod.c



#

Documentation/feature-removal-schedule.txt

+0 −9
Original line number Diff line number Diff line
@@ -71,15 +71,6 @@ Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br> 


---------------------------



What:	i2c sysfs name change: in1_ref, vid deprecated in favour of cpu0_vid

When:	November 2005

Files:	drivers/i2c/chips/adm1025.c, drivers/i2c/chips/adm1026.c

Why:	Match the other drivers' name for the same function, duplicate names

	will be available until removal of old names.

Who:	Grant Coady <gcoady@gmail.com>



---------------------------



What:	remove EXPORT_SYMBOL(panic_timeout)

When:	April 2006

Files:	kernel/panic.c

Documentation/hwmon/w83627hf

+11 −8
Original line number Diff line number Diff line
@@ -54,13 +54,16 @@ If you really want i2c accesses for these Super I/O chips, 
use the w83781d driver. However this is not the preferred method

now that this ISA driver has been developed.



Technically, the w83627thf does not support a VID reading. However, it's

possible or even likely that your mainboard maker has routed these signals

to a specific set of general purpose IO pins (the Asus P4C800-E is one such

board). The w83627thf driver now interprets these as VID. If the VID on

your board doesn't work, first see doc/vid in the lm_sensors package. If

that still doesn't help, email us at lm-sensors@lm-sensors.org.

The w83627_HF_ uses pins 110-106 as VID0-VID4. The w83627_THF_ uses the

same pins as GPIO[0:4]. Technically, the w83627_THF_ does not support a

VID reading. However the two chips have the identical 128 pin package. So,

it is possible or even likely for a w83627thf to have the VID signals routed

to these pins despite their not being labeled for that purpose. Therefore,

the w83627thf driver interprets these as VID. If the VID on your board

doesn't work, first see doc/vid in the lm_sensors package[1]. If that still

doesn't help, you may just ignore the bogus VID reading with no harm done.



For further information on this driver see the w83781d driver

documentation.

For further information on this driver see the w83781d driver documentation.



[1] http://www2.lm-sensors.nu/~lm78/cvs/browse.cgi/lm_sensors2/doc/vid

Documentation/i2c/busses/i2c-nforce2

+2 −1
Original line number Diff line number Diff line
@@ -6,6 +6,7 @@ Supported adapters: 
  * nForce3 Pro150 MCP         10de:00D4 

  * nForce3 250Gb MCP          10de:00E4 

  * nForce4 MCP                10de:0052

  * nForce4 MCP-04             10de:0034



Datasheet: not publically available, but seems to be similar to the

           AMD-8111 SMBus 2.0 adapter.

Documentation/i2c/busses/i2c-parport

+1 −0
Original line number Diff line number Diff line
@@ -17,6 +17,7 @@ It currently supports the following devices: 
 * Velleman K8000 adapter

 * ELV adapter

 * Analog Devices evaluation boards (ADM1025, ADM1030, ADM1031, ADM1032)

 * Barco LPT->DVI (K5800236) adapter



These devices use different pinout configurations, so you have to tell

the driver what you have, using the type module parameter. There is no