15 Jul, 2019

1 commit


04 Jun, 2018

1 commit

  • The "Clear Error Unit" may be smaller than the ECC unit size on some
    devices. For example, poison may be tracked at 64-byte alignment even
    though the ECC unit is larger. Unless / until the ACPI specification
    provides a non-ambiguous way to communicate this property do not expose
    this to userspace.

    Software that had been using this property must already be prepared for
    the case where the property is not provided on older kernels, so it is
    safe to remove this attribute.

    Signed-off-by: Dan Williams

    Dan Williams
     

24 Feb, 2016

1 commit

  • This was scheduled to be removed in 2012 by:

    commit 69c86373c6ea1149aa559e6088362d58d8ec8835
    Author: florian@mickler.org
    Date: Wed Feb 24 12:05:16 2010 +0100

    Document the rfkill sysfs ABI

    This moves sysfs ABI info from Documentation/rfkill.txt to the
    ABI subfolder and reformats it.

    This also schedules the deprecated sysfs parts to be removed in
    2012 (claim file) and 2014 (state file).

    Signed-off-by: Florian Mickler
    Signed-off-by: John W. Linville

    Signed-off-by: João Paulo Rechi Vita
    Signed-off-by: Johannes Berg

    João Paulo Rechi Vita
     

28 Sep, 2014

1 commit

  • Per commit "77873803363c net_dma: mark broken" net_dma is no longer used
    and there is no plan to fix it.

    This is the mechanical removal of bits in CONFIG_NET_DMA ifdef guards.
    Reverting the remainder of the net_dma induced changes is deferred to
    subsequent patches.

    Marked for stable due to Roman's report of a memory leak in
    dma_pin_iovec_pages():

    https://lkml.org/lkml/2014/9/3/177

    Cc: Dave Jiang
    Cc: Vinod Koul
    Cc: David Whipple
    Cc: Alexander Duyck
    Cc:
    Reported-by: Roman Gushchin
    Acked-by: David S. Miller
    Signed-off-by: Dan Williams

    Dan Williams
     

09 May, 2012

1 commit

  • This patch removes ip_queue support which was marked as obsolete
    years ago. The nfnetlink_queue modules provides more advanced
    user-space packet queueing mechanism.

    This patch also removes capability code included in SELinux that
    refers to ip_queue. Otherwise, we break compilation.

    Several warning has been sent regarding this to the mailing list
    in the past month without anyone rising the hand to stop this
    with some strong argument.

    Signed-off-by: Pablo Neira Ayuso

    Pablo Neira Ayuso
     

16 Feb, 2012

1 commit


28 Sep, 2011

1 commit


05 Aug, 2011

1 commit


24 May, 2011

1 commit


11 Oct, 2010

1 commit

  • 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: Stefan Richter

    Stefan Richter
     

10 Jul, 2007

1 commit

  • Based on patch "the scheduled removal of RAW1394_REQ_ISO_{SEND,LISTEN}"
    from Adrian Bunk, November 20 2006.

    This patch also removes the underlying facilities in ohci1394 and
    disables them in pcilynx. That is, hpsb_host_driver.devctl() and
    hpsb_host_driver.transmit_packet() are no longer used for iso reception
    and transmission.

    Since video1394 and dv1394 only work with ohci1394 and raw1394's rawiso
    interface has never been implemented in pcilynx, pcilynx is now no
    longer useful for isochronous applications.

    raw1394 will still handle the request types but will complete the
    requests with errors that indicate API version conflicts.

    Signed-off-by: Stefan Richter

    Stefan Richter
     

09 May, 2007

1 commit


26 Sep, 2006

1 commit