← Documents Documentation/networking/device_drivers/wifi/intel/ipw2200.rst GitHub 원문 ↗

Linux 6.18.37 · Networking

Intel PRO/Wireless 2915ABG/2200BG Driver

통합 IPW2200 드라이버의 B/G/A mode, private wireless method, sysfs와 RF kill, regulatory channel, Ad-Hoc 구성 및 firmware 설치를 설명합니다.

Source pathDocumentation/networking/device_drivers/wifi/intel/ipw2200.rst
Source versionLinux v6.18.37
TranslationDUJINLABS 전문 번역 + 해설

요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.

1. 요약·해설

원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.

요약·해설

ipw2200.rst:1-526

IPW2200은 2200BG와 2915ABG를 함께 지원하는 통합 드라이버입니다. 장치별 IEEE mode와 geography code를 구분하고, mode 변경이 channel·rate·ESSID 같은 runtime 설정을 초기화한다는 점을 특히 주의해야 합니다.

IPW2200 장치 차이
장치지원 mode
2200BG802.11b, 802.11g, 802.11bg
2915ABG802.11a/b/g 및 조합 mode

2200BG와 2915ABG가 지원하는 radio mode 범위입니다.

IPW2200 구성 흐름
geography code 감지허용 802.11 channel 결정IEEE mode 설정ESSID·channel 설정association 또는 Ad-Hoc 생성

regulatory domain과 interface 설정이 실제 channel 동작을 결정합니다.

2. 영어 원문 전체

번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.

원문 전체 펼치기
1 .. SPDX-License-Identifier: GPL-2.0
2 .. include:: <isonum.txt>
3
4 ==============================================
5 Intel(R) PRO/Wireless 2915ABG Driver for Linux
6 ==============================================
7
8
9 Support for:
10
11 - Intel(R) PRO/Wireless 2200BG Network Connection
12 - Intel(R) PRO/Wireless 2915ABG Network Connection
13
14 Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R)
15 PRO/Wireless 2200BG Driver for Linux is a unified driver that works on
16 both hardware adapters listed above. In this document the Intel(R)
17 PRO/Wireless 2915ABG Driver for Linux will be used to reference the
18 unified driver.
19
20 Copyright |copy| 2004-2006, Intel Corporation
21
22 README.ipw2200
23
24 :Version: 1.1.2
25 :Date: March 30, 2006
26
27
28 .. Index
29
30 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
31 1. Introduction
32 1.1. Overview of features
33 1.2. Module parameters
34 1.3. Wireless Extension Private Methods
35 1.4. Sysfs Helper Files
36 1.5. Supported channels
37 2. Ad-Hoc Networking
38 3. Interacting with Wireless Tools
39 3.1. iwconfig mode
40 3.2. iwconfig sens
41 4. About the Version Numbers
42 5. Firmware installation
43 6. Support
44 7. License
45
46
47 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
48 =================================================
49
50 Important Notice FOR ALL USERS OR DISTRIBUTORS!!!!
51
52 Intel wireless LAN adapters are engineered, manufactured, tested, and
53 quality checked to ensure that they meet all necessary local and
54 governmental regulatory agency requirements for the regions that they
55 are designated and/or marked to ship into. Since wireless LANs are
56 generally unlicensed devices that share spectrum with radars,
57 satellites, and other licensed and unlicensed devices, it is sometimes
58 necessary to dynamically detect, avoid, and limit usage to avoid
59 interference with these devices. In many instances Intel is required to
60 provide test data to prove regional and local compliance to regional and
61 governmental regulations before certification or approval to use the
62 product is granted. Intel's wireless LAN's EEPROM, firmware, and
63 software driver are designed to carefully control parameters that affect
64 radio operation and to ensure electromagnetic compliance (EMC). These
65 parameters include, without limitation, RF power, spectrum usage,
66 channel scanning, and human exposure.
67
68 For these reasons Intel cannot permit any manipulation by third parties
69 of the software provided in binary format with the wireless WLAN
70 adapters (e.g., the EEPROM and firmware). Furthermore, if you use any
71 patches, utilities, or code with the Intel wireless LAN adapters that
72 have been manipulated by an unauthorized party (i.e., patches,
73 utilities, or code (including open source code modifications) which have
74 not been validated by Intel), (i) you will be solely responsible for
75 ensuring the regulatory compliance of the products, (ii) Intel will bear
76 no liability, under any theory of liability for any issues associated
77 with the modified products, including without limitation, claims under
78 the warranty and/or issues arising from regulatory non-compliance, and
79 (iii) Intel will not provide or be required to assist in providing
80 support to any third parties for such modified products.
81
82 Note: Many regulatory agencies consider Wireless LAN adapters to be
83 modules, and accordingly, condition system-level regulatory approval
84 upon receipt and review of test data documenting that the antennas and
85 system configuration do not cause the EMC and radio operation to be
86 non-compliant.
87
88 The drivers available for download from SourceForge are provided as a
89 part of a development project. Conformance to local regulatory
90 requirements is the responsibility of the individual developer. As
91 such, if you are interested in deploying or shipping a driver as part of
92 solution intended to be used for purposes other than development, please
93 obtain a tested driver from Intel Customer Support at:
94
95 http://support.intel.com
96
97
98 1. Introduction
99 ===============
100
101 The following sections attempt to provide a brief introduction to using
102 the Intel(R) PRO/Wireless 2915ABG Driver for Linux.
103
104 This document is not meant to be a comprehensive manual on
105 understanding or using wireless technologies, but should be sufficient
106 to get you moving without wires on Linux.
107
108 For information on building and installing the driver, see the INSTALL
109 file.
110
111
112 1.1. Overview of Features
113 -------------------------
114 The current release (1.1.2) supports the following features:
115
116 + BSS mode (Infrastructure, Managed)
117 + IBSS mode (Ad-Hoc)
118 + WEP (OPEN and SHARED KEY mode)
119 + 802.1x EAP via wpa_supplicant and xsupplicant
120 + Wireless Extension support
121 + Full B and G rate support (2200 and 2915)
122 + Full A rate support (2915 only)
123 + Transmit power control
124 + S state support (ACPI suspend/resume)
125
126 The following features are currently enabled, but not officially
127 supported:
128
129 + WPA
130 + long/short preamble support
131 + Monitor mode (aka RFMon)
132
133 The distinction between officially supported and enabled is a reflection
134 on the amount of validation and interoperability testing that has been
135 performed on a given feature.
136
137
138
139 1.2. Command Line Parameters
140 ----------------------------
141
142 Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless
143 2915ABG Driver for Linux allows configuration options to be provided
144 as module parameters. The most common way to specify a module parameter
145 is via the command line.
146
147 The general form is::
148
149 % modprobe ipw2200 parameter=value
150
151 Where the supported parameter are:
152
153 associate
154 Set to 0 to disable the auto scan-and-associate functionality of the
155 driver. If disabled, the driver will not attempt to scan
156 for and associate to a network until it has been configured with
157 one or more properties for the target network, for example configuring
158 the network SSID. Default is 0 (do not auto-associate)
159
160 Example: % modprobe ipw2200 associate=0
161
162 auto_create
163 Set to 0 to disable the auto creation of an Ad-Hoc network
164 matching the channel and network name parameters provided.
165 Default is 1.
166
167 channel
168 channel number for association. The normal method for setting
169 the channel would be to use the standard wireless tools
170 (i.e. `iwconfig eth1 channel 10`), but it is useful sometimes
171 to set this while debugging. Channel 0 means 'ANY'
172
173 debug
174 If using a debug build, this is used to control the amount of debug
175 info is logged. See the 'dvals' and 'load' script for more info on
176 how to use this (the dvals and load scripts are provided as part
177 of the ipw2200 development snapshot releases available from the
178 SourceForge project at http://ipw2200.sf.net)
179
180 led
181 Can be used to turn on experimental LED code.
182 0 = Off, 1 = On. Default is 1.
183
184 mode
185 Can be used to set the default mode of the adapter.
186 0 = Managed, 1 = Ad-Hoc, 2 = Monitor
187
188
189 1.3. Wireless Extension Private Methods
190 ---------------------------------------
191
192 As an interface designed to handle generic hardware, there are certain
193 capabilities not exposed through the normal Wireless Tool interface. As
194 such, a provision is provided for a driver to declare custom, or
195 private, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux
196 defines several of these to configure various settings.
197
198 The general form of using the private wireless methods is::
199
200 % iwpriv $IFNAME method parameters
201
202 Where $IFNAME is the interface name the device is registered with
203 (typically eth1, customized via one of the various network interface
204 name managers, such as ifrename)
205
206 The supported private methods are:
207
208 get_mode
209 Can be used to report out which IEEE mode the driver is
210 configured to support. Example:
211
212 % iwpriv eth1 get_mode
213 eth1 get_mode:802.11bg (6)
214
215 set_mode
216 Can be used to configure which IEEE mode the driver will
217 support.
218
219 Usage::
220
221 % iwpriv eth1 set_mode {mode}
222
223 Where {mode} is a number in the range 1-7:
224
225 == =====================
226 1 802.11a (2915 only)
227 2 802.11b
228 3 802.11ab (2915 only)
229 4 802.11g
230 5 802.11ag (2915 only)
231 6 802.11bg
232 7 802.11abg (2915 only)
233 == =====================
234
235 get_preamble
236 Can be used to report configuration of preamble length.
237
238 set_preamble
239 Can be used to set the configuration of preamble length:
240
241 Usage::
242
243 % iwpriv eth1 set_preamble {mode}
244
245 Where {mode} is one of:
246
247 == ========================================
248 1 Long preamble only
249 0 Auto (long or short based on connection)
250 == ========================================
251
252
253 1.4. Sysfs Helper Files
254 -----------------------
255
256 The Linux kernel provides a pseudo file system that can be used to
257 access various components of the operating system. The Intel(R)
258 PRO/Wireless 2915ABG Driver for Linux exposes several configuration
259 parameters through this mechanism.
260
261 An entry in the sysfs can support reading and/or writing. You can
262 typically query the contents of a sysfs entry through the use of cat,
263 and can set the contents via echo. For example::
264
265 % cat /sys/bus/pci/drivers/ipw2200/debug_level
266
267 Will report the current debug level of the driver's logging subsystem
268 (only available if CONFIG_IPW2200_DEBUG was configured when the driver
269 was built).
270
271 You can set the debug level via::
272
273 % echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level
274
275 Where $VALUE would be a number in the case of this sysfs entry. The
276 input to sysfs files does not have to be a number. For example, the
277 firmware loader used by hotplug utilizes sysfs entries for transferring
278 the firmware image from user space into the driver.
279
280 The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries
281 at two levels -- driver level, which apply to all instances of the driver
282 (in the event that there are more than one device installed) and device
283 level, which applies only to the single specific instance.
284
285
286 1.4.1 Driver Level Sysfs Helper Files
287 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
288
289 For the driver level files, look in /sys/bus/pci/drivers/ipw2200/
290
291 debug_level
292 This controls the same global as the 'debug' module parameter
293
294
295
296 1.4.2 Device Level Sysfs Helper Files
297 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
298
299 For the device level files, look in::
300
301 /sys/bus/pci/drivers/ipw2200/{PCI-ID}/
302
303 For example:::
304
305 /sys/bus/pci/drivers/ipw2200/0000:02:01.0
306
307 For the device level files, see /sys/bus/pci/drivers/ipw2200:
308
309 rf_kill
310 read -
311
312 == =========================================
313 0 RF kill not enabled (radio on)
314 1 SW based RF kill active (radio off)
315 2 HW based RF kill active (radio off)
316 3 Both HW and SW RF kill active (radio off)
317 == =========================================
318
319 write -
320
321 == ==================================================
322 0 If SW based RF kill active, turn the radio back on
323 1 If radio is on, activate SW based RF kill
324 == ==================================================
325
326 .. note::
327
328 If you enable the SW based RF kill and then toggle the HW
329 based RF kill from ON -> OFF -> ON, the radio will NOT come back on
330
331 ucode
332 read-only access to the ucode version number
333
334 led
335 read -
336
337 == =================
338 0 LED code disabled
339 1 LED code enabled
340 == =================
341
342 write -
343
344 == ================
345 0 Disable LED code
346 1 Enable LED code
347 == ================
348
349
350 .. note::
351
352 The LED code has been reported to hang some systems when
353 running ifconfig and is therefore disabled by default.
354
355
356 1.5. Supported channels
357 -----------------------
358
359 Upon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a
360 message stating the detected geography code and the number of 802.11
361 channels supported by the card will be displayed in the log.
362
363 The geography code corresponds to a regulatory domain as shown in the
364 table below.
365
366 +------+----------------------------+--------------------+
367 | | | Supported channels |
368 | Code | Geography +----------+---------+
369 | | | 802.11bg | 802.11a |
370 +======+============================+==========+=========+
371 | --- | Restricted | 11 | 0 |
372 +------+----------------------------+----------+---------+
373 | ZZF | Custom US/Canada | 11 | 8 |
374 +------+----------------------------+----------+---------+
375 | ZZD | Rest of World | 13 | 0 |
376 +------+----------------------------+----------+---------+
377 | ZZA | Custom USA & Europe & High | 11 | 13 |
378 +------+----------------------------+----------+---------+
379 | ZZB | Custom NA & Europe | 11 | 13 |
380 +------+----------------------------+----------+---------+
381 | ZZC | Custom Japan | 11 | 4 |
382 +------+----------------------------+----------+---------+
383 | ZZM | Custom | 11 | 0 |
384 +------+----------------------------+----------+---------+
385 | ZZE | Europe | 13 | 19 |
386 +------+----------------------------+----------+---------+
387 | ZZJ | Custom Japan | 14 | 4 |
388 +------+----------------------------+----------+---------+
389 | ZZR | Rest of World | 14 | 0 |
390 +------+----------------------------+----------+---------+
391 | ZZH | High Band | 13 | 4 |
392 +------+----------------------------+----------+---------+
393 | ZZG | Custom Europe | 13 | 4 |
394 +------+----------------------------+----------+---------+
395 | ZZK | Europe | 13 | 24 |
396 +------+----------------------------+----------+---------+
397 | ZZL | Europe | 11 | 13 |
398 +------+----------------------------+----------+---------+
399
400 2. Ad-Hoc Networking
401 =====================
402
403 When using a device in an Ad-Hoc network, it is useful to understand the
404 sequence and requirements for the driver to be able to create, join, or
405 merge networks.
406
407 The following attempts to provide enough information so that you can
408 have a consistent experience while using the driver as a member of an
409 Ad-Hoc network.
410
411 2.1. Joining an Ad-Hoc Network
412 ------------------------------
413
414 The easiest way to get onto an Ad-Hoc network is to join one that
415 already exists.
416
417 2.2. Creating an Ad-Hoc Network
418 -------------------------------
419
420 An Ad-Hoc networks is created using the syntax of the Wireless tool.
421
422 For Example:
423 iwconfig eth1 mode ad-hoc essid testing channel 2
424
425 2.3. Merging Ad-Hoc Networks
426 ----------------------------
427
428
429 3. Interaction with Wireless Tools
430 ==================================
431
432 3.1 iwconfig mode
433 -----------------
434
435 When configuring the mode of the adapter, all run-time configured parameters
436 are reset to the value used when the module was loaded. This includes
437 channels, rates, ESSID, etc.
438
439 3.2 iwconfig sens
440 -----------------
441
442 The 'iwconfig ethX sens XX' command will not set the signal sensitivity
443 threshold, as described in iwconfig documentation, but rather the number
444 of consecutive missed beacons that will trigger handover, i.e. roaming
445 to another access point. At the same time, it will set the disassociation
446 threshold to 3 times the given value.
447
448
449 4. About the Version Numbers
450 =============================
451
452 Due to the nature of open source development projects, there are
453 frequently changes being incorporated that have not gone through
454 a complete validation process. These changes are incorporated into
455 development snapshot releases.
456
457 Releases are numbered with a three level scheme:
458
459 major.minor.development
460
461 Any version where the 'development' portion is 0 (for example
462 1.0.0, 1.1.0, etc.) indicates a stable version that will be made
463 available for kernel inclusion.
464
465 Any version where the 'development' portion is not a 0 (for
466 example 1.0.1, 1.1.5, etc.) indicates a development version that is
467 being made available for testing and cutting edge users. The stability
468 and functionality of the development releases are not know. We make
469 efforts to try and keep all snapshots reasonably stable, but due to the
470 frequency of their release, and the desire to get those releases
471 available as quickly as possible, unknown anomalies should be expected.
472
473 The major version number will be incremented when significant changes
474 are made to the driver. Currently, there are no major changes planned.
475
476 5. Firmware installation
477 ========================
478
479 The driver requires a firmware image, download it and extract the
480 files under /lib/firmware (or wherever your hotplug's firmware.agent
481 will look for firmware files)
482
483 The firmware can be downloaded from the following URL:
484
485 http://ipw2200.sf.net/
486
487
488 6. Support
489 ==========
490
491 For direct support of the 1.0.0 version, you can contact
492 http://supportmail.intel.com, or you can use the open source project
493 support.
494
495 For general information and support, go to:
496
497 http://ipw2200.sf.net/
498
499
500 7. License
501 ==========
502
503 Copyright |copy| 2003 - 2006 Intel Corporation. All rights reserved.
504
505 This program is free software; you can redistribute it and/or modify it
506 under the terms of the GNU General Public License version 2 as
507 published by the Free Software Foundation.
508
509 This program is distributed in the hope that it will be useful, but WITHOUT
510 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
511 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
512 more details.
513
514 You should have received a copy of the GNU General Public License along with
515 this program; if not, write to the Free Software Foundation, Inc., 59
516 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
517
518 The full GNU General Public License is included in this distribution in the
519 file called LICENSE.
520
521 Contact Information:
522
523 James P. Ketrenos <[email protected]>
524
525 Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497
526
527

3. 한국어 전문 번역

영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.

IPW2200 문서 정보와 목차

1-46

이 문서는 `GPL-2.0` 라이선스를 따릅니다.

Linux용 Intel(R) PRO/Wireless 2915ABG 드라이버

지원 장치는 Intel(R) PRO/Wireless 2200BG Network Connection과 Intel(R) PRO/Wireless 2915ABG Network Connection입니다.

Linux용 2915ABG와 2200BG 드라이버는 두 adapter 모두에서 동작하는 통합 드라이버입니다. 이 문서에서는 통합 드라이버를 2915ABG 드라이버라고 부릅니다.

Copyright 2004-2006 Intel Corporation.

`README.ipw2200`, 버전 1.1.2, 2006년 3월 30일.

목차는 중요 규제 정보, 소개와 기능, module parameter, private wireless method, sysfs helper, 지원 channel, Ad-Hoc networking, Wireless Tools 상호 작용, version 번호, firmware 설치, 지원, 라이선스를 다룹니다.

.. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>

==============================================
Intel(R) PRO/Wireless 2915ABG Driver for Linux
==============================================


Support for:

- Intel(R) PRO/Wireless 2200BG Network Connection
- Intel(R) PRO/Wireless 2915ABG Network Connection

Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R)
PRO/Wireless 2200BG Driver for Linux is a unified driver that works on
both hardware adapters listed above. In this document the Intel(R)
PRO/Wireless 2915ABG Driver for Linux will be used to reference the
unified driver.

Copyright |copy| 2004-2006, Intel Corporation

README.ipw2200

:Version: 1.1.2
:Date: March 30, 2006


.. Index

    0.   IMPORTANT INFORMATION BEFORE USING THIS DRIVER
    1.   Introduction
    1.1. Overview of features
    1.2. Module parameters
    1.3. Wireless Extension Private Methods
    1.4. Sysfs Helper Files
    1.5. Supported channels
    2.   Ad-Hoc Networking
    3.   Interacting with Wireless Tools
    3.1. iwconfig mode
    3.2. iwconfig sens
    4.   About the Version Numbers
    5.   Firmware installation
    6.   Support
    7.   License

규제 준수에 관한 중요 고지

47-97

0. 이 드라이버 사용 전 중요 정보

모든 사용자와 배포자를 위한 중요 고지입니다.

Intel wireless LAN adapter는 출하 대상 지역의 지방 및 정부 규제 요구 사항을 만족하도록 설계, 제조, 시험, 품질 검사됩니다.

wireless LAN은 radar, satellite, 기타 허가·비허가 장치와 spectrum을 공유하는 비허가 장치인 경우가 많습니다. 간섭 방지를 위해 사용 환경을 동적으로 감지하고 회피하며 사용을 제한해야 할 수 있습니다.

제품 인증·승인 전에 Intel이 지역 규제 준수를 입증하는 시험 데이터를 제공해야 하는 경우가 많습니다.

EEPROM, firmware, software driver는 RF power, spectrum 사용, channel scanning, 인체 노출 같은 radio parameter를 세밀하게 제어하고 EMC를 보장하도록 설계되었습니다.

Intel은 adapter와 함께 binary로 제공하는 EEPROM과 firmware를 제3자가 조작하는 것을 허용할 수 없다고 설명합니다.

Intel이 검증하지 않은 patch, utility, code 또는 open source 수정본을 사용하면 제품의 규제 준수 책임은 사용자에게 있습니다.

Intel은 보증 청구나 규제 미준수를 포함해 수정 제품과 관련된 문제에 책임을 지지 않으며, 해당 제품에 대한 제3자 지원을 제공하거나 지원할 의무도 없다고 고지합니다.

많은 규제 기관은 wireless LAN adapter를 module로 간주하므로 antenna와 system 구성이 EMC 및 radio 규정을 위반하지 않는다는 시험 자료를 검토한 뒤 system-level 승인을 내릴 수 있습니다.

SourceForge에서 내려받는 드라이버는 개발 프로젝트 일부이며 지방 규제 준수는 개별 개발자의 책임입니다.

개발 이외의 목적으로 배포하거나 제품에 포함하려면 원문은 `http://support.intel.com`에서 시험된 드라이버를 구하라고 안내합니다. 현재 유효성은 별도로 확인해야 합니다.

IPW2200 규제 대상 parameter
범주통제 대상
출력RF power
주파수spectrum 사용과 channel scanning
안전인체 노출
적합성EMC와 지역별 인증 조건

EEPROM·firmware·driver가 함께 통제하는 대표 항목입니다.

0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
=================================================

Important Notice FOR ALL USERS OR DISTRIBUTORS!!!!

Intel wireless LAN adapters are engineered, manufactured, tested, and
quality checked to ensure that they meet all necessary local and
governmental regulatory agency requirements for the regions that they
are designated and/or marked to ship into. Since wireless LANs are
generally unlicensed devices that share spectrum with radars,
satellites, and other licensed and unlicensed devices, it is sometimes
necessary to dynamically detect, avoid, and limit usage to avoid
interference with these devices. In many instances Intel is required to
provide test data to prove regional and local compliance to regional and
governmental regulations before certification or approval to use the
product is granted. Intel's wireless LAN's EEPROM, firmware, and
software driver are designed to carefully control parameters that affect
radio operation and to ensure electromagnetic compliance (EMC). These
parameters include, without limitation, RF power, spectrum usage,
channel scanning, and human exposure.

For these reasons Intel cannot permit any manipulation by third parties
of the software provided in binary format with the wireless WLAN
adapters (e.g., the EEPROM and firmware). Furthermore, if you use any
patches, utilities, or code with the Intel wireless LAN adapters that
have been manipulated by an unauthorized party (i.e., patches,
utilities, or code (including open source code modifications) which have
not been validated by Intel), (i) you will be solely responsible for
ensuring the regulatory compliance of the products, (ii) Intel will bear
no liability, under any theory of liability for any issues associated
with the modified products, including without limitation, claims under
the warranty and/or issues arising from regulatory non-compliance, and
(iii) Intel will not provide or be required to assist in providing
support to any third parties for such modified products.

Note: Many regulatory agencies consider Wireless LAN adapters to be
modules, and accordingly, condition system-level regulatory approval
upon receipt and review of test data documenting that the antennas and
system configuration do not cause the EMC and radio operation to be
non-compliant.

The drivers available for download from SourceForge are provided as a
part of a development project.  Conformance to local regulatory
requirements is the responsibility of the individual developer.  As
such, if you are interested in deploying or shipping a driver as part of
solution intended to be used for purposes other than development, please
obtain a tested driver from Intel Customer Support at:

http://support.intel.com

소개와 기능 개요

98-138

1. 소개

다음 절은 Linux용 Intel(R) PRO/Wireless 2915ABG 드라이버 사용법을 간단히 소개합니다.

wireless 기술의 종합 설명서가 아니라 Linux에서 무선 연결을 시작하는 데 충분한 내용을 목표로 합니다. 빌드와 설치는 `INSTALL` 파일을 참조하십시오.

1.1 기능 개요

IPW2200 1.1.2 기능 상태
상태기능
지원BSS/Managed, IBSS/Ad-Hoc, WEP OPEN/SHARED KEY, 802.1x EAP, Wireless Extension
지원2200·2915의 B/G rate, 2915의 A rate, transmit power control, ACPI suspend/resume
활성화되었으나 미지원WPA, long/short preamble, Monitor/RFMon

공식 지원과 단순 활성화 기능을 validation 범위에 따라 구분합니다.

802.1x EAP는 `wpa_supplicant`와 `xsupplicant`를 통해 지원합니다. 공식 지원과 활성화 기능의 차이는 validation과 interoperability 시험의 양을 반영합니다.

1. Introduction
===============

The following sections attempt to provide a brief introduction to using
the Intel(R) PRO/Wireless 2915ABG Driver for Linux.

This document is not meant to be a comprehensive manual on
understanding or using wireless technologies, but should be sufficient
to get you moving without wires on Linux.

For information on building and installing the driver, see the INSTALL
file.


1.1. Overview of Features
-------------------------
The current release (1.1.2) supports the following features:

+ BSS mode (Infrastructure, Managed)
+ IBSS mode (Ad-Hoc)
+ WEP (OPEN and SHARED KEY mode)
+ 802.1x EAP via wpa_supplicant and xsupplicant
+ Wireless Extension support
+ Full B and G rate support (2200 and 2915)
+ Full A rate support (2915 only)
+ Transmit power control
+ S state support (ACPI suspend/resume)

The following features are currently enabled, but not officially
supported:

+ WPA
+ long/short preamble support
+ Monitor mode (aka RFMon)

The distinction between officially supported and enabled is a reflection
on the amount of validation and interoperability testing that has been
performed on a given feature.


명령줄 module parameter

139-188

1.2 명령줄 parameter

다른 Linux 커널 module처럼 2915ABG 통합 드라이버도 module parameter로 option을 받을 수 있습니다. 일반 형식은 다음과 같습니다.

% modprobe ipw2200 parameter=value
IPW2200 module parameter
parameter값/기본값효과
`associate`기본 00이면 자동 scan·association 비활성; target SSID 같은 속성을 설정할 때까지 연결하지 않음
`auto_create`기본 10이면 지정 channel·network name과 일치하는 Ad-Hoc network 자동 생성 비활성
`channel`0은 ANYassociation channel; 보통 `iwconfig eth1 channel 10` 사용
`debug`debug buildlog 양 제어; `dvals`, `load` script 참조
`led`0=off, 1=on, 기본 1실험적 LED code 제어
`mode`0=Managed, 1=Ad-Hoc, 2=Monitoradapter 기본 mode 설정

각 parameter의 기본 동작과 용도입니다.

`associate=0` 예는 `% modprobe ipw2200 associate=0`입니다. 자동 연결을 끄면 target network의 SSID 같은 속성을 하나 이상 설정할 때까지 scan과 association을 시도하지 않습니다.

`channel`은 보통 standard wireless tools로 설정하지만 debugging 중 module 적재 시 지정하면 유용할 수 있습니다.

`debug` 사용법은 당시 `http://ipw2200.sf.net`의 development snapshot에 포함된 `dvals`와 `load` script를 참조합니다.

1.2. Command Line Parameters
----------------------------

Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless
2915ABG Driver for Linux allows configuration options to be provided
as module parameters.  The most common way to specify a module parameter
is via the command line.

The general form is::

    % modprobe ipw2200 parameter=value

Where the supported parameter are:

  associate
        Set to 0 to disable the auto scan-and-associate functionality of the
        driver.  If disabled, the driver will not attempt to scan
        for and associate to a network until it has been configured with
        one or more properties for the target network, for example configuring
        the network SSID.  Default is 0 (do not auto-associate)

        Example: % modprobe ipw2200 associate=0

  auto_create
        Set to 0 to disable the auto creation of an Ad-Hoc network
        matching the channel and network name parameters provided.
        Default is 1.

  channel
        channel number for association.  The normal method for setting
        the channel would be to use the standard wireless tools
        (i.e. `iwconfig eth1 channel 10`), but it is useful sometimes
        to set this while debugging.  Channel 0 means 'ANY'

  debug
        If using a debug build, this is used to control the amount of debug
        info is logged.  See the 'dvals' and 'load' script for more info on
        how to use this (the dvals and load scripts are provided as part
        of the ipw2200 development snapshot releases available from the
        SourceForge project at http://ipw2200.sf.net)

  led
        Can be used to turn on experimental LED code.
        0 = Off, 1 = On.  Default is 1.

  mode
        Can be used to set the default mode of the adapter.
        0 = Managed, 1 = Ad-Hoc, 2 = Monitor

Wireless Extension private method

189-252

1.3 Wireless Extension private method

일반 hardware를 다루도록 설계된 Wireless Tool interface가 모든 기능을 노출하지는 못합니다. 그래서 드라이버가 custom/private method를 선언할 수 있습니다.

2915ABG 통합 드라이버는 여러 설정을 위한 private method를 정의합니다. 일반 형식은 다음과 같습니다.

% iwpriv $IFNAME method parameters

`$IFNAME`은 장치가 등록된 interface 이름이며 보통 `eth1`입니다. `ifrename` 같은 network interface name manager로 바꿀 수 있습니다.

`get_mode`는 드라이버가 지원하도록 설정된 IEEE mode를 보고합니다.

% iwpriv eth1 get_mode
eth1    get_mode:802.11bg (6)

`set_mode`는 드라이버가 지원할 IEEE mode를 설정합니다. 형식은 `% iwpriv eth1 set_mode {mode}`이며 `{mode}`는 1~7입니다.

IPW2200 IEEE mode 값
mode장치 제약
1802.11a2915만
2802.11b2200·2915
3802.11ab2915만
4802.11g2200·2915
5802.11ag2915만
6802.11bg2200·2915
7802.11abg2915만

2915 전용 조합과 공통 B/G 조합을 구분합니다.

`get_preamble`은 preamble length 설정을 보고합니다. `set_preamble`은 `% iwpriv eth1 set_preamble {mode}` 형식으로 길이 설정을 바꿉니다.

IPW2200 preamble mode
동작
1long preamble만 사용
0연결에 따라 long 또는 short 자동 선택

long preamble 고정과 연결별 자동 선택입니다.

1.3. Wireless Extension Private Methods
---------------------------------------

As an interface designed to handle generic hardware, there are certain
capabilities not exposed through the normal Wireless Tool interface.  As
such, a provision is provided for a driver to declare custom, or
private, methods.  The Intel(R) PRO/Wireless 2915ABG Driver for Linux
defines several of these to configure various settings.

The general form of using the private wireless methods is::

        % iwpriv $IFNAME method parameters

Where $IFNAME is the interface name the device is registered with
(typically eth1, customized via one of the various network interface
name managers, such as ifrename)

The supported private methods are:

  get_mode
        Can be used to report out which IEEE mode the driver is
        configured to support.  Example:

        % iwpriv eth1 get_mode
        eth1        get_mode:802.11bg (6)

  set_mode
        Can be used to configure which IEEE mode the driver will
        support.

        Usage::

            % iwpriv eth1 set_mode {mode}

        Where {mode} is a number in the range 1-7:

        ==        =====================
        1        802.11a (2915 only)
        2        802.11b
        3        802.11ab (2915 only)
        4        802.11g
        5        802.11ag (2915 only)
        6        802.11bg
        7        802.11abg (2915 only)
        ==        =====================

  get_preamble
        Can be used to report configuration of preamble length.

  set_preamble
        Can be used to set the configuration of preamble length:

        Usage::

            % iwpriv eth1 set_preamble {mode}

        Where {mode} is one of:

        ==        ========================================
        1        Long preamble only
        0        Auto (long or short based on connection)
        ==        ========================================

Sysfs helper file

253-355

1.4 Sysfs helper file

Linux 커널의 pseudo filesystem인 sysfs로 운영 체제 구성 요소에 접근할 수 있습니다. 2915ABG 통합 드라이버도 여러 설정 parameter를 이 방식으로 노출합니다.

sysfs entry는 읽기와 쓰기 중 하나 또는 둘 다 지원할 수 있습니다. 보통 `cat`으로 조회하고 `echo`로 값을 씁니다.

% cat /sys/bus/pci/drivers/ipw2200/debug_level
% echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level

첫 명령은 driver logging subsystem의 현재 debug level을 보고합니다. 드라이버를 빌드할 때 `CONFIG_IPW2200_DEBUG`를 설정한 경우에만 사용할 수 있습니다.

두 번째 명령은 debug level을 설정합니다. sysfs 입력은 반드시 숫자일 필요가 없습니다. 예를 들어 hotplug가 쓰는 firmware loader는 sysfs entry를 통해 user space의 firmware image를 드라이버로 전송합니다.

sysfs entry는 설치된 모든 장치에 적용하는 driver level과 특정 장치 하나에만 적용하는 device level 두 계층으로 제공됩니다.

driver-level file은 `/sys/bus/pci/drivers/ipw2200/`에 있습니다. `debug_level`은 `debug` module parameter와 같은 global 값을 제어합니다.

device-level file은 `/sys/bus/pci/drivers/ipw2200/{PCI-ID}/`에 있습니다. 예: `/sys/bus/pci/drivers/ipw2200/0000:02:01.0`.

IPW2200 device sysfs entry
entry동작값과 의미
`rf_kill`읽기0=off 아님, 1=SW kill, 2=HW kill, 3=둘 다
`rf_kill`쓰기0=SW kill 해제, 1=SW kill 활성화
`ucode`읽기 전용ucode version number
`led`읽기0=LED code 비활성, 1=활성
`led`쓰기0=LED code 끄기, 1=켜기

`rf_kill`, `ucode`, `led`의 읽기·쓰기 동작입니다.

software RF kill을 활성화한 뒤 hardware RF kill을 ON → OFF → ON으로 전환해도 radio는 다시 켜지지 않습니다.

LED code는 `ifconfig` 실행 시 일부 system을 멈추게 한다는 보고가 있어 기본적으로 비활성화됩니다.

1.4. Sysfs Helper Files
-----------------------

The Linux kernel provides a pseudo file system that can be used to
access various components of the operating system.  The Intel(R)
PRO/Wireless 2915ABG Driver for Linux exposes several configuration
parameters through this mechanism.

An entry in the sysfs can support reading and/or writing.  You can
typically query the contents of a sysfs entry through the use of cat,
and can set the contents via echo.  For example::

    % cat /sys/bus/pci/drivers/ipw2200/debug_level

Will report the current debug level of the driver's logging subsystem
(only available if CONFIG_IPW2200_DEBUG was configured when the driver
was built).

You can set the debug level via::

    % echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level

Where $VALUE would be a number in the case of this sysfs entry.  The
input to sysfs files does not have to be a number.  For example, the
firmware loader used by hotplug utilizes sysfs entries for transferring
the firmware image from user space into the driver.

The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries
at two levels -- driver level, which apply to all instances of the driver
(in the event that there are more than one device installed) and device
level, which applies only to the single specific instance.


1.4.1 Driver Level Sysfs Helper Files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For the driver level files, look in /sys/bus/pci/drivers/ipw2200/

  debug_level
        This controls the same global as the 'debug' module parameter



1.4.2 Device Level Sysfs Helper Files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For the device level files, look in::

        /sys/bus/pci/drivers/ipw2200/{PCI-ID}/

For example:::

        /sys/bus/pci/drivers/ipw2200/0000:02:01.0

For the device level files, see /sys/bus/pci/drivers/ipw2200:

  rf_kill
        read -

        ==  =========================================
        0   RF kill not enabled (radio on)
        1   SW based RF kill active (radio off)
        2   HW based RF kill active (radio off)
        3   Both HW and SW RF kill active (radio off)
        ==  =========================================

        write -

        ==  ==================================================
        0   If SW based RF kill active, turn the radio back on
        1   If radio is on, activate SW based RF kill
        ==  ==================================================

        .. note::

           If you enable the SW based RF kill and then toggle the HW
           based RF kill from ON -> OFF -> ON, the radio will NOT come back on

  ucode
        read-only access to the ucode version number

  led
        read -

        ==  =================
        0   LED code disabled
        1   LED code enabled
        ==  =================

        write -

        ==  ================
        0   Disable LED code
        1   Enable LED code
        ==  ================


        .. note::

           The LED code has been reported to hang some systems when
           running ifconfig and is therefore disabled by default.

지원 channel과 regulatory domain

356-399

1.5 지원 channel

2915ABG 통합 드라이버를 적재하면 감지한 geography code와 card가 지원하는 802.11 channel 수를 log에 표시합니다.

geography code는 아래 regulatory domain과 대응합니다.

IPW2200 geography code
code지역802.11bg802.11a
---Restricted110
ZZFCustom US/Canada118
ZZDRest of World130
ZZACustom USA & Europe & High1113
ZZBCustom NA & Europe1113
ZZCCustom Japan114
ZZMCustom110
ZZEEurope1319
ZZJCustom Japan144
ZZRRest of World140
ZZHHigh Band134
ZZGCustom Europe134
ZZKEurope1324
ZZLEurope1113

각 domain에서 지원하는 802.11bg와 802.11a channel 수입니다.

1.5. Supported channels
-----------------------

Upon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a
message stating the detected geography code and the number of 802.11
channels supported by the card will be displayed in the log.

The geography code corresponds to a regulatory domain as shown in the
table below.

        +------+----------------------------+--------------------+
        |      |                            | Supported channels |
        | Code |        Geography            +----------+---------+
        |      |                            | 802.11bg | 802.11a |
        +======+============================+==========+=========+
        | ---  | Restricted                     |  11      |   0     |
        +------+----------------------------+----------+---------+
        | ZZF  | Custom US/Canada             |  11      |   8     |
        +------+----------------------------+----------+---------+
        | ZZD  | Rest of World                     |  13      |   0     |
        +------+----------------------------+----------+---------+
        | ZZA  | Custom USA & Europe & High |  11      |  13     |
        +------+----------------------------+----------+---------+
        | ZZB  | Custom NA & Europe            |  11      |  13     |
        +------+----------------------------+----------+---------+
        | ZZC  | Custom Japan                     |  11      |   4     |
        +------+----------------------------+----------+---------+
        | ZZM  | Custom                      |  11      |   0     |
        +------+----------------------------+----------+---------+
        | ZZE  | Europe                     |  13      |  19     |
        +------+----------------------------+----------+---------+
        | ZZJ  | Custom Japan                     |  14      |   4     |
        +------+----------------------------+----------+---------+
        | ZZR  | Rest of World                    |  14      |   0     |
        +------+----------------------------+----------+---------+
        | ZZH  | High Band                    |  13      |   4     |
        +------+----------------------------+----------+---------+
        | ZZG  | Custom Europe                    |  13      |   4     |
        +------+----------------------------+----------+---------+
        | ZZK  | Europe                     |  13      |  24     |
        +------+----------------------------+----------+---------+
        | ZZL  | Europe                     |  11      |  13     |
        +------+----------------------------+----------+---------+

Ad-Hoc network와 Wireless Tools

400-448

2. Ad-Hoc networking

Ad-Hoc network에서 장치를 사용할 때 드라이버가 network를 생성, 참가, 병합하는 순서와 요구 사항을 이해하면 유용합니다.

이 절은 Ad-Hoc network 구성원으로 드라이버를 사용할 때 일관된 경험을 얻는 데 필요한 정보를 제공하려는 것입니다.

2.1 Ad-Hoc network 참가

Ad-Hoc network에 들어가는 가장 쉬운 방법은 이미 존재하는 network에 참가하는 것입니다.

2.2 Ad-Hoc network 생성

Ad-Hoc network는 Wireless tool 문법으로 생성합니다.

iwconfig eth1 mode ad-hoc essid testing channel 2

2.3 Ad-Hoc network 병합

원문은 이 제목만 제공하고 구체적인 병합 절차는 기록하지 않습니다.

IPW2200 Ad-Hoc 설정
`eth1` 선택`mode ad-hoc``essid testing``channel 2`기존 network 참가 또는 새 network 생성

mode, ESSID, channel을 한 명령에서 지정합니다.

3. Wireless Tools와 상호 작용

3.1 `iwconfig mode`

adapter mode를 설정하면 runtime에 설정한 모든 parameter가 module을 적재할 때 사용한 값으로 초기화됩니다. 여기에는 channel, rate, ESSID 등이 포함됩니다.

3.2 `iwconfig sens`

`iwconfig ethX sens XX`는 iwconfig 설명서에 적힌 signal sensitivity threshold를 설정하지 않습니다.

대신 handover, 즉 다른 access point로 roaming을 일으킬 연속 beacon miss 횟수를 설정합니다. 동시에 disassociation threshold를 지정 값의 세 배로 설정합니다.

IPW2200 `sens` 해석
항목이 드라이버의 동작
`sens XX`연속 beacon miss `XX`회에서 handover
disassociation`3 × XX`회에서 threshold 도달

표준 문서의 의미와 이 드라이버의 실제 의미가 다릅니다.

2.  Ad-Hoc Networking
=====================

When using a device in an Ad-Hoc network, it is useful to understand the
sequence and requirements for the driver to be able to create, join, or
merge networks.

The following attempts to provide enough information so that you can
have a consistent experience while using the driver as a member of an
Ad-Hoc network.

2.1. Joining an Ad-Hoc Network
------------------------------

The easiest way to get onto an Ad-Hoc network is to join one that
already exists.

2.2. Creating an Ad-Hoc Network
-------------------------------

An Ad-Hoc networks is created using the syntax of the Wireless tool.

For Example:
iwconfig eth1 mode ad-hoc essid testing channel 2

2.3. Merging Ad-Hoc Networks
----------------------------


3. Interaction with Wireless Tools
==================================

3.1 iwconfig mode
-----------------

When configuring the mode of the adapter, all run-time configured parameters
are reset to the value used when the module was loaded.  This includes
channels, rates, ESSID, etc.

3.2 iwconfig sens
-----------------

The 'iwconfig ethX sens XX' command will not set the signal sensitivity
threshold, as described in iwconfig documentation, but rather the number
of consecutive missed beacons that will trigger handover, i.e. roaming
to another access point. At the same time, it will set the disassociation
threshold to 3 times the given value.

Version 번호와 firmware 설치

449-487

4. Version 번호

open source 개발 프로젝트 특성상 완전한 validation을 거치지 않은 변경이 자주 통합되며, 이런 변경은 development snapshot release에 포함됩니다.

release 번호는 `major.minor.development`의 세 단계 형식입니다.

IPW2200 version 안정성
형식의미
`development = 0`1.0.0, 1.1.0커널 포함 대상으로 제공할 stable version
`development ≠ 0`1.0.1, 1.1.5시험·최신 기능 사용자를 위한 development version

`development` 자리 값으로 stable과 development release를 구분합니다.

development release의 안정성과 기능은 알려져 있지 않습니다. snapshot을 합리적으로 안정되게 유지하려고 하지만 release 빈도와 빠른 공개 목표 때문에 알려지지 않은 이상 동작을 예상해야 합니다.

드라이버에 큰 변경이 생기면 major version을 올립니다. 원문 작성 당시에는 계획된 major change가 없었습니다.

5. Firmware 설치

드라이버에는 firmware image가 필요합니다. 내려받은 뒤 `/lib/firmware` 또는 hotplug의 `firmware.agent`가 검색하는 위치에 파일을 추출하십시오.

원문은 firmware 다운로드 주소로 `http://ipw2200.sf.net/`을 안내합니다.

4.  About the Version Numbers
=============================

Due to the nature of open source development projects, there are
frequently changes being incorporated that have not gone through
a complete validation process.  These changes are incorporated into
development snapshot releases.

Releases are numbered with a three level scheme:

        major.minor.development

Any version where the 'development' portion is 0 (for example
1.0.0, 1.1.0, etc.) indicates a stable version that will be made
available for kernel inclusion.

Any version where the 'development' portion is not a 0 (for
example 1.0.1, 1.1.5, etc.) indicates a development version that is
being made available for testing and cutting edge users.  The stability
and functionality of the development releases are not know.  We make
efforts to try and keep all snapshots reasonably stable, but due to the
frequency of their release, and the desire to get those releases
available as quickly as possible, unknown anomalies should be expected.

The major version number will be incremented when significant changes
are made to the driver.  Currently, there are no major changes planned.

5. Firmware installation
========================

The driver requires a firmware image, download it and extract the
files under /lib/firmware (or wherever your hotplug's firmware.agent
will look for firmware files)

The firmware can be downloaded from the following URL:

    http://ipw2200.sf.net/

지원과 라이선스

488-526

6. 지원

version 1.0.0 직접 지원은 당시 `http://supportmail.intel.com`으로 문의하거나 open source project 지원을 사용할 수 있었습니다.

일반 정보와 지원은 `http://ipw2200.sf.net/`에서 제공되었습니다. 두 주소는 역사적 기록이므로 현재 유효성은 별도로 확인해야 합니다.

7. 라이선스

Copyright 2003-2006 Intel Corporation. All rights reserved.

이 프로그램은 Free Software Foundation이 공개한 GNU General Public License version 2의 조건에 따라 재배포하거나 수정할 수 있는 free software입니다.

이 프로그램은 유용하기를 바라며 배포하지만 어떠한 보증도 제공하지 않습니다. 상품성 또는 특정 목적 적합성에 대한 묵시적 보증도 없습니다. 자세한 내용은 GNU GPL을 참조하십시오.

GNU GPL 사본을 프로그램과 함께 받았어야 합니다. 받지 못했다면 원문에 기재된 Free Software Foundation 주소로 문의하십시오. 전체 라이선스는 배포판의 `LICENSE` 파일에 포함됩니다.

연락처: James P. Ketrenos `<[email protected]>`, Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497.

6. Support
==========

For direct support of the 1.0.0 version, you can contact
http://supportmail.intel.com, or you can use the open source project
support.

For general information and support, go to:

    http://ipw2200.sf.net/


7. License
==========

  Copyright |copy| 2003 - 2006 Intel Corporation. All rights reserved.

  This program is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License version 2 as
  published by the Free Software Foundation.

  This program is distributed in the hope that it will be useful, but WITHOUT
  ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
  more details.

  You should have received a copy of the GNU General Public License along with
  this program; if not, write to the Free Software Foundation, Inc., 59
  Temple Place - Suite 330, Boston, MA  02111-1307, USA.

  The full GNU General Public License is included in this distribution in the
  file called LICENSE.

  Contact Information:

  James P. Ketrenos <[email protected]>

  Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497