Ports 搜索

U-Boot loader and related files for the Pine64 For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader and related files for Raspberry Pi To install this bootloader, copy ALL the files in the share/u-boot/u-boot-rpi directory to the first partition, formatted as FAT16 or FAT32, on an SD card. This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file uboot.env on the FAT partition. For information about running FreeBSD on RaspberryPi, see For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader and related files for Raspberry Pi 2 To install this bootloader, copy ALL the files in the share/u-boot/u-boot-rpi2 directory to the first partition, formatted as FAT32, on an SD card. This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file uboot.env on the FAT partition. For information about running FreeBSD on RaspberryPi, see For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Banana Pi M3. To install this bootloader, follow the instructions in http://linux-sunxi.org/Bootable_SD_card#Bootloader This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file u-boot.env on the FAT partition. * The DTB file name is chosen based on the board model and passed to ubldr using the fdtfile env variable. ubldr loads the DTB from /boot/dtb/ on the FreeBSD partition. * By default, it loads ELF ubldr from file ubldr on the FAT partition to address 0x42000000, and launches it. For information about running FreeBSD on Banana Pi M3, see https://wiki.freebsd.org/FreeBSD/arm/Allwinner For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Utilite and Utilite Pro Install the cm-fx6-firmware file onto the boot disk using: dd if=cm-fx6-firmware of=/dev/whatever bs=1k skip=1 seek=1 oflag=dsync The U-Boot built by this port expects the first 1MB of the boot media to be reserved for the U-Boot executable and saved environment. The firmware file begins at an offset of 1K from the start of the boot disk. The U-Boot environment area begins at an offset of 512K. This version is patched so that: * ELF and API features are enabled to support ubldr. * A single U-Boot image supports Utilite and Utilite Pro. * When the selected board has multiple SD or MMC devices available, the mmc0 device in U-Boot (and thus the disk0 device in loader(8)) will be whichever device U-Boot was loaded from by the ROM bootloader routines. The sources for this port are based on stock U-Boot 2015.07 with patches provided by CompuLab at: http://www.compulab.co.il/wp-content/uploads/2015/10/u-boot-2015.07.tar.bz2 For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Wandboard Solo, Dual, and Quad. Install the u-boot.imx file onto the boot disk using: dd if=u-boot.imx of=/dev/whatever bs=1k oseek=1 conv=sync The U-Boot built by this port expects the first 1MB of the boot media to be reserved for the U-Boot executable and saved environment. The u-boot.imx file begins at an offset of 1K from the start of the boot disk. The U-Boot environment area begins at an offset of 512K. This version is patched so that: * ELF and API features are enabled to support ubldr. * A single U-Boot image supports Solo, Dual[lite], and Quad processors. * When the selected board has multiple SD or MMC devices available, the mmc0 device in U-Boot (and thus the disk0 device in loader(8)) will be whichever device U-Boot was loaded from by the ROM bootloader routines. The sources for this port were originally obtained from commit 87f595d1ee at https://github.com/TechNexion/U-Boot-edm/ which appears to be a slightly modified fork of the stock U-Boot 2013.10 release. As of this writing, the changes in this fork have not been rolled back into upstream U-Boot. For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

vcp copies files and directories in a curses interface, and behaves much like cp.

ipcserver and ipcclient are command-line tools for building local-domain client-server applications. They conform to the UNIX Client-Server Program Interface, UCSPI. ipcserver listens for connections on a local-domain stream socket, and runs a program for each connection it accepts. The program environment includes variables that hold the local and remote socket addresses, and the effective user and group IDs of the process that called connect. ipcserver offers a concurrency limit on acceptance of new connections, and selective handling of connections based on client identity. ipcclient requests a connection to a local-domain socket, and runs a program. The program environment includes a variable that holds the local socket address. ipcperl is an example of an ipchandle server. It invokes a perl subroutine for each request.

This package contains a proxy program that passes data back and forth between two connections set up by a UCSPI server and a UCSPI client.

Unix domain socket client and server programs that conform to UCSPI, the Unix Client-Server Program Interface.