# packages

pkgId: 6d44dc2b128361360a64ef76b9f9e6ca9d4287b352f61ea4710f32f17d6893c2
name: acpi_call
arch: src
version: 1.1.0
epoch: 0
release: 6.fc24
summary: Kernel module that enables you to call ACPI methods to /proc/acpi/call
url: https://github.com/mkottman/acpi_call
rpm_license: GPL
rpm_group: System Environment/Kernel
rpm_buildhost: f24dev32.aritgw.de
location_href: acpi_call-1.1.0-6.fc24.src.rpm
checksum_type: sha256
description:
  A kernel module that enables you to call ACPI methods by writing the method
  name followed by arguments to /proc/acpi/call


pkgId: 8f4fab6adfe2fa2374a4a63167d673ef4a7e55616a7a07f795455de83eedb85b
name: gobi_loader
arch: src
version: 0.8
epoch: 0
release: 7.fc24
summary: Firmware loader for Qualcomm Gobi WWAN devices
url: http://www.codon.org.uk/~mjg59/gobi_loader
rpm_license: GPLv2
rpm_group: Applications/System
rpm_buildhost: f24dev32.aritgw.de
location_href: gobi_loader-0.8-7.fc24.src.rpm
checksum_type: sha256
description:
  gobi_loader is a firmware loader for Qualcomm Gobi USB chipsets. These
  devices appear in an uninitialized state when power is applied and require
  firmware to be loaded before they can be used as modems. gobi_loader adds
  a udev rule that will trigger loading of the firmware and make the modem
  usable.

  Note that gobi_loader requires firmware images which can't be
  freely redistributed.

  See
    http://www.codon.org.uk/~mjg59/gobi_loader or
    http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000 or
    http://thinkwiki.de/Qualcomm_Gobi_2000_unter_Linux_installieren
  for more information.


pkgId: a1090fc1396267aa7e6be57f756567c4c37589c790fb4a62be0fe6fff7acbdf0
name: tp_smapi
arch: src
version: 0.41
epoch: 0
release: 6.fc24
summary: Thinkpad hardware/firmware features
url: http://www.thinkwiki.org/wiki/Tp_smapi
rpm_license: GPL
rpm_group: Development/System
rpm_buildhost: f24dev32.aritgw.de
location_href: tp_smapi-0.41-6.fc24.src.rpm
checksum_type: sha256
description:
  The tp_smapi kernel module exposes some features of the ThinkPad
  hardware/firmware via a sysfs interface. Currently, the main implemented
  functionality is control of battery charging and extended battery
  status. The underlfying hardware interfaces are SMAPI and direct access
  to the embedded controller


