Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 24 9月, 2009 1 次提交
  3. 09 9月, 2009 1 次提交
    • L
      wireless: mark prism54 as deprecated and mark for removal · 4d8cd268
      由 Luis R. Rodriguez 提交于 
      The preferred module is p54pci which also supports FullMAC
PCI / Cardbus devices. We schedule removal for 2.6.34. Reason
to remove this is no one really is testing prism54 anymore,
and while it works p54pci provides support for the same hardware.
It should be noted I have been told some FullMAC devices may not
have worked with the SoftMAC driver but to date we have yet to
recieve a single bug report regarding this. If there are users
out there please let us know!

Cc: aquilaver@yahoo.com
Cc: linux-kernel@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>
Cc: Kai Engert <kengert@redhat.com>
Cc: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Tim de Waal<tim.dewaal@yahoo.com>
Cc: Roy Marples <uberlord@gentoo.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christian Lamparter <chunkeey@web.de>
Cc: Björn Steinbrink <B.Steinbrink@gmx.de>
Cc: Tim Gardner <tim.gardner@canonical.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4d8cd268
  5. 02 9月, 2009 1 次提交
  7. 10 8月, 2009 9 次提交
  9. 10 7月, 2009 1 次提交
  11. 07 7月, 2009 1 次提交
  13. 05 7月, 2009 1 次提交
  15. 19 6月, 2009 3 次提交
  17. 04 6月, 2009 1 次提交
    • J
      rfkill: create useful userspace interface · c64fb016
      由 Johannes Berg 提交于 
      The new code added by this patch will make rfkill create
a misc character device /dev/rfkill that userspace can use
to control rfkill soft blocks and get status of devices as
well as events when the status changes.

Using it is very simple -- when you open it you can read
a number of times to get the initial state, and every
further read blocks (you can poll) on getting the next
event from the kernel. The same structure you read is
also used when writing to it to change the soft block of
a given device, all devices of a given type, or all
devices.

This also makes CONFIG_RFKILL_INPUT selectable again in
order to be able to test without it present since its
functionality can now be replaced by userspace entirely
and distros and users may not want the input part of
rfkill interfering with their userspace code. We will
also write a userspace daemon to handle all that and
consequently add the input code to the feature removal
schedule.

In order to have rfkilld support both kernels with and
without CONFIG_RFKILL_INPUT (or new kernels after its
eventual removal) we also add an ioctl (that only exists
if rfkill-input is present) to disable rfkill-input.
It is not very efficient, but at least gives the correct
behaviour in all cases.
Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
Acked-by: NMarcel Holtmann <marcel@holtmann.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      c64fb016
  19. 29 5月, 2009 1 次提交
  21. 13 4月, 2009 1 次提交
  23. 07 4月, 2009 1 次提交
  25. 03 4月, 2009 1 次提交
  27. 01 4月, 2009 1 次提交
  29. 30 3月, 2009 2 次提交
  31. 29 3月, 2009 1 次提交
  33. 28 3月, 2009 3 次提交
  35. 21 3月, 2009 1 次提交
  37. 13 3月, 2009 2 次提交
  39. 10 3月, 2009 1 次提交
  41. 30 1月, 2009 1 次提交
  43. 07 1月, 2009 1 次提交
  45. 02 1月, 2009 1 次提交
  47. 01 1月, 2009 1 次提交
    • P
      selinux: Deprecate and schedule the removal of the the compat_net functionality · 277d342f
      由 Paul Moore 提交于 
      This patch is the first step towards removing the old "compat_net" code from
the kernel.  Secmark, the "compat_net" replacement was first introduced in
2.6.18 (September 2006) and the major Linux distributions with SELinux support
have transitioned to Secmark so it is time to start deprecating the "compat_net"
mechanism.  Testing a patched version of 2.6.28-rc6 with the initial release of
Fedora Core 5 did not show any problems when running in enforcing mode.

This patch adds an entry to the feature-removal-schedule.txt file and removes
the SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT configuration option, forcing
Secmark on by default although it can still be disabled at runtime.  The patch
also makes the Secmark permission checks "dynamic" in the sense that they are
only executed when Secmark is configured; this should help prevent problems
with older distributions that have not yet migrated to Secmark.
Signed-off-by: NPaul Moore <paul.moore@hp.com>
Acked-by: NJames Morris <jmorris@namei.org>
      277d342f
  49. 12 12月, 2008 1 次提交
  51. 11 11月, 2008 1 次提交