Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 20 3月, 2011 2 次提交
  3. 16 3月, 2011 1 次提交
  5. 22 2月, 2011 1 次提交
  7. 03 2月, 2011 1 次提交
  9. 21 1月, 2011 1 次提交
  11. 20 1月, 2011 1 次提交
    • J
      netfilter: xtables: connlimit revision 1 · cc4fc022
      由 Jan Engelhardt 提交于 
      This adds destination address-based selection. The old "inverse"
member is overloaded (memory-wise) with a new "flags" variable,
similar to how J.Park did it with xt_string rev 1. Since revision 0
userspace only sets flag 0x1, no great changes are made to explicitly
test for different revisions.
Signed-off-by: NJan Engelhardt <jengelh@medozas.de>
      cc4fc022
  13. 14 1月, 2011 1 次提交
  15. 13 1月, 2011 1 次提交
  17. 12 1月, 2011 1 次提交
    • Z
      ACPI: delete CONFIG_ACPI_PROCFS_POWER and power procfs I/F in 2.6.39 · 6d855fcd
      由 Zhang Rui 提交于 
      sysfs I/F for ACPI power devices, including AC and Battery,
has been working in upstream kenrel since 2.6.24, Sep 2007.
In 2.6.37, we made the sysfs I/F always built in and this option
disabled by default.
Now, we plan to remove this option and the ACPI power procfs
interface in 2.6.39.

First, update the feature-removal-schedule to announce this change.
Second, add runtime warnings in ACPI AC/Battery/SBS driver, so that
users will notice this change even if "make oldconfig" is used.
Signed-off-by: NZhang Rui <rui.zhang@intel.com>
Signed-off-by: NLen Brown <len.brown@intel.com>
      6d855fcd
  19. 29 12月, 2010 3 次提交
  21. 15 12月, 2010 1 次提交
  23. 16 11月, 2010 1 次提交
  25. 28 10月, 2010 1 次提交
  27. 21 10月, 2010 3 次提交
    • M
      V4L/DVB: Deprecate stradis driver · 96322b80
      由 Mauro Carvalho Chehab 提交于 
      The driver author seems to not worked on this driver since its conversion
from 2.2 to 2.4. Nobody is known to have a stradis hardware for testing. As
it still uses V4L1 API, BKL and probably some other old stuff, someone would
need to work on it to preserve the driver. Instead of investing time and
efforts to keep porting it to work with new API's, it seems better to just
drop the driver.

So, let's move it to drivers/staging and label it to die at 2.6.38, if nobody
cares enough to port parallel port support to gspca or to create a new driver
that uses the same gspca-cpia sub-driver.
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      96322b80
    • M
      V4L/DVB: Deprecate cpia driver (used for parallel port webcams) · 7af97eff
      由 Mauro Carvalho Chehab 提交于 
      cpia driver were re-written inside gspca driver, for USB devices. The only
functionality that were not migrated is the support for parallel port,
as:
	1) the developer didn't find any hardware;
	2) it doesn't  seem important to keep support for a parallel port webcam,
	   as this is an obsolete technology;
	3) the changes at gspca for it to work with parallel port would be very large;
	4) this driver still uses BKL.

So, let's move it to drivers/staging and label it to die at 2.6.38, if nobody
cares enough to port parallel port support to gspca or to create a new driver
that uses the same gspca-cpia sub-driver.
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      7af97eff
    • H
      V4L/DVB: Documentation: update now that the vtx/videotext API has been removed · f44026db
      由 Hans Verkuil 提交于 
      Remove all references to /dev/vtx in the documentation, except for
some historical comments in dev-teletext.xml.

Documentation/devices.txt is not updated, this will go through Alan Cox
who maintains this file.
Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      f44026db
  29. 11 10月, 2010 1 次提交
    • S
      ieee1394: remove the old IEEE 1394 driver stack · 66fa12c5
      由 Stefan Richter 提交于 
      The drivers
  - ohci1394 (controller driver)
  - ieee1394 (core)
  - dv1394, raw1394, video1394 (userspace ABI)
  - eth1394, sbp2 (protocol drivers)
are replaced by
  - firewire-ohci (controller driver)
  - firewire-core (core and userspace ABI)
  - firewire-net, firewire-sbp2 (protocol drivers)
which are more featureful, better performing, and more secure than the older
drivers; all with a smaller and more modern code base.

The driver firedtv in drivers/media/dvb/firewire/ contains backends to both
ieee1394 and firewire-core.  Its ieee1394 backend code can be removed in an
independent commit; firedtv as-is builds and works fine without ieee1394.

The driver pcilynx (an incomplete controller driver) is deleted without
replacement since PCILynx cards are extremely rare.  Owners of these cards
use them with the stand-alone bus sniffer driver nosy instead.

The drivers nosy and init_ohci1394_dma which do not interact with either of
the two IEEE 1394 stacks are not affected by the ieee1394 subsystem removal.

There are still some issues with the newer firewire subsystem compared to
the older one:
  - The rare and quirky controllers ALi M52xx, Apple UniNorth v1, NVIDIA
    NForce2 are even less well supported by firewire-ohci than by ohci1394.
    I am looking into the M52xx issue.
  - The experimental firewire-net is reportedly less stable than its
    experimental cousin eth1394.
  - Audio playback of a certain group of audio devices (ones based on DICE
    chipset with EAP; supported by prerelease FFADO code) does not work yet.
    This issue is still under investigation.
  - There were some ieee1394 based out-of-the-mainline drivers.  Of them,
    only lisight, an audio driver for iSight webcams, seems still useful.
    Work is underway to reimplement it on top of firewire-core.

All these remainig issues are minor; they should not stand in the way of
overall better user experience of IEEE 1394 on Linux, together with a
reduction in support efforts and maintenance burden.  The coexistence of two
IEEE 1394 kernel driver stacks in the mainline since 2.6.22 shall end now,
as announced earlier this year.
Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      66fa12c5
  31. 06 10月, 2010 1 次提交
  33. 23 9月, 2010 1 次提交
  35. 24 8月, 2010 1 次提交
    • A
      x86, vmware: Remove deprecated VMI kernel support · 9863c90f
      由 Alok Kataria 提交于 
      With the recent innovations in CPU hardware acceleration technologies
from Intel and AMD, VMware ran a few experiments to compare these
techniques to guest paravirtualization technique on VMware's platform.
These hardware assisted virtualization techniques have outperformed the
performance benefits provided by VMI in most of the workloads. VMware
expects that these hardware features will be ubiquitous in a couple of
years, as a result, VMware has started a phased retirement of this
feature from the hypervisor.

Please note that VMI has always been an optimization and non-VMI kernels
still work fine on VMware's platform.
Latest versions of VMware's product which support VMI are,
Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence
releases for these products will continue supporting VMI.

For more details about VMI retirement take a look at this,
http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html

This feature removal was scheduled for 2.6.37 back in September 2009.
Signed-off-by: NAlok N Kataria <akataria@vmware.com>
LKML-Reference: <1282600151.19396.22.camel@ank32.eng.vmware.com>
Signed-off-by: NH. Peter Anvin <hpa@linux.intel.com>
      9863c90f
  37. 11 8月, 2010 2 次提交
  39. 10 8月, 2010 1 次提交
  41. 04 8月, 2010 1 次提交
  43. 03 8月, 2010 6 次提交
  45. 01 8月, 2010 2 次提交
  47. 31 7月, 2010 1 次提交
  49. 28 7月, 2010 1 次提交
  51. 27 7月, 2010 1 次提交
  53. 25 7月, 2010 1 次提交
  55. 19 7月, 2010 1 次提交