| /Linux-v6.1/Documentation/scsi/ |
| D | FlashPoint.rst | 8 The upgrade program described below has been officially terminated effective
78 BusLogic FlashPoint LT/BT-948 Upgrade Program
82 BusLogic FlashPoint LW/BT-958 Upgrade Program
101 the FlashPoint would be able to upgrade to the BT-946C. While this helped
134 has put in place a direct upgrade program to allow any Linux user worldwide
140 upgrade has been set at US $45 plus shipping and handling, and the upgrade
145 As of 14 June 1996, the original BusLogic FlashPoint LT to BT-948 upgrade
149 price for this upgrade has been set at US $65 plus shipping and handling.
168 participate. To summarize, BusLogic is offering Linux users an upgrade
|
| /Linux-v6.1/arch/powerpc/platforms/powermac/ |
| D | Kconfig | 25 bool "Support for powersurge upgrade cards" if EXPERT
34 both dual and quad socket upgrade cards.
|
| /Linux-v6.1/drivers/net/ethernet/pensando/ionic/ |
| D | ionic_phc.c | 325 /* Reject phc adjustments during device upgrade */ in ionic_phc_adjfine()
361 /* Reject phc adjustments during device upgrade */ in ionic_phc_adjtime()
388 /* Reject phc adjustments during device upgrade */ in ionic_phc_settime64()
417 /* Do not attempt to read device time during upgrade */ in ionic_phc_gettimex64()
441 /* Do not update phc during device upgrade, but keep polling to resume in ionic_phc_aux_work()
442 * after upgrade. Since we don't update the point in time basis, there in ionic_phc_aux_work()
444 * upgrade. After upgrade, it will need to be readjusted back to the in ionic_phc_aux_work()
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | thunderbolt.rst | 211 Before you upgrade firmware on a device, host or retimer, please make
212 sure it is a suitable upgrade. Failing to do that may render the device
216 Host NVM upgrade on Apple Macs is not supported.
234 upgrade process as follows::
261 If the platform supports, it may be possible to upgrade the retimer NVM
264 attributes: ``offline`` and ``rescan``. The way to upgrade the firmware
|
| /Linux-v6.1/drivers/char/tpm/ |
| D | tpm2-cmd.c | 405 * returns SUCCESS on TPM2_Startup in field upgrade mode. Also in tpm2_get_tpm_pt()
407 * in field upgrade mode. in tpm2_get_tpm_pt()
757 "TPM in field failure mode, requires firmware upgrade\n"); in tpm2_auto_startup()
764 * Infineon TPM in field upgrade mode will return no data for the number in tpm2_auto_startup()
768 dev_info(&chip->dev, "TPM in field upgrade mode, requires firmware upgrade\n"); in tpm2_auto_startup()
|
| /Linux-v6.1/Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 11 upgrade the ACPI execution environment that is defined by the ACPI tables
37 allows you to upgrade the buggy tables before your platform/BIOS vendor
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-driver-ucsi-ccg | 6 firmware upgrade by writing [Yy1] to the file.
|
| /Linux-v6.1/include/uapi/linux/ |
| D | rxrpc.h | 37 #define RXRPC_UPGRADEABLE_SERVICE 5 /* Upgrade service[0] -> service[1] */
55 RXRPC_UPGRADE_SERVICE = 11, /* s-: Request service upgrade for client call */
|
| /Linux-v6.1/fs/xfs/ |
| D | Kconfig | 34 should upgrade by backing up their files, reformatting, and restoring
41 upgrade xfsprogs to the latest version and try again.
|
| /Linux-v6.1/drivers/scsi/device_handler/ |
| D | scsi_dh_emc.c | 124 * indicates in-progress ucode upgrade (NDU). in trespass_endio()
127 "ucode upgrade NDU operation while sending " in trespass_endio()
140 /* check for in-progress ucode upgrade (NDU) */ in parse_sp_info_reply()
143 "ucode upgrade NDU operation while finding " in parse_sp_info_reply()
|
| D | Kconfig | 26 be sent to start it and cannot upgrade the firmware then select y.
|
| /Linux-v6.1/Documentation/networking/ |
| D | rxrpc.rst | 417 Once this has been used to establish the upgrade capability (or lack
488 upgrade one bound service to the other if requested by the client. optval
490 service ID to upgrade from and the second the service ID to upgrade to.
632 hold the same value as given to sendmsg() if the upgrade request was ignored by
690 This will automatically upgrade connections on service from_ID to service
810 bool upgrade,
836 upgrade should be set to true if a client operation should request that
837 the server upgrade the service to a better one. The resultant service ID
919 This can be used to see if a call got a service upgrade.
|
| /Linux-v6.1/net/smc/ |
| D | Kconfig | 7 RDMA over Converged Ethernet (RoCE) technology to upgrade
|
| /Linux-v6.1/scripts/ |
| D | gen_ksymdeps.sh | 11 # Use -q instead of 2>/dev/null when we upgrade the minimum version of
|
| D | check-local-export | 19 # Use --quiet instead of 2>/dev/null when we upgrade the minimum version of
|
| /Linux-v6.1/net/rxrpc/ |
| D | ar-internal.h | 145 /* Service upgrade information */
146 u16 from; /* Service ID to upgrade (if not 0) */
147 u16 to; /* service ID to upgrade to */
350 bool upgrade; /* T if service ID can be upgraded */ member
362 RXRPC_CONN_PROBING_FOR_UPGRADE, /* Probing for service upgrade */
404 bool try_upgrade; /* True if the bundle is attempting upgrade */
501 RXRPC_CALL_UPGRADE, /* Service upgrade was requested for the call */
745 bool upgrade; /* If the connection is upgradeable */ member
|
| D | af_rxrpc.c | 269 * @upgrade: Request service upgrade for call
287 bool upgrade, in rxrpc_kernel_begin_call() argument
321 cp.upgrade = upgrade; in rxrpc_kernel_begin_call()
|
| /Linux-v6.1/Documentation/ |
| D | Changes | 20 Upgrade to at **least** these software revisions before thinking you've
203 You'll probably want to upgrade.
227 debugfs. Obviously, it's a good idea to upgrade.
323 upgrade pppd to at least 2.4.0.
|
| /Linux-v6.1/Documentation/process/ |
| D | changes.rst | 20 Upgrade to at **least** these software revisions before thinking you've
203 You'll probably want to upgrade.
227 debugfs. Obviously, it's a good idea to upgrade.
323 upgrade pppd to at least 2.4.0.
|
| D | handling-regressions.rst | 476 have a "upgrade in place" model. We don't have a "upgrade with new
574 The whole point of "we do not regress" is so that people can upgrade
622 And dammit, we upgrade the kernel ALL THE TIME without upgrading any
627 upgrade random other tools that I don't even care about as I develop
631 So no. Your rule is COMPLETELY wrong. If you cannot upgrade a kernel
704 another problem, and as such caused a kernel upgrade to fail for a
|
| /Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.yaml | 28 5) Backup TRX firmware used after failed upgrade
|
| /Linux-v6.1/arch/ia64/scripts/ |
| D | toolchain-flags | 24 please upgrade to a newer version (it is safe to use this linker, but
|
| /Linux-v6.1/drivers/sbus/char/ |
| D | Kconfig | 22 able to upgrade the OBP firmware, say Y here.
|
| /Linux-v6.1/drivers/net/wireless/ath/ath6kl/ |
| D | common.h | 30 * that requires upgrade of the driver on the host side for the change to
|
| /Linux-v6.1/arch/mips/kernel/ |
| D | mips-cm.c | 56 [0x0c] = "Coherent Upgrade",
86 [0x6] = "Coherent Upgrade",
87 [0x7] = "Coherent Upgrade for Store Conditional",
|
