2 # Watchdog device configuration
8 bool "Watchdog Timer Support"
10 If you say Y here (and to one of the following options) and create a
11 character special file /dev/watchdog with major number 10 and minor
12 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13 subsequently opening the file and then failing to write to it for
14 longer than 1 minute will result in rebooting the machine. This
15 could be useful for a networked machine that needs to come back
16 on-line as fast as possible after a lock-up. There's both a watchdog
17 implementation entirely in software (which can sometimes fail to
18 reboot the machine) and a driver for hardware watchdog boards, which
19 are more robust and can also keep track of the temperature inside
20 your computer. For details, read <file:Documentation/watchdog/watchdog.txt>
23 The watchdog is usually used together with the watchdog daemon
24 which is available from
25 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
26 also monitor NFS connections and can reboot the machine when the process
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
35 The default watchdog behaviour (which you get if you say N here) is
36 to stop the timer if the process managing it closes the file
37 /dev/watchdog. It's always remotely possible that this process might
38 get killed. If you say Y here, the watchdog cannot be stopped once
42 # General Watchdog drivers
45 comment "Watchdog Device Drivers"
48 # Architecture Independent
51 tristate "Software watchdog"
54 A software monitoring watchdog. This will fail to reboot your system
55 from some situations that the hardware watchdog will recover
56 from. Equally it's a lot cheaper to install.
58 To compile this driver as a module, choose M here: the
59 module will be called softdog.
63 config AT91RM9200_WATCHDOG
64 tristate "AT91RM9200 watchdog"
65 depends on WATCHDOG && ARCH_AT91RM9200
67 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
68 system when the timeout is reached.
71 tristate "DC21285 watchdog"
72 depends on WATCHDOG && FOOTBRIDGE
74 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
75 here if you wish to use this. Alternatively say M to compile the
76 driver as a module, which will be called wdt285.
78 This driver does not work on all machines. In particular, early CATS
79 boards have hardware problems that will cause the machine to simply
80 lock up if the watchdog fires.
82 "If in doubt, leave it out" - say N.
85 tristate "Moxa ART CPU watchdog"
86 depends on ARCH_MOXART
88 Author : Jimmy_chen@moxa.com.tw
89 Watchdog timer embedded into moxart chips. This will
90 reboot your system when timeout is reached.
92 NOTE: once enabled, this timer cannot be disabled.
94 To compile this driver as a module, choose M here: the
95 module will be called em1240wdt.ko.
98 tristate "NetWinder WB83C977 watchdog"
99 depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
101 Say Y here to include support for the WB977 watchdog included in
102 NetWinder machines. Alternatively say M to compile the driver as
103 a module, which will be called wdt977.
105 Not sure? It's safe to say N.
107 config IXP2000_WATCHDOG
108 tristate "IXP2000 Watchdog"
109 depends on WATCHDOG && ARCH_IXP2000
111 Say Y here if to include support for the watchdog timer
112 in the Intel IXP2000(2400, 2800, 2850) network processors.
113 This driver can be built as a module by choosing M. The module
114 will be called ixp2000_wdt.
116 Say N if you are unsure.
118 config IXP4XX_WATCHDOG
119 tristate "IXP4xx Watchdog"
120 depends on WATCHDOG && ARCH_IXP4XX
122 Say Y here if to include support for the watchdog timer
123 in the Intel IXP4xx network processors. This driver can
124 be built as a module by choosing M. The module will
125 be called ixp4xx_wdt.
127 Note: The internal IXP4xx watchdog does a soft CPU reset
128 which doesn't reset any peripherals. There are circumstances
129 where the watchdog will fail to reset the board correctly
130 (e.g., if the boot ROM is in an unreadable state).
132 Say N if you are unsure.
134 config S3C2410_WATCHDOG
135 tristate "S3C2410 Watchdog"
136 depends on WATCHDOG && ARCH_S3C2410
138 Watchdog timer block in the Samsung S3C2410 chips. This will
139 reboot the system when the timer expires with the watchdog
142 The driver is limited by the speed of the system's PCLK
143 signal, so with reasonably fast systems (PCLK around 50-66MHz)
144 then watchdog intervals of over approximately 20seconds are
147 The driver can be built as a module by choosing M, and will
148 be called s3c2410_wdt
150 config SA1100_WATCHDOG
151 tristate "SA1100/PXA2xx watchdog"
152 depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
154 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
155 reboot your system when timeout is reached.
157 NOTE: once enabled, this timer cannot be disabled.
159 To compile this driver as a module, choose M here: the
160 module will be called sa1100_wdt.
162 config MPCORE_WATCHDOG
163 tristate "MPcore watchdog"
164 depends on WATCHDOG && ARM_MPCORE_PLATFORM && LOCAL_TIMERS
166 Watchdog timer embedded into the MPcore system.
168 To compile this driver as a module, choose M here: the
169 module will be called mpcore_wdt.
171 config EP93XX_WATCHDOG
172 tristate "EP93xx Watchdog"
173 depends on WATCHDOG && ARCH_EP93XX
175 Say Y here if to include support for the watchdog timer
176 embedded in the Cirrus Logic EP93xx family of devices.
178 To compile this driver as a module, choose M here: the
179 module will be called ep93xx_wdt.
182 tristate "OMAP Watchdog"
183 depends on WATCHDOG && (ARCH_OMAP16XX || ARCH_OMAP24XX)
185 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
186 enable the OMAP1610/OMAP1710 watchdog timer.
188 config PNX4008_WATCHDOG
189 tristate "PNX4008 Watchdog"
190 depends on WATCHDOG && ARCH_PNX4008
192 Say Y here if to include support for the watchdog timer
193 in the PNX4008 processor.
194 This driver can be built as a module by choosing M. The module
195 will be called pnx4008_wdt.
197 Say N if you are unsure.
199 # X86 (i386 + ia64 + x86_64) Architecture
202 tristate "Acquire SBC Watchdog Timer"
203 depends on WATCHDOG && X86
205 This is the driver for the hardware watchdog on Single Board
206 Computers produced by Acquire Inc (and others). This watchdog
207 simply watches your kernel to make sure it doesn't freeze, and if
208 it does, it reboots your computer after a certain amount of time.
210 To compile this driver as a module, choose M here: the
211 module will be called acquirewdt.
213 Most people will say N.
216 tristate "Advantech SBC Watchdog Timer"
217 depends on WATCHDOG && X86
219 If you are configuring a Linux kernel for the Advantech single-board
220 computer, say `Y' here to support its built-in watchdog timer
221 feature. More information can be found at
222 <http://www.advantech.com.tw/products/>
225 tristate "ALi M1535 PMU Watchdog Timer"
226 depends on WATCHDOG && X86 && PCI
228 This is the driver for the hardware watchdog on the ALi M1535 PMU.
230 To compile this driver as a module, choose M here: the
231 module will be called alim1535_wdt.
233 Most people will say N.
236 tristate "ALi M7101 PMU Computer Watchdog"
237 depends on WATCHDOG && X86 && PCI
239 This is the driver for the hardware watchdog on the ALi M7101 PMU
240 as used in the x86 Cobalt servers.
242 To compile this driver as a module, choose M here: the
243 module will be called alim7101_wdt.
245 Most people will say N.
248 tristate "AMD Elan SC520 processor Watchdog"
249 depends on WATCHDOG && X86
251 This is the driver for the hardware watchdog built in to the
252 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
253 This watchdog simply watches your kernel to make sure it doesn't
254 freeze, and if it does, it reboots your computer after a certain
257 You can compile this driver directly into the kernel, or use
258 it as a module. The module will be called sc520_wdt.
261 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
262 depends on WATCHDOG && X86
264 Enable support for the watchdog timer on the Eurotech CPU-1220 and
265 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
266 information are at <http://www.eurotech.it/>.
269 tristate "IB700 SBC Watchdog Timer"
270 depends on WATCHDOG && X86
272 This is the driver for the hardware watchdog on the IB700 Single
273 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
274 simply watches your kernel to make sure it doesn't freeze, and if
275 it does, it reboots your computer after a certain amount of time.
277 This driver is like the WDT501 driver but for slightly different hardware.
279 To compile this driver as a module, choose M here: the
280 module will be called ib700wdt.
282 Most people will say N.
285 tristate "IBM Automatic Server Restart"
286 depends on WATCHDOG && X86
288 This is the driver for the IBM Automatic Server Restart watchdog
289 timer built-in into some eServer xSeries machines.
291 To compile this driver as a module, choose M here: the
292 module will be called ibmasr.
295 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
296 depends on WATCHDOG && X86
298 This is a driver for the hardware watchdog on the ICP Wafer 5823
299 Single Board Computer (and probably other similar models).
301 To compile this driver as a module, choose M here: the
302 module will be called wafer5823wdt.
305 tristate "Intel 6300ESB Timer/Watchdog"
306 depends on WATCHDOG && X86 && PCI
308 Hardware driver for the watchdog timer built into the Intel
309 6300ESB controller hub.
311 To compile this driver as a module, choose M here: the
312 module will be called i6300esb.
315 tristate "Intel i8xx TCO Timer/Watchdog"
316 depends on WATCHDOG && (X86 || IA64) && PCI
318 Hardware driver for the TCO timer built into the Intel 82801
319 I/O Controller Hub family. The TCO (Total Cost of Ownership)
320 timer is a watchdog timer that will reboot the machine after
321 its second expiration. The expiration time can be configured
322 with the "heartbeat" parameter.
324 On some motherboards the driver may fail to reset the chipset's
325 NO_REBOOT flag which prevents the watchdog from rebooting the
326 machine. If this is the case you will get a kernel message like
327 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
329 To compile this driver as a module, choose M here: the
330 module will be called i8xx_tco.
332 Note: This driver will be removed in the near future. Please
333 use the Intel TCO Timer/Watchdog driver.
336 tristate "Intel TCO Timer/Watchdog"
337 depends on WATCHDOG && (X86 || IA64) && PCI
339 Hardware driver for the intel TCO timer based watchdog devices.
340 These drivers are included in the Intel 82801 I/O Controller
341 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
344 The TCO (Total Cost of Ownership) timer is a watchdog timer
345 that will reboot the machine after its second expiration. The
346 expiration time can be configured with the "heartbeat" parameter.
348 On some motherboards the driver may fail to reset the chipset's
349 NO_REBOOT flag which prevents the watchdog from rebooting the
350 machine. If this is the case you will get a kernel message like
351 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
353 To compile this driver as a module, choose M here: the
354 module will be called iTCO_wdt.
357 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
358 depends on WATCHDOG && X86
360 This is a driver for National Semiconductor PC87307/PC97307 hardware
361 watchdog cards as found on the SC1200. This watchdog is mainly used
362 for power management purposes and can be used to power down the device
363 during inactivity periods (includes interrupt activity monitoring).
365 To compile this driver as a module, choose M here: the
366 module will be called sc1200wdt.
368 Most people will say N.
371 tristate "National Semiconductor SCx200 Watchdog"
372 depends on WATCHDOG && SCx200 && PCI
374 Enable the built-in watchdog timer support on the National
375 Semiconductor SCx200 processors.
377 If compiled as a module, it will be called scx200_wdt.
380 tristate "SBC-60XX Watchdog Timer"
381 depends on WATCHDOG && X86
383 This driver can be used with the watchdog timer found on some
384 single board computers, namely the 6010 PII based computer.
385 It may well work with other cards. It reads port 0x443 to enable
386 and re-set the watchdog timer, and reads port 0x45 to disable
387 the watchdog. If you have a card that behave in similar ways,
388 you can probably make this driver work with your card as well.
390 You can compile this driver directly into the kernel, or use
391 it as a module. The module will be called sbc60xxwdt.
394 tristate "SBC8360 Watchdog Timer"
395 depends on WATCHDOG && X86
398 This is the driver for the hardware watchdog on the SBC8360 Single
399 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
401 To compile this driver as a module, choose M here: the
402 module will be called sbc8360.ko.
404 Most people will say N.
407 tristate "SMA CPU5 Watchdog"
408 depends on WATCHDOG && X86
411 To compile this driver as a module, choose M here: the
412 module will be called cpu5wdt.
414 config SMSC37B787_WDT
415 tristate "Winbond SMsC37B787 Watchdog Timer"
416 depends on WATCHDOG && X86
418 This is the driver for the hardware watchdog component on the
419 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
420 from Vision Systems and maybe others.
422 This watchdog simply watches your kernel to make sure it doesn't
423 freeze, and if it does, it reboots your computer after a certain
426 Usually a userspace daemon will notify the kernel WDT driver that
427 userspace is still alive, at regular intervals.
429 To compile this driver as a module, choose M here: the
430 module will be called smsc37b787_wdt.
432 Most people will say N.
435 tristate "W83627HF Watchdog Timer"
436 depends on WATCHDOG && X86
438 This is the driver for the hardware watchdog on the W83627HF chipset
439 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
440 (and likely others). This watchdog simply watches your kernel to
441 make sure it doesn't freeze, and if it does, it reboots your computer
442 after a certain amount of time.
444 To compile this driver as a module, choose M here: the
445 module will be called w83627hf_wdt.
447 Most people will say N.
450 tristate "W83697HF/W83697HG Watchdog Timer"
451 depends on WATCHDOG && X86
453 This is the driver for the hardware watchdog on the W83697HF/HG
454 chipset as used in Dedibox/VIA motherboards (and likely others).
455 This watchdog simply watches your kernel to make sure it doesn't
456 freeze, and if it does, it reboots your computer after a certain
459 To compile this driver as a module, choose M here: the
460 module will be called w83697hf_wdt.
462 Most people will say N.
465 tristate "W83877F (EMACS) Watchdog Timer"
466 depends on WATCHDOG && X86
468 This is the driver for the hardware watchdog on the W83877F chipset
469 as used in EMACS PC-104 motherboards (and likely others). This
470 watchdog simply watches your kernel to make sure it doesn't freeze,
471 and if it does, it reboots your computer after a certain amount of
474 To compile this driver as a module, choose M here: the
475 module will be called w83877f_wdt.
477 Most people will say N.
480 tristate "W83977F (PCM-5335) Watchdog Timer"
481 depends on WATCHDOG && X86
483 This is the driver for the hardware watchdog on the W83977F I/O chip
484 as used in AAEON's PCM-5335 SBC (and likely others). This
485 watchdog simply watches your kernel to make sure it doesn't freeze,
486 and if it does, it reboots your computer after a certain amount of
489 To compile this driver as a module, choose M here: the
490 module will be called w83977f_wdt.
493 tristate "ZF MachZ Watchdog"
494 depends on WATCHDOG && X86
496 If you are using a ZF Micro MachZ processor, say Y here, otherwise
497 N. This is the driver for the watchdog timer built-in on that
498 processor using ZF-Logic interface. This watchdog simply watches
499 your kernel to make sure it doesn't freeze, and if it does, it
500 reboots your computer after a certain amount of time.
502 To compile this driver as a module, choose M here: the
503 module will be called machzwd.
505 config SBC_EPX_C3_WATCHDOG
506 tristate "Winsystems SBC EPX-C3 watchdog"
507 depends on WATCHDOG && X86
509 This is the driver for the built-in watchdog timer on the EPX-C3
510 Single-board computer made by Winsystems, Inc.
512 *Note*: This hardware watchdog is not probeable and thus there
513 is no way to know if writing to its IO address will corrupt
514 your system or have any real effect. The only way to be sure
515 that this driver does what you want is to make sure you
516 are running it on an EPX-C3 from Winsystems with the watchdog
517 timer at IO address 0x1ee and 0x1ef. It will write to both those
518 IO ports. Basically, the assumption is made that if you compile
519 this driver into your kernel and/or load it as a module, that you
520 know what you are doing and that you are in fact running on an
523 To compile this driver as a module, choose M here: the
524 module will be called sbc_epx_c3.
526 # PowerPC Architecture
529 tristate "MPC8xx Watchdog Timer"
530 depends on WATCHDOG && 8xx
533 tristate "MPC83xx Watchdog Timer"
534 depends on WATCHDOG && PPC_83xx
537 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
538 depends on WATCHDOG && MV64X60
541 tristate "PowerPC Book-E Watchdog Timer"
542 depends on WATCHDOG && (BOOKE || 4xx)
544 Please see Documentation/watchdog/watchdog-api.txt for
550 tristate "RTAS watchdog"
551 depends on WATCHDOG && PPC_RTAS
553 This driver adds watchdog support for the RTAS watchdog.
555 To compile this driver as a module, choose M here. The module
556 will be called wdrtas.
561 tristate "Indy/I2 Hardware Watchdog"
562 depends on WATCHDOG && SGI_IP22
564 Hardware driver for the Indy's/I2's watchdog. This is a
565 watchdog timer that will reboot the machine after a 60 second
566 timer expired and no process has written to /dev/watchdog during
571 tristate "Nios2 Watchdog (Avalon)"
572 depends on WATCHDOG && NIOS2
574 This is a driver for a timer connected to the avalon switch fabric wich is
575 configured as a watchdog.
576 Once started the watchdog cannot be stopped!
577 This driver assumes you named the watchdog timer watchdog.
578 If you didn't you should rename the component or change the definition in
579 drivers/char/watchdog/avalonwdt.c
581 Most people will say N.
587 tristate "z/VM Watchdog Timer"
588 depends on WATCHDOG && S390
590 IBM s/390 and zSeries machines running under z/VM 5.1 or later
591 provide a virtual watchdog timer to their guest that cause a
592 user define Control Program command to be executed after a
595 To compile this driver as a module, choose M here. The module
596 will be called vmwatchdog.
598 # SUPERH Architecture
601 tristate "SuperH Watchdog"
602 depends on WATCHDOG && SUPERH
604 This driver adds watchdog support for the integrated watchdog in the
605 SuperH processors. If you have one of these processors and wish
606 to have watchdog support enabled, say Y, otherwise say N.
608 As a side note, saying Y here will automatically boost HZ to 1000
609 so that the timer has a chance to clear the overflow counter. On
610 slower systems (such as the SH-2 and SH-3) this will likely yield
611 some performance issues. As such, the WDT should be avoided here
612 unless it is absolutely necessary.
614 To compile this driver as a module, choose M here: the
615 module will be called shwdt.
618 bool "Allow mmap of SH WDT"
622 If you say Y here, user applications will be able to mmap the
625 # SPARC64 Architecture
627 config WATCHDOG_CP1XXX
628 tristate "CP1XXX Hardware Watchdog support"
629 depends on WATCHDOG && SPARC64 && PCI
631 This is the driver for the hardware watchdog timers present on
632 Sun Microsystems CompactPCI models CP1400 and CP1500.
634 To compile this driver as a module, choose M here: the
635 module will be called cpwatchdog.
637 If you do not have a CompactPCI model CP1400 or CP1500, or
638 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
639 you should say N to this option.
642 tristate "RIO Hardware Watchdog support"
643 depends on WATCHDOG && SPARC64 && PCI
645 Say Y here to support the hardware watchdog capability on Sun RIO
646 machines. The watchdog timeout period is normally one minute but
647 can be changed with a boot-time parameter.
649 # M68KNOMMU Architecture
652 tristate "MCF5272 Hardware Watchdog support"
653 depends on WATCHDOG && M5272
655 Say Y here to suuport the hardware watchdog capability on Freescale
656 Coldfire MCF5272 machines.
659 # ISA-based Watchdog Cards
662 comment "ISA-based Watchdog Cards"
663 depends on WATCHDOG && ISA
666 tristate "Berkshire Products ISA-PC Watchdog"
667 depends on WATCHDOG && ISA
669 This is the driver for the Berkshire Products ISA-PC Watchdog card.
670 This card simply watches your kernel to make sure it doesn't freeze,
671 and if it does, it reboots your computer after a certain amount of
672 time. This driver is like the WDT501 driver but for different
673 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
674 watchdog cards can be ordered from <http://www.berkprod.com/>.
676 To compile this driver as a module, choose M here: the
677 module will be called pcwd.
679 Most people will say N.
682 tristate "Mixcom Watchdog"
683 depends on WATCHDOG && ISA
685 This is a driver for the Mixcom hardware watchdog cards. This
686 watchdog simply watches your kernel to make sure it doesn't freeze,
687 and if it does, it reboots your computer after a certain amount of
690 To compile this driver as a module, choose M here: the
691 module will be called mixcomwd.
693 Most people will say N.
696 tristate "WDT Watchdog timer"
697 depends on WATCHDOG && ISA
699 If you have a WDT500P or WDT501P watchdog board, say Y here,
700 otherwise N. It is not possible to probe for this board, which means
701 that you have to inform the kernel about the IO port and IRQ that
702 is needed (you can do this via the io and irq parameters)
704 To compile this driver as a module, choose M here: the
705 module will be called wdt.
708 bool "WDT501 features"
711 Saying Y here and creating a character special file /dev/temperature
712 with major number 10 and minor number 131 ("man mknod") will give
713 you a thermometer inside your computer: reading from
714 /dev/temperature yields one byte, the temperature in degrees
715 Fahrenheit. This works only if you have a WDT501P watchdog board
718 If you want to enable the Fan Tachometer on the WDT501P, then you
719 can do this via the tachometer parameter. Only do this if you have a
720 fan tachometer actually set up.
723 # PCI-based Watchdog Cards
726 comment "PCI-based Watchdog Cards"
727 depends on WATCHDOG && PCI
730 tristate "Berkshire Products PCI-PC Watchdog"
731 depends on WATCHDOG && PCI
733 This is the driver for the Berkshire Products PCI-PC Watchdog card.
734 This card simply watches your kernel to make sure it doesn't freeze,
735 and if it does, it reboots your computer after a certain amount of
736 time. The card can also monitor the internal temperature of the PC.
737 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
739 To compile this driver as a module, choose M here: the
740 module will be called pcwd_pci.
742 Most people will say N.
745 tristate "PCI-WDT500/501 Watchdog timer"
746 depends on WATCHDOG && PCI
748 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
750 To compile this driver as a module, choose M here: the
751 module will be called wdt_pci.
754 bool "PCI-WDT501 features"
757 Saying Y here and creating a character special file /dev/temperature
758 with major number 10 and minor number 131 ("man mknod") will give
759 you a thermometer inside your computer: reading from
760 /dev/temperature yields one byte, the temperature in degrees
761 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
764 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
765 can do this via the tachometer parameter. Only do this if you have a
766 fan tachometer actually set up.
769 # USB-based Watchdog Cards
772 comment "USB-based Watchdog Cards"
773 depends on WATCHDOG && USB
776 tristate "Berkshire Products USB-PC Watchdog"
777 depends on WATCHDOG && USB
779 This is the driver for the Berkshire Products USB-PC Watchdog card.
780 This card simply watches your kernel to make sure it doesn't freeze,
781 and if it does, it reboots your computer after a certain amount of
782 time. The card can also monitor the internal temperature of the PC.
783 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
785 To compile this driver as a module, choose M here: the
786 module will be called pcwd_usb.
788 Most people will say N.