요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.
1. 요약·해설
원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.
2. 영어 원문 전체
번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.
원문 전체 펼치기
===========
Metronomefb
===========
Maintained by Jaya Kumar <jayakumar.lkml.gmail.com>
Last revised: Mar 10, 2008
Metronomefb is a driver for the Metronome display controller. The controller
is from E-Ink Corporation. It is intended to be used to drive the E-Ink
Vizplex display media. E-Ink hosts some details of this controller and the
display media here http://www.e-ink.com/products/matrix/metronome.html .
Metronome is interfaced to the host CPU through the AMLCD interface. The
host CPU generates the control information and the image in a framebuffer
which is then delivered to the AMLCD interface by a host specific method.
The display and error status are each pulled through individual GPIOs.
Metronomefb is platform independent and depends on a board specific driver
to do all physical IO work. Currently, an example is implemented for the
PXA board used in the AM-200 EPD devkit. This example is am200epd.c
Metronomefb requires waveform information which is delivered via the AMLCD
interface to the metronome controller. The waveform information is expected to
be delivered from userspace via the firmware class interface. The waveform file
can be compressed as long as your udev or hotplug script is aware of the need
to uncompress it before delivering it. metronomefb will ask for metronome.wbf
which would typically go into /lib/firmware/metronome.wbf depending on your
udev/hotplug setup. I have only tested with a single waveform file which was
originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
Caution should be exercised when manipulating the waveform as there may be
a possibility that it could have some permanent effects on the display media.
I neither have access to nor know exactly what the waveform does in terms of
the physical media.
Metronomefb uses the deferred IO interface so that it can provide a memory
mappable frame buffer. It has been tested with tinyx (Xfbdev). It is known
to work at this time with xeyes, xclock, xloadimage, xpdf.
3. 한국어 전문 번역
영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.
Metronome E-Ink controller와 AMLCD 연결
1-18`Metronomefb`는 E-Ink Corporation의 Metronome display controller용 드라이버이며 E-Ink Vizplex display media를 구동하도록 만들어졌습니다. 문서는 당시 제품 정보 URL `http://www.e-ink.com/products/matrix/metronome.html`을 제공합니다.
Metronome은 AMLCD interface를 통해 host CPU에 연결됩니다. host CPU가 framebuffer에 control 정보와 image를 만들고 host별 방식으로 AMLCD interface에 전달합니다. display status와 error status는 각각 별도 GPIO에서 읽습니다.
===========
Metronomefb
===========
Maintained by Jaya Kumar <jayakumar.lkml.gmail.com>
Last revised: Mar 10, 2008
Metronomefb is a driver for the Metronome display controller. The controller
is from E-Ink Corporation. It is intended to be used to drive the E-Ink
Vizplex display media. E-Ink hosts some details of this controller and the
display media here http://www.e-ink.com/products/matrix/metronome.html .
Metronome is interfaced to the host CPU through the AMLCD interface. The
host CPU generates the control information and the image in a framebuffer
which is then delivered to the AMLCD interface by a host specific method.
The display and error status are each pulled through individual GPIOs.
보드 드라이버와 waveform firmware
19-34`Metronomefb` 자체는 platform 독립적이며 모든 물리 I/O는 board-specific driver에 의존합니다. 예시는 AM-200 EPD devkit의 PXA board용 `am200epd.c`입니다.
controller에는 AMLCD interface로 보내는 waveform 정보가 필요합니다. waveform은 firmware class interface를 통해 user space에서 전달하며, `udev` 또는 `hotplug` script가 전달 전에 압축을 풀 수 있다면 압축 파일도 사용할 수 있습니다.
드라이버는 `metronome.wbf`를 요청하고 보통 `/lib/firmware/metronome.wbf`에 둡니다. 문서 작성자는 `23P01201_60_WT0107_MTC`로 표시된 waveform 하나만 시험했으며 이름의 의미와 물리 media에서 waveform이 정확히 무엇을 하는지는 알지 못한다고 밝힙니다.
waveform 조작은 display media에 영구적인 영향을 줄 가능성이 있으므로 주의해야 합니다.
사용자 공간 firmware 전달과 board I/O가 결합됩니다.
Metronomefb is platform independent and depends on a board specific driver
to do all physical IO work. Currently, an example is implemented for the
PXA board used in the AM-200 EPD devkit. This example is am200epd.c
Metronomefb requires waveform information which is delivered via the AMLCD
interface to the metronome controller. The waveform information is expected to
be delivered from userspace via the firmware class interface. The waveform file
can be compressed as long as your udev or hotplug script is aware of the need
to uncompress it before delivering it. metronomefb will ask for metronome.wbf
which would typically go into /lib/firmware/metronome.wbf depending on your
udev/hotplug setup. I have only tested with a single waveform file which was
originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
Caution should be exercised when manipulating the waveform as there may be
a possibility that it could have some permanent effects on the display media.
I neither have access to nor know exactly what the waveform does in terms of
the physical media.deferred I/O와 Xfbdev 시험
35-38`Metronomefb`는 memory-mappable framebuffer를 제공하기 위해 deferred I/O interface를 사용합니다.
`tinyx`의 `Xfbdev`로 시험했으며 당시 `xeyes`, `xclock`, `xloadimage`, `xpdf`가 동작하는 것으로 알려졌습니다.
Metronomefb uses the deferred IO interface so that it can provide a memory
mappable frame buffer. It has been tested with tinyx (Xfbdev). It is known
to work at this time with xeyes, xclock, xloadimage, xpdf.
요약·해설
metronomefb.rst:1-38Metronomefb는 board driver, AMLCD interface와 firmware class를 결합해 E-Ink Vizplex media를 구동하며 deferred I/O로 mmap 가능한 framebuffer를 제공합니다.
firmware waveform과 image가 별도 경로에서 controller에 모입니다.