/[gentoo]/xml/htdocs/doc/en/usb-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/usb-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.6 Revision 1.13
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.6 2005/08/10 13:09:27 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/usb-guide.xml,v 1.13 2006/11/27 00:13:19 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.4</version> 22<version>1.11</version>
23<date>2005-06-17</date> 23<date>2006-11-26</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>
179the kernel sources you want to use. Please ensure the same before proceeding. 179the kernel sources you want to use. Please ensure the same before proceeding.
180</note> 180</note>
181 181
182</body> 182</body>
183</section> 183</section>
184<section id="2.6.xconfig"> 184<section id="newkernelconfig">
185<title>Config options for the 2.6.x kernel</title> 185<title>Config options for the 2.6.x kernel</title>
186<body> 186<body>
187 187
188<p> 188<p>
189Now we will look at some of the options we will have to enable in the 2.6 189Now we will look at some of the options we will have to enable in the 2.6
190kernel to ensure proper USB support for our devices. If you are using a 2.4 190kernel to ensure proper USB support for our devices. If you are using a 2.4
191kernel, please proceed with <uri link="#2.4.xconfig">Config options for the 191kernel, please proceed with <uri link="#oldkernelconfig">Config options for the
1922.4.x kernel</uri>. 1922.4.x kernel</uri>.
193</p> 193</p>
194 194
195<note> 195<note>
196Examples in this document will show configuration options for basic USB 196Examples in this document will show configuration options for basic USB
232 232
233<comment>(Moving a little further down, we come to CDC and mass storage.)</comment> 233<comment>(Moving a little further down, we come to CDC and mass storage.)</comment>
234&lt; &gt; USB Modem (CDC ACM) support 234&lt; &gt; USB Modem (CDC ACM) support
235&lt;*&gt; USB Printer support 235&lt;*&gt; USB Printer support
236&lt;*&gt; USB Mass Storage support 236&lt;*&gt; USB Mass Storage support
237 [*] USB Mass Storage Write-Protected Media Detection (EXPERIMENTAL)
238 237
239<comment>(Then the HID bits. 238<comment>(Then the HID bits.
240You have to select HID input support if you have a USB keyboard, 239You have to select HID input support if you have a USB keyboard,
241mouse, joystick or any other USB input device)</comment> 240mouse, joystick or any other USB input device)</comment>
242--- USB Input Devices 241--- USB Input Devices
260working as it should. 259working as it should.
261</p> 260</p>
262 261
263</body> 262</body>
264</section> 263</section>
265<section id="2.4.xconfig"> 264<section id="oldkernelconfig">
266<title>Config options for the 2.4.x kernel</title> 265<title>Config options for the 2.4.x kernel</title>
267<body> 266<body>
268 267
269<p> 268<p>
270We will look at the options the we will have to enable in the 2.4 kernel to 269We will look at the options the we will have to enable in the 2.4 kernel to
271ensure proper USB support for our devices. If you are using a 2.6 kernel, 270ensure proper USB support for our devices. If you are using a 2.6 kernel,
272please look at <uri link="#2.6.xconfig">Config options for the 2.6.x 271please look at <uri link="#newkernelconfig">Config options for the 2.6.x
273kernel</uri>. 272kernel</uri>.
274</p> 273</p>
275 274
276<note> 275<note>
277Examples in this document will show configuration options for basic USB 276Examples in this document will show configuration options for basic USB
409/dev/sda1 490M 34M 457M 7% /mnt/usb 408/dev/sda1 490M 34M 457M 7% /mnt/usb
410</pre> 409</pre>
411 410
412<note> 411<note>
413Digital cameras can be accessed the same way as memory sticks. I have a Nikon 412Digital cameras can be accessed the same way as memory sticks. I have a Nikon
414Coolpix 5200 and this is the way I access it. The camera is set to behave like 413Coolpix 5200 and this is the way I access it. Cameras these days usually have
415a USB mass storage device (as against PTP mode, which most cameras have these 414two modes to transfer pictures; USB mass storage and PTP (Picture Transfer
416days) and the procedure is exactly the same, because of which I have not 415Protocol). The camera is set to USB mass storage mode and hence the procedure is
416exactly the same as that of accessing a memory stick because of which I have not
417explained in detail about the same. Please note that this may NOT work in all 417explained in detail about it. Please note that this may NOT work in all cases
418cases and with all digital cameras that have USB support. 418and with all digital cameras that have USB support.
419</note> 419</note>
420 420
421<p> 421<p>
422How would a USB mouse show up in case you had one? It will show up as an HID 422How would a USB mouse show up in case you had one? It will show up as an HID
423device. 423device.
538<p> 538<p>
539To cut the long story short, Gentoo uses <c>sys-apps/hotplug</c> to handle 539To cut the long story short, Gentoo uses <c>sys-apps/hotplug</c> to handle
540the firmware side of things in <e>hot-pluggable</e> devices. 540the firmware side of things in <e>hot-pluggable</e> devices.
541<c>sys-apps/hotplug</c> will use the required firmware to make that device 541<c>sys-apps/hotplug</c> will use the required firmware to make that device
542usable. The firmware should be put in the <path>/lib/firmware</path> directory 542usable. The firmware should be put in the <path>/lib/firmware</path> directory
543and is picked up from there. Getting it is simple: the usual emerge will do. 543and is picked up from there. Getting it is simple; the usual emerge will do.
544</p> 544</p>
545 545
546<pre caption="Installing hotplug"> 546<pre caption="Installing hotplug">
547# <i>emerge hotplug</i> 547# <i>emerge hotplug</i>
548</pre> 548</pre>
549 549
550<p> 550<p>
551Now the obvious question would be, what is coldplug and why is it needed? 551Now 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 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 553<e>hot-pluggable</e> devices that are already connected at boot time. A good
554example of this would be a USB Network card. Earlier the hotplug package was 554example of this would be a USB Network card. Earlier, hotplug was the package
555responsible for handling both, but then it was split into hotplug and coldplug, 555responsible for handling both, but then it was split into hotplug and coldplug,
556each with their distinct purposes. Emerge it if you have <e>hot-pluggable</e> 556with coldplug doing all the work. Install it if you have <e>hot-pluggable</e>
557devices that you need activated on boot up. 557devices that you need activated on boot up. Afterward, you can add the coldplug
558init script to the boot runlevel.
558</p> 559</p>
559 560
560<pre caption="Installing coldplug"> 561<pre caption="Installing coldplug">
561# <i>emerge coldplug</i> 562# <i>emerge coldplug</i>
562<comment>(And you can add it to the boot runlevel)</comment> 563<comment>(And you can add it to the boot runlevel)</comment>
564 * coldplug added to runlevel boot 565 * coldplug added to runlevel boot
565 * rc-update complete. 566 * rc-update complete.
566</pre> 567</pre>
567 568
568<note> 569<note>
569The above initscript does what hotplug's initscript used to do (for already 570You no longer need to emerge <c>coldplug</c> if you're using <c>udev</c> version
570attached hot-pluggable devices). hotplug does not have an initscript of its 571103 and higher, as udev itself will handle module loading. If you are upgrading
571own as of now. 572to version 103, you must unmerge coldplug (<c>emerge -aC coldplug</c>) before
573upgrading 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.
572</note> 576</note>
573 577
574</body> 578</body>
575</section> 579</section>
576</chapter> 580</chapter>
587I thought they all deserve some credit, so here we go! 591I thought they all deserve some credit, so here we go!
588</p> 592</p>
589 593
590<ul> 594<ul>
591 <li><uri link="http://www.usb.org">The Official USB Website</uri></li> 595 <li><uri link="http://www.usb.org">The Official USB Website</uri></li>
592 <li><uri link="http://www.usb.org/faq">The USB FAQ</uri></li> 596 <li><uri link="http://www.usb.org/about/faq">The USB FAQ</uri></li>
593 <li> 597 <li>
594 <uri 598 <uri
595 link="http://h18000.www1.hp.com/productinfo/development/openhci.html">Compaq's 599 link="http://h18000.www1.hp.com/productinfo/development/openhci.html">Compaq's
596 OHCI Standard</uri> 600 OHCI Standard</uri>
597 </li> 601 </li>
605 </li> 609 </li>
606</ul> 610</ul>
607 611
608</body> 612</body>
609</section> 613</section>
614<section>
615<title>Other Interesting Links</title>
616<body>
617
618<ul>
619 <li><uri link="/doc/en/liveusb.xml">Gentoo Linux LiveUSB HOWTO</uri></li>
620</ul>
621
622</body>
623</section>
610</chapter> 624</chapter>
611</guide> 625</guide>

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.13

  ViewVC Help
Powered by ViewVC 1.1.20