Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 22 2月, 2013 2 次提交
  3. 19 2月, 2013 2 次提交
  5. 17 2月, 2013 3 次提交
  7. 14 2月, 2013 2 次提交
  9. 10 2月, 2013 1 次提交
  11. 07 2月, 2013 1 次提交
  13. 05 2月, 2013 1 次提交
  15. 30 1月, 2013 1 次提交
  17. 26 1月, 2013 4 次提交
  19. 24 1月, 2013 3 次提交
  21. 22 1月, 2013 2 次提交
    • P
      drivers/net: delete old fujitsu based eth16i driver · bb37f122
      由 Paul Gortmaker 提交于 
      This is another driver for relatively rare 10Mbit hardware that
originated in the early 1990's.  So we select it for removal at
this point in time as well.

Cc: Mika Kuoppala <miku@iki.fi>
Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      bb37f122
    • P
      drivers/net: delete old 8 bit ISA Racal ni5010 support. · d2477de7
      由 Paul Gortmaker 提交于 
      These cards were only available in 8bit format, and in addition
they only had AUI and BNC(10-Base2) interfaces (i.e. no RJ-45).

In fact, they are so rare, that an internet search on these old
cards almost comes up empty, unless the "Micom interlan" name
is used.

This puts them in the equivalent domain as the 3c501, so there
should be no strong opposition to the driver removal, as nobody
is seriously using 3.9+ with 8 bit ISA hardware.

In doing so, the whole "ethernet/racal" category becomes empty,
so we clean up the Makefile/Kconfig and subdir appropriately.

Cc: Andreas Mohr <andi@lisas.de>
Cc: Jan-Pascal van Best <janpascal@vanbest.org>
Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      d2477de7
  23. 18 1月, 2013 2 次提交
    • J
      net: Add support for NTB virtual ethernet device · 548c237c
      由 Jon Mason 提交于 
      A virtual ethernet device that uses the NTB transport API to
send/receive data.
Signed-off-by: NJon Mason <jon.mason@intel.com>
Reviewed-by: NNicholas Bellinger <nab@linux-iscsi.org>
Acked-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      548c237c
    • J
      PCI-Express Non-Transparent Bridge Support · fce8a7bb
      由 Jon Mason 提交于 
      A PCI-Express non-transparent bridge (NTB) is a point-to-point PCIe bus
connecting 2 systems, providing electrical isolation between the two subsystems.
A non-transparent bridge is functionally similar to a transparent bridge except
that both sides of the bridge have their own independent address domains.  The
host on one side of the bridge will not have the visibility of the complete
memory or I/O space on the other side of the bridge.  To communicate across the
non-transparent bridge, each NTB endpoint has one (or more) apertures exposed to
the local system.  Writes to these apertures are mirrored to memory on the
remote system.  Communications can also occur through the use of doorbell
registers that initiate interrupts to the alternate domain, and scratch-pad
registers accessible from both sides.

The NTB device driver is needed to configure these memory windows, doorbell, and
scratch-pad registers as well as use them in such a way as they can be turned
into a viable communication channel to the remote system.  ntb_hw.[ch]
determines the usage model (NTB to NTB or NTB to Root Port) and abstracts away
the underlying hardware to provide access and a common interface to the doorbell
registers, scratch pads, and memory windows.  These hardware interfaces are
exported so that other, non-mainlined kernel drivers can access these.
ntb_transport.[ch] also uses the exported interfaces in ntb_hw.[ch] to setup a
communication channel(s) and provide a reliable way of transferring data from
one side to the other, which it then exports so that "client" drivers can access
them.  These client drivers are used to provide a standard kernel interface
(i.e., Ethernet device) to NTB, such that Linux can transfer data from one
system to the other in a standard way.
Signed-off-by: NJon Mason <jon.mason@intel.com>
Reviewed-by: NNicholas Bellinger <nab@linux-iscsi.org>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      fce8a7bb
  25. 17 1月, 2013 2 次提交
  27. 16 1月, 2013 3 次提交
  29. 14 1月, 2013 1 次提交
  31. 12 1月, 2013 4 次提交
  33. 11 1月, 2013 1 次提交
  35. 08 1月, 2013 2 次提交
  37. 07 1月, 2013 2 次提交
  39. 05 1月, 2013 1 次提交