| 1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
| 2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.13 2006/11/27 00:13:19 nightmorph Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.14 2007/03/13 00:40:27 nightmorph Exp $ --> |
| 3 | |
3 | |
| 4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 5 | |
5 | |
| 6 | <guide link="/doc/en/usb-guide.xml"> |
6 | <guide link="/doc/en/usb-guide.xml"> |
| 7 | <title>Gentoo Linux USB Guide</title> |
7 | <title>Gentoo Linux USB Guide</title> |
| … | |
… | |
| 17 | |
17 | |
| 18 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
18 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 19 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
19 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 20 | <license/> |
20 | <license/> |
| 21 | |
21 | |
| 22 | <version>1.11</version> |
22 | <version>1.12</version> |
| 23 | <date>2006-11-26</date> |
23 | <date>2007-03-12</date> |
| 24 | |
24 | |
| 25 | <chapter> |
25 | <chapter> |
| 26 | <title>Introduction</title> |
26 | <title>Introduction</title> |
| 27 | <section> |
27 | <section> |
| 28 | <title>What is USB?</title> |
28 | <title>What is USB?</title> |
| … | |
… | |
| 511 | </p> |
511 | </p> |
| 512 | |
512 | |
| 513 | </body> |
513 | </body> |
| 514 | </section> |
514 | </section> |
| 515 | <section> |
515 | <section> |
| 516 | <title>Hot or Cold plug??</title> |
516 | <title>Hotplug</title> |
| 517 | <body> |
517 | <body> |
| 518 | |
518 | |
| 519 | <p> |
519 | <p> |
| 520 | Gentoo uses two packages, <c>sys-apps/hotplug</c> and <c>sys-apps/coldplug</c> |
520 | Gentoo uses <c>sys-apps/hotplug</c> to do some magic with <e>hot-pluggable</e> |
| 521 | to do some magic with <e>hot-pluggable</e> devices. Just like any other magic |
521 | devices. Just like any other magic trick, there is a simple logic behind this |
| 522 | trick, there is a simple logic behind this one too. We shall now see what that |
522 | one too. We shall now see what that is, and in the process hopefully we will be |
| 523 | is, and in the process hopefully we will be able to understand these twins |
523 | able to understand these twins better. |
| 524 | better. |
|
|
| 525 | </p> |
524 | </p> |
| 526 | |
525 | |
| 527 | <p> |
526 | <p> |
| 528 | Firmware can be defined as the software on a piece of hardware that is loaded |
527 | Firmware can be defined as the software on a piece of hardware that is loaded |
| 529 | and executed but can't be modified easily. Many devices have firmware in them |
528 | and executed but can't be modified easily. Many devices have firmware in them |
| … | |
… | |
| 544 | </p> |
543 | </p> |
| 545 | |
544 | |
| 546 | <pre caption="Installing hotplug"> |
545 | <pre caption="Installing hotplug"> |
| 547 | # <i>emerge hotplug</i> |
546 | # <i>emerge hotplug</i> |
| 548 | </pre> |
547 | </pre> |
| 549 | |
|
|
| 550 | <p> |
|
|
| 551 | Now the obvious question would be, what is coldplug and why is it needed? |
|
|
| 552 | <c>sys-apps/coldplug</c> does what hotplug does, but it does it for |
|
|
| 553 | <e>hot-pluggable</e> devices that are already connected at boot time. A good |
|
|
| 554 | example of this would be a USB Network card. Earlier, hotplug was the package |
|
|
| 555 | responsible for handling both, but then it was split into hotplug and coldplug, |
|
|
| 556 | with coldplug doing all the work. Install it if you have <e>hot-pluggable</e> |
|
|
| 557 | devices that you need activated on boot up. Afterward, you can add the coldplug |
|
|
| 558 | init script to the boot runlevel. |
|
|
| 559 | </p> |
|
|
| 560 | |
|
|
| 561 | <pre caption="Installing coldplug"> |
|
|
| 562 | # <i>emerge coldplug</i> |
|
|
| 563 | <comment>(And you can add it to the boot runlevel)</comment> |
|
|
| 564 | # <i>rc-update add coldplug boot</i> |
|
|
| 565 | * coldplug added to runlevel boot |
|
|
| 566 | * rc-update complete. |
|
|
| 567 | </pre> |
|
|
| 568 | |
|
|
| 569 | <note> |
|
|
| 570 | You no longer need to emerge <c>coldplug</c> if you're using <c>udev</c> version |
|
|
| 571 | 103 and higher, as udev itself will handle module loading. If you are upgrading |
|
|
| 572 | to version 103, you must unmerge coldplug (<c>emerge -aC coldplug</c>) before |
|
|
| 573 | upgrading udev. Be sure to remove the coldplug init script from all runlevels |
|
|
| 574 | (<c>rc-update del coldplug</c>), and then delete it from |
|
|
| 575 | <path>/etc/init.d/</path> afterward. |
|
|
| 576 | </note> |
|
|
| 577 | |
548 | |
| 578 | </body> |
549 | </body> |
| 579 | </section> |
550 | </section> |
| 580 | </chapter> |
551 | </chapter> |
| 581 | |
552 | |