Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/books/arch-handbook/usb/_index.po
Translation file Download documentation/content/ko/books/arch-handbook/usb/_index.po
Last change March 6, 2023, 11:45 p.m.
Last author Kyung-tak, Yoo

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 77 4,375 27,158
Translated 1% 1 1% 1 1% 12
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 98% 76 99% 4,374 99% 27,146
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 81 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

4,375
Hosted words
77
Hosted strings
1%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+98%
Hosted words
+100%
+100%
Hosted strings
—
+1%
Translated
—
—
Contributors
+100%
User avatar cygnus6960

New translation

Documentation / books/arch-handbook/usb/_index — Korean

Introduction
소개
2 months ago
User avatar cygnus6960

New contributor

Documentation / books/arch-handbook/usb/_index — Korean

New contributor 2 months ago
User avatar None

New strings to translate

Documentation / books/arch-handbook/usb/_index — Korean

77 new strings to translate appeared to the translation. 2 months ago
User avatar None

Resource update

Documentation / books/arch-handbook/usb/_index — Korean

File documentation/content/ko/books/arch-handbook/usb/_index.po was added. 2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

The support for the USB floppy from Y-E Data is again less straightforward as a new command set has been designed.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

The Mass Storage Specification supports 2 different types of wrapping of the command block.The initial attempt was based on sending the command and status through the default pipe and using bulk transfers for the data to be moved between the host and the device. Based on experience a second approach was designed that was based on wrapping the command and status blocks and sending them over the bulk out and in endpoint. The specification specifies exactly what has to happen when and what has to be done in case an error condition is encountered. The biggest challenge when writing drivers for these devices is to fit USB based protocol into the existing support for mass storage devices. CAM provides hooks to do this in a fairly straight forward way. ATAPI is less simple as historically the IDE interface has never had many different appearances.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

Example: Mass Storage Devices Support for mass storage devices is mainly built around existing protocols. The Iomega USB Zipdrive is based on the SCSI version of their drive. The SCSI commands and status messages are wrapped in blocks and transferred over the bulk pipes to and from the device, emulating a SCSI controller over the USB wire. ATAPI and UFI commands are supported in a similar fashion.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

An example of these types of devices is the ActiveWire I/O board, based on the EZ-USB chip. For this chip a generic firmware downloader is available. The firmware downloaded into the ActiveWire board changes the revision Id. It will then perform a soft reset of the USB part of the EZ-USB chip to disconnect from the USB bus and again reconnect.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

The procedure followed is straightforward. The device identifies itself through a vendor and product Id. The first driver probes and attaches to it and downloads the firmware into it. After that the device soft resets itself and the driver is detached. After a short pause the device announces its presence on the bus. The device will have changed its vendor/product/revision Id to reflect the fact that it has been supplied with firmware and as a consequence a second driver will probe it and attach to it.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/arch-handbook/usb/_index — Korean

Example: Firmware download Many devices that have been developed are based on a general purpose processor with an additional USB core added to it. Since the development of drivers and firmware for USB devices is still very new, many devices require the downloading of the firmware after they have been connected.
 
2 months ago
Browse all translation changes