Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 01 2月, 2011 1 次提交
  3. 22 1月, 2011 1 次提交
  5. 14 1月, 2011 1 次提交
  7. 29 12月, 2010 4 次提交
  9. 17 12月, 2010 1 次提交
  11. 03 12月, 2010 1 次提交
  13. 20 11月, 2010 1 次提交
    • M
      Staging: sep: Introduce sep driver · 4856ab33
      由 Mark Allyn 提交于 
      This driver is for the Security Processor, a dedicated encryption
and decryption driver that is used on the Intel mobile platform.

This has been checked with checkpatch and there are four
warnings for lines over 80 charactors.

There is one compile warning. This is for a function that is
only used if the rar register driver is needed. There is an
ifdef in a header file that stubs out the rar register driver
if the rar register is not configured.

This driver does add a configuration, which is CONFIG_DX_SEP.
Signed-off-by: NMark Allyn <mark.a.allyn@intel.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      4856ab33
  15. 16 11月, 2010 1 次提交
  17. 10 11月, 2010 2 次提交
  19. 30 10月, 2010 1 次提交
  21. 21 10月, 2010 2 次提交
    • 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
  23. 08 10月, 2010 1 次提交
  25. 06 10月, 2010 3 次提交
    • V
      Staging: sst: Intel SST audio driver · fffa1cca
      由 Vinod Koul 提交于 
      This is the Intel SST audio driver.

As compared to the previous versions it has all the printks and other stuff
noted cleaned up and more hardware support. The Aava support is disabled in
this patch (is_aava resolves to 0) because the Aava board detection logic
is not yet upstream.

The driver itself is a combination of a traditional ALSA driver and a
hardware assisted offload driver which can play audio while the processor
is asleep but which can't do all the more interactive stuff.

In the general case most software would use the ALSA interface, but the
other interface is needed for certain classes of use such as music playback
on highly power consumption sensitive devices.

This is going to staging primarily because it depends upon the staging memrar
driver.
Signed-off-by: NVinod Koul <vinod.koul@intel.com>
Signed-off-by: NHarsha Priya <priya.harsha@intel.com>
[Merged together and tweaked for -next]
Signed-off-by: NAlan Cox <alan@linux.intel.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      fffa1cca
    • A
      smbfs: move to drivers/staging · 2116b7a4
      由 Arnd Bergmann 提交于 
      smbfs has been scheduled for removal in 2.6.27, so
maybe we can now move it to drivers/staging on the
way out.

smbfs still uses the big kernel lock and nobody
is going to fix that, so we should be getting
rid of it soon.

This removes the 32 bit compat mount and ioctl
handling code, which is implemented in common fs
code, and moves all smbfs related files into
drivers/staging/smbfs.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
Acked-by: NJeff Layton <jlayton@redhat.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      2116b7a4
    • A
      autofs3: move to drivers/staging · db7bee24
      由 Arnd Bergmann 提交于 
      Nobody appears to be interested in fixing autofs3 bugs
any more and it uses the BKL, which is going away.

Move this to staging for retirement. Unless someone
complains until 2.6.38, we can remove it for good.

The include/linux/auto_fs.h header file is still used
by autofs4, so it remains in place.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
Cc: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>
Acked-by: NH. Peter Anvin <hpa@zytor.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      db7bee24
  27. 02 10月, 2010 1 次提交
  29. 30 9月, 2010 1 次提交
    • A
      staging: olpc_dcon: add OLPC display controller (DCON) support · eecb3e4e
      由 Andres Salomon 提交于 
      This adds DCON support for the OLPC XO.  The DCON is found in XO-1 and
XO-1.5 hardware.  The XO-1 has a CS5536 southbridge, while the XO-1.5
has a Via chipset; the GPIO magic that's necessary to communicate with
the DCON chip is unfortunately different across both platforms.  This
driver supports both.

This driver is in bad state atm, so I'm requesting its inclusion into
staging so it can be cleaned up while staying in the kernel tree.

Original driver by Dave Woodhouse, and modified extensively by
Jordan Crouse, myself, Deepak Saxena, Paul Fox, Daniel Drake, and
probably others that I've missed.
Signed-off-by: NAndres Salomon <dilinger@queued.net>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      eecb3e4e
  31. 22 9月, 2010 1 次提交
  33. 09 9月, 2010 2 次提交
  35. 08 9月, 2010 1 次提交
  37. 03 9月, 2010 1 次提交
    • V
      staging: add ath6kl driver for AR6003 chip · 30295c89
      由 Vipin Mehta 提交于 
      AR6003 is a single stream, SDIO based 802.11 chipset from
Atheros optimized for mobile and embedded devices. ath6kl is a
cfg80211 driver for AR6003 and supports both the station and
AP mode of operation.

Station mode supports 802.11 a/b/g/n with HT20 on 2.4/5GHz and
HT40 only on 5GHz. Some of the other features include WPA/WPA2,
WPS, WMM, WMM-PS, and BT coexistence. AP mode can be operated
only in b/g mode with support for a subset of features mentioned
above.

The driver supports cfg80211 but comes with its own set of
wext ioctls which have historically supported some of our
customers with features like BT 3.0 and AP mode of operation.

For further details, please refer to:

http://wireless.kernel.org/en/users/Drivers/ath6kl

The driver requires firmware that runs on the chip's network
processor. The majority of it is stored in ROM. The binaries
that are downloaded and executed from RAM are as follows:

1) Patch against the code in ROM for bug fixes and feature
   enhancements.
2) Code to copy the data from the OTP region of the memory
   into RAM.
3) Calibration file carrying board specific data.

The above files need to be present in the directory
'/lib/firmware/ath6k/AR6003/hw2.0/' for the driver to initialize
the chip upon enumeration. The files can be downloaded from the
link specified at the following location:

http://wireless.kernel.org/en/users/Drivers/ath6kl#Download

This driver is only provided in the interim while we work on
the mac80211 replacement, ath6k. Once the mac80211 driver
achieves feature parity with the ath6kl driver, the ath6kl will
be deprecated and removed from staging.
Signed-off-by: NVipin Mehta <vmehta@atheros.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      30295c89
  39. 02 9月, 2010 1 次提交
  41. 31 8月, 2010 3 次提交
    • K
      Staging: Add SBE 2T3E3 WAN driver · 921a86e0
      由 Krzysztof Halasa 提交于 
      This is a driver for SBE Inc.'s dual port T3/E3 WAN cards. Based on
their original GPLed driver.

The original driver tarball is now accessible at
http://userweb.kernel.org/~chris/SBE_2T3_Linux_2.0c.tgz

It needs at least a new generic HDLC setup code (not yet written) before
moving to drivers/net/wan.
Signed-off-by: NKrzysztof Hałasa <khc@pm.waw.pl>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      921a86e0
    • D
      Staging: add West Bridge Astoria Driver · 81eb669b
      由 David Cross 提交于 
      This is a driver for the Cypress West Bridge companion chip. Its
function is analogous to the North/South Bridges of PC environments
applied to embedded devices, in that it expands I/O and storage
capabilities of an embedded processor. The Astoria version, which this
driver applies to, functions as a USB, embedded memory and SDIO
controller. The kernel that this patch was applied to is linux-2.6.35,
although it was tested using the android kernel 2.6.29 running on the
Zoom 2 platform. In this system, it was used primarily as a sideloading
accelerator enabling direct data transfers between a USB host PC and
embedded memory without system overheads.  Minor modifications were also
made to the kernel for this patch. These include changes such as
EXPORTing of fat_get_block in the kernel code. Another function,
mpage_cleardirty was also added to the memory management code. This
function is used to clear the dirty pages from a specific inode. This
allows for direct, file based DMA. None of these changes are believed to
have any negative impact on the kernel and may provide additional
benefit for other developers and drivers.

The driver, as submitted, was placed into the drivers/staging/westbridge
folder as the directory structure it will eventually reside in is not yet
defined. The driver, as placed in staging is divided into four parts:
1) gadget - this implements a gadget peripheral controller and includes IOCTLs
for MTP transfers
2) block -this implements a generic block device driver to enable access to
embedded memory
3) api -this is the Cypress SDK, and includes USB and Storage specific
functions. In addition, it includes common code for low level routines such as
message passing and common data transfer routines
4) hal - this should likely be included in the arch directory as it needs to
be modified for a given platform. The directory structure in the staging area
is meant to reflect the eventual location of where this code likely should be.
It is platform specific. In this case, the HAL included is for the Android
Zoom 2 platform. Here, West Bridge is connected to the GPMC (general purpose
memory controller) of the OMAP3. Specific timing needs to be enabled to ensure
reliable communication.
Many thanks to Greg KH for conducting initial reviews and providing pointers.
Please contact david.cross@cypress.com for questions, concerns or feedback.
Signed-off-by: NDavid Cross <david.cross@cypress.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      81eb669b
    • G
      Staging: delete rtl8192su driver · 760ffce8
      由 Greg Kroah-Hartman 提交于 
      Now that we have a much better driver for this device (rtl8712), delete
this driver as it is no longer needed.

Cc: Larry Finger <Larry.Finger@lwfinger.net>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      760ffce8
  43. 24 8月, 2010 1 次提交
  45. 20 8月, 2010 1 次提交
  47. 03 8月, 2010 3 次提交
  49. 09 7月, 2010 1 次提交
  51. 25 6月, 2010 1 次提交
  53. 23 6月, 2010 1 次提交
  55. 19 6月, 2010 1 次提交