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/isa/_index.po
Translation file Download documentation/content/es/books/arch-handbook/isa/_index.po
Last change July 18, 2023, 7:57 a.m.
Last author Fernando Apesteguía

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 368 10,361 69,046
Translated 100% 368 100% 10,361 100% 69,046
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 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 1 change 0 changes 1 change 0 changes 0 changes 84 changes 0 changes 49 changes 0 changes 0 changes 0 changes 29 changes 0 changes 232 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

10,361
Hosted words
368
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Committed changes

Documentation / books/arch-handbook/isa/_index — Spanish

Committed changes 4 months ago
User avatar fernape

Translation changed

Documentation / books/arch-handbook/isa/_index — Spanish

Synopsis
Sinopsis
4 months ago
User avatar fernape

Translation changed

Documentation / books/arch-handbook/isa/_index — Spanish

/* many things get inherited from the parent tag
* sc->data is supposed to point to the structure with the shared data,
* for example for a ring buffer it could be:
* struct {
* u_short rd_pos;
* u_short wr_pos;
* char bf[XXX_RING_BUFFER_SIZE]
* } *data;
*/
error=bus_dma_tag_create(sc->parent_tag, 1,
0, BUS_SPACE_MAXADDR, 0, /*filter*/ NULL, /*filterarg*/ NULL,
/*maxsize*/ sizeof(* sc->data), /*nsegments*/ 1,
/*maxsegsz*/ sizeof(* sc->data), /*flags*/ 0,
&sc->data_tag);
if(error)
goto bad;
/* many things get inherited from the parent tag
* sc->data is supposed to point to the structure with the shared data,
* for example for a ring buffer it could be:
* struct {
* u_short rd_pos;
* u_short wr_pos;
* char bf[XXX_RING_BUFFER_SIZE]
* } *data;
*/
error=bus_dma_tag_create(sc->parent_tag, 1,
0, BUS_SPACE_MAXADDR, 0, /*filter*/ NULL, /*filterarg*/ NULL,
/*maxsize*/ sizeof(* sc->data), /*nsegments*/ 1,
/*maxsegsz*/ sizeof(* sc->data), /*flags*/ 0,
&sc->data_tag);
if(error)
goto bad;
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

The interrupt handler has to acknowledge interrupt to the device only but not to the interrupt controller, the system takes care of the latter.
El manejador de interrupción tiene que reconocer la interrupción ante el dispositivo pero no ante el controlador, el sistema se encarga de esto último.
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

while(xxx_interrupt_pending(sc)) {
xxx_process_interrupt(sc);
xxx_acknowledge_interrupt(sc);
}
while(xxx_interrupt_pending(sc)) {
xxx_process_interrupt(sc);
xxx_acknowledge_interrupt(sc);
}
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

To avoid races it is commonly written as a loop:
Pare evitar carreras se suele escribir como un bucle:
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

It runs at the interrupt priority level specified by the interrupt type parameter of `bus_setup_intr()`. That means that all the other interrupts of the same type as well as all the software interrupts are disabled.
Se ejecuta en el nivel de prioridad de la interrupción especificado por el parámetro tipo de interrupción de `bus_setup_intr()`. Eso significa que las demás interrupciones del mismo tipo así como las interrupciones software están deshabilitadas.
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

static void
xxx_intr(struct xxx_softc *sc)
{
static void
xxx_intr(struct xxx_softc *sc)
{
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

The old convention for the ISA drivers was getting the device unit number as an argument. This is obsolete, and the new drivers receive whatever argument was specified for them in the attach routine when calling `bus_setup_intr()`. By the new convention it should be the pointer to the structure softc. So the interrupt handler commonly starts as:
La antigua convención para los controladores ISA era obtener el número de unidad del dispositivo como un argumento. Esto está obsoleto, y los nuevos controladores reciben cualquier argumento que se haya especificado en la rutina de adjuntar cuando se llama a `bus_setup_intr()`. Según la nueva convención debería ser un puntero a la estructura softc. De forma que el manejador de interrupción normalmente comienza así:
4 months ago
User avatar fernape

New translation

Documentation / books/arch-handbook/isa/_index — Spanish

The interrupt handler is called when an interrupt is received which may be from this particular device. The ISA bus does not support interrupt sharing (except in some special cases) so in practice if the interrupt handler is called then the interrupt almost for sure came from its device. Still, the interrupt handler must poll the device registers and make sure that the interrupt was generated by its device. If not it should just return.
El manejador de interrupción se llama cuando se recibe una interrupción que podría ser de este dispositivo particular. El bus ISA no tiene soporte para compartir interrupciones (excepto en algunos casos especiales) así que en la práctica el manejador de interrupción se llama cuando la interrupción casi seguro que proviene de este dispositivo. Aún así, el manejador de interrupción debe sondear los registros del dispositivo y asegurarse que la interrupción vino de él. Si no es así simplemente debe retornar.
4 months ago
Browse all translation changes