The translation is temporarily closed for contributions due to maintenance, please come back later.
Context English Portuguese (Brazil) State
Now that we have files <filename>boot1</filename>, <filename>boot2.bin</filename> and <filename>boot2.ldr</filename>, only the <acronym>BTX</acronym> server is missing before creating the all-in-one <filename>boot</filename> file. The <acronym>BTX</acronym> server is located in <filename>/usr/src/sys/boot/i386/btx/btx</filename>; it has its own <filename>Makefile</filename> with its own set of rules for building. The important thing to notice is that it is also compiled as a <emphasis>raw</emphasis> binary, and that it is linked to execute at address <literal>0x9000</literal>. The details can be found in <filename>/usr/src/sys/boot/i386/btx/btx/Makefile</filename>. Agora que temos arquivos <filename> boot1 </filename> , <filename> boot2.bin </filename> e <filename> boot2.ldr </filename> , apenas o servidor <acronym>BTX</acronym> est� ausente antes de criar o all-in-one <filename> bota </filename> Arquivo. O servidor <acronym>BTX</acronym> est� localizado em <filename> / usr / src / sys / boot / i386 / btx / btx </filename> ; tem o seu pr�prio <filename> Makefile </filename> com seu pr�prio conjunto de regras para a constru��o. O importante � notar que tamb�m � compilado como um <emphasis> cru </emphasis> bin�rio, e que est� ligado para executar no endere�o <literal> 0x9000 </literal> . Os detalhes podem ser encontrados em <filename> / usr / src / sys / boot / i386 / btx / btx / Makefile </filename>
In addition to labels associated with specific kernel objects, an additional class of labels exists: temporary labels. These labels are used to store update information submitted by user processes. These labels are initialized and destroyed as with other label types, but the creation event is <symbol>MAC_INTERNALIZE</symbol>, which accepts a user label to be converted to an in-kernel representation. Al�m de r�tulos associados a objetos de kernel espec�ficos, existe uma classe adicional de r�tulos: r�tulos tempor�rios. Esses r�tulos s�o usados ​​para armazenar informa��es de atualiza��o enviadas pelos processos do usu�rio. Esses r�tulos s�o inicializados e destru�dos como com outros tipos de r�tulo, mas o evento de cria��o � <symbol> MAC_INTERNALIZE </symbol> , que aceita um r�tulo de usu�rio para ser convertido em uma representa��o no kernel.
<function>int bus_get_resource(device_t dev, int type, int rid, u_long *startp, u_long *countp)</function> <function> int bus_get_resource (device_t dev, tipo int, int livrar, u_long * startp, u_long * countp) </function>
<function>u_long bus_get_resource_start(device_t dev, int type, int rid) u_long bus_get_resource_count (device_t dev, int type, int rid)</function> <function> u_long bus_get_resource_start (device_t dev, int tipo, int rid) u_long bus_get_resource_count (device_t dev, tipo int, int livrado) </function>
<function>void bus_delete_resource(device_t dev, int type, int rid)</function> <function> void bus_delete_resource (device_t dev, tipo int, int rid) </function>
<function>int bus_release_resource(device_t dev, int type, int rid, struct resource *r)</function> <function> int bus_release_resource (device_t dev, tipo int, int rid, recurso struct * r) </function>
<function>int bus_activate_resource(device_t dev, int type, int rid, struct resource *r)</function> <function>int bus_deactivate_resource(device_t dev, int type, int rid, struct resource *r)</function> <function> int bus_activate_resource (device_t dev, tipo int, int rid, recurso struct * r) </function><function> int bus_deactivate_resource (device_t dev, int tipo, int rid, struct resource * r) </function>
<emphasis>filter, filterarg</emphasis> - the filter function and its argument. If NULL is passed for filter then the whole range [lowaddr, highaddr] is considered unaccessible when doing <function>bus_dmamap_create()</function>. Otherwise the physical address of each attempted page in range [lowaddr; highaddr] is passed to the filter function which decides if it is accessible. The prototype of the filter function is: <function>int filterfunc(void *arg, bus_addr_t paddr)</function>. It must return 0 if the page is accessible, non-zero otherwise. <emphasis> filtrar, filtrar </emphasis> - a fun��o de filtro e seu argumento. Se NULL for passado para filtro, todo o intervalo [lowaddr, highaddr] ser� considerado inacess�vel ao fazer <function> bus_dmamap_create () </function> . Caso contr�rio, o endere�o f�sico de cada p�gina tentada no intervalo [lowaddr; highaddr] � passado para a fun��o de filtro que decide se � acess�vel. O prot�tipo da fun��o de filtro �: <function> int filterfunc (void * arg, bus_addr_t paddr) </function> . Ele deve retornar 0 se a p�gina estiver acess�vel, diferente de zero.
<funcdef>static void <function>xxx_action</function> </funcdef> <paramdef> <parameter>struct cam_sim *sim</parameter>, <parameter>union ccb *ccb</parameter> </paramdef> <funcdef> vazio est�tico <function> xxx_action </function></funcdef><paramdef><parameter> struct cam_sim * sim </parameter> , <parameter> uni�o ccb * ccb </parameter></paramdef>
CAM provides the framework for such asynchronous events. Some events originate from the lower levels (the SIM drivers), some events originate from the peripheral drivers, some events originate from the CAM subsystem itself. Any driver can register callbacks for some types of the asynchronous events, so that it would be notified if these events occur. O CAM fornece a estrutura para tais eventos ass�ncronos. Alguns eventos se originam dos n�veis mais baixos (os drivers SIM), alguns eventos s�o originados dos drivers perif�ricos, alguns eventos s�o originados do pr�prio subsistema CAM. Qualquer driver pode registrar retornos de chamada para alguns tipos de eventos. eventos ass�ncronos, para que seja notificado se esses eventos ocorrerem.
Each device provides different levels of configuration information. Each device has one or more configurations, of which one is selected during probe/attach. A configuration provides power and bandwidth requirements. Within each configuration there can be multiple interfaces. A device interface is a collection of endpoints. For example USB speakers can have an interface for the audio data (Audio Class) and an interface for the knobs, dials and buttons (HID Class). All interfaces in a configuration are active at the same time and can be attached to by different drivers. Each interface can have alternates, providing different quality of service parameters. In for example cameras this is used to provide different frame sizes and numbers of frames per second. Cada dispositivo fornece diferentes n�veis de informa��es de configura��o. Cada dispositivo tem uma ou mais configura��es, uma das quais � selecionada durante a sonda / conex�o. Uma configura��o fornece requisitos de pot�ncia e largura de banda. Dentro de cada configura��o pode haver v�rias interfaces. Uma interface de dispositivo � uma cole��o de pontos de extremidade.Por exemplo, os alto-falantes USB podem ter uma interface para os dados de �udio (classe de �udio) e uma interface para os bot�es, bot�es e mostradores (classe HID) .Todas as interfaces em uma configura��o est�o ativas ao mesmo tempo por diferentes drivers. Cada interface pode ter alternativas, fornecendo diferentes par�metros de qualidade de servi�o. Em c��meras, por exemplo, isso � usado para fornecer diferentes tamanhos de quadros e n�meros de quadros por segundo.
The protocol used over pipes other than the default pipe is undefined by the USB specification. Information on this can be found from various sources. The most accurate source is the developer's section on the USB home pages. From these pages, a growing number of deviceclass specifications are available. These specifications specify what a compliant device should look like from a driver perspective, basic functionality it needs to provide and the protocol that is to be used over the communication channels. The USB specification includes the description of the Hub Class. A class specification for Human Interface Devices (HID) has been created to cater for keyboards, tablets, bar-code readers, buttons, knobs, switches, etc. A third example is the class specification for mass storage devices. For a full list of device classes see the developers section on the USB home pages. O protocolo usado em outros pipes al�m do pipe padr�o � indefinido pela especifica��o USB. Informa��es sobre isso podem ser encontradas em v�rias fontes. A fonte mais precisa � a se��o do desenvolvedor nas home pages USB. A partir dessas p�ginas, um n�mero crescente de Est�o dispon�veis especifica��es deviceclass Estas especifica��es especificam como deve ser um dispositivo compat�vel do ponto de vista do driver, a funcionalidade b�sica que ele precisa fornecer e o protocolo que deve ser usado nos canais de comunica��o.A especifica��o USB inclui a descri��o da Classe Hub. Uma especifica��o de classe para dispositivos de interface humana (HID) foi criada para atender a teclados, tablets, leitores de c�digo de barras, bot�es, bot�es, switches, etc. Um terceiro exemplo � a especifica��o de classe para dispositivos de armazenamento em massa. classes de dispositivos, consulte a se��o de desenvolvedores nas p�ginas iniciais do USB.