old-www/HOWTO/PA-RISC-Linux-Boot-HOWTO/kernelconf.html

1327 lines
21 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Kernel configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="PA-RISC/Linux Boot HOWTO"
HREF="index.html"><LINK
REL="UP"
TITLE="Building and installing a custom kernel"
HREF="vmlinux.html"><LINK
REL="PREVIOUS"
TITLE="GCC compiler"
HREF="gcc.html"><LINK
REL="NEXT"
TITLE="Kernel installation"
HREF="kernelinstall.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PA-RISC/Linux Boot HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gcc.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Building and installing a custom kernel</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="kernelinstall.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="kernelconf"
></A
>5.2. Kernel configuration</H1
><P
>&#13; If you want to take advantage of the latest kernel improvements, we
suggest you retrieve it from the official
<A
HREF="http://cvs.parisc-linux.org/"
TARGET="_top"
>PA-RISC/Linux CVS</A
>.
Please mind that the <EM
>vanilla</EM
> kernel that can
be found at <A
HREF="http://www.kernel.org/"
TARGET="_top"
>http://www.kernel.org/</A
>
is generally out of sync with the above mentioned CVS kernel, and that
snapshots of this kernel are available too, check the
<A
HREF="http://cvs.parisc-linux.org/download/"
TARGET="_top"
>download area</A
>.
In the following, we will focus on a fresh CVS tree.
</P
><P
>&#13; The best way to obtain appreciable performances is to get a well
configured kernel. For the PA-RISC platform, <B
CLASS="command"
>make oldconfig</B
>
is a kind of default setup. If you want to make your own kernel,
the first step is to know what hardware you have. The best way to
grab useful info is to look at your box and find a maximum of data
(model name, partnumber, chipsets, and so on). If you have already
booted your box, you can take a look at <B
CLASS="command"
>dmesg</B
>
output. Then, go to the <A
HREF="http://hwdb.parisc-linux.org/"
TARGET="_top"
>official
hardware database</A
> or to the
<A
HREF="http://partsurfer.hp.com/"
TARGET="_top"
>HP partsurfer website</A
>.
</P
><P
>&#13; Once you know what is inside your box and what you want to do with it,
just run <B
CLASS="command"
>make menuconfig</B
> or another config command.
</P
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="kernelconf24"
></A
>5.2.1. Configuring 2.4 kernels</H2
><DIV
CLASS="highlights"
><A
NAME="AEN1357"
></A
><P
>&#13; Here is a brief list of architecture dependent menus for 2.4 kernels.
You should take a look at them, to see if the values set match
your hardware. Mind that 2.4 kernels are now considered <EM
>deprecated</EM
>
anyway: you will not get community support for them.
</P
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Remember that <B
CLASS="command"
>make oldconfig</B
> is a
good base to start with, since it works for almost any machine.
</P
></TD
></TR
></TABLE
></DIV
><P
></P
><UL
><LI
><P
><EM
>Processor type</EM
> - indicates your CPU model</P
></LI
><LI
><P
><EM
>General options</EM
> - tells you what is going to be enabled in your kernel (U2/Uturn, USC/GSC/HSC, Lasi, Wax, Dino, LBA/Elroy, SuperIO)</P
></LI
><LI
><P
><EM
>Parallel port support</EM
> - enables/disables the Lasi/ASP parport</P
></LI
><LI
><P
><EM
>SCSI support</EM
> - check there for your SCSI chipset (Lasi, Zalon, NCR/SYM53C8XX or other)</P
></LI
><LI
><P
><EM
>Network device support</EM
> - is used to set your network card (Lasi, Tulip...)</P
></LI
><LI
><P
><EM
>Character devices</EM
> - defines your I/O capabilities (Lasi, Dino, MUX see <A
HREF="kernelconf.html#MUX24"
>Section 5.2.1.3</A
>)</P
></LI
><LI
><P
><EM
>HIL Support</EM
> - useful if you have a HIL controller. See below <A
HREF="kernelconf.html#HIL24"
>Section 5.2.1.1</A
>.</P
></LI
><LI
><P
><EM
>Console drivers</EM
> - is directly related to your console mode (STI console or STI framebuffer)</P
></LI
><LI
><P
><EM
>Sound</EM
> - enables/disables the Harmony driver</P
></LI
></UL
><P
>&#13; As you can see, menus specifically concerned by PA-RISC hardware are not
that numerous, but there are lots of dependencies between them. Now,
you must configure the kernel accordingly to what you plan to use
this box for. Here is a list of some menus you should be going
through to configure additional functionalities you might want:
</P
><P
></P
><UL
><LI
><P
>&#13; <EM
>General setup</EM
> - is responsible for binary
formats handled by the kernel. You need ELF, and can try SOM
(support for HP/UX binaries. It *might* work with some static
executables).
</P
></LI
><LI
><P
>&#13; <EM
>Block devices</EM
> - sets the ramdisk and loopback
support. You probably won't use them.
</P
></LI
><LI
><P
>&#13; <EM
>ATA/IDE/MFM/RLL support</EM
> - You will need to
check this to enable IDE. See <A
HREF="kernelconf.html#IDE24"
>Section 5.2.1.4</A
>.
</P
></LI
><LI
><P
>&#13; <EM
>File Systems/Network File Systems</EM
> - is where
to set EXT3 or NFS support.
</P
></LI
><LI
><P
>&#13; <EM
>USB support</EM
> - If you have enabled
<EM
>SuperIO</EM
> and want USB, look here:
<A
HREF="kernelconf.html#USB24"
>Section 5.2.1.2</A
>.
</P
></LI
></UL
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; By the time this HOWTO was written, there was no floppy drive
support; and what's more, it is not expected to ever be supported.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; When you're done with it, save your kernel configuration.
Everything is written in the <TT
CLASS="filename"
>.config</TT
> file.
You should back it up because <B
CLASS="command"
>make distclean</B
>
will remove it. At this stage, you can do
<B
CLASS="command"
>make dep vmlinux</B
> and if everything goes fine,
you will have a new kernel in a couple of minutes.
</P
><P
>&#13; Here follows brief information about specific hardware configurations.
</P
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="HIL24"
></A
>5.2.1.1. <SPAN
CLASS="acronym"
>HIL</SPAN
> Support in 2.4</H3
><P
>&#13; Since <TT
CLASS="literal"
>kernel-2.4.18-pa45</TT
>, there is a full
<SPAN
CLASS="acronym"
>HIL</SPAN
> support, for mice, tablets and keyboards.
It is based on the <EM
>Linux Input Driver</EM
> model.
See the <A
HREF="http://www.parisc-linux.org/faq/"
TARGET="_top"
>PA-RISC/Linux FAQ</A
>
and the <A
HREF="http://lists.parisc-linux.org/pipermail/parisc-linux/2002-June/016757.html"
TARGET="_top"
>mail</A
>
posted on the mailing list by <EM
>Helge Deller</EM
>.
Here is how to configure it:
</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Make sure you have a 2.4.18-pa45 or higher kernel source.</P
></LI
><LI
><P
>&#13; Look at your kernel configuration for the following options:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;CONFIG_INPUT=y
CONFIG_INPUT_KEYBDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_SERIO=y
CONFIG_HIL=y
CONFIG_HP_SDC=y
CONFIG_HIL_MLC=y
CONFIG_HP_SDC_MLC=y
CONFIG_HIL_KBD=y
CONFIG_HIL_PTR=y
</PRE
></FONT
></TD
></TR
></TABLE
>
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; There is no more <TT
CLASS="literal"
>CONFIG_HIL_KBD_BASIC</TT
>.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>&#13; On your target system, check that the following devices are available:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;/dev/input/mice
/dev/input/mouseX
/dev/input/eventX
</PRE
></FONT
></TD
></TR
></TABLE
>
If they are not yet present, create them as <TT
CLASS="literal"
>root</TT
> by running:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<TT
CLASS="prompt"
>[user@machine ~/dir]&#62;</TT
> <B
CLASS="command"
>cd /dev; MAKEDEV input</B
>
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; Configure <B
CLASS="command"
>gpm</B
> with the following
options in <TT
CLASS="filename"
>/etc/gpm.conf</TT
>:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;device=/dev/input/mice
type=imps2
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; Here is a sample <TT
CLASS="filename"
>/etc/X11/XF86Config-4</TT
>:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Section "InputDevice"
Identifier "HIL Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "HIL Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "HIL Keyboard"
InputDevice "HIL Mouse"
EndSection
</PRE
></FONT
></TD
></TR
></TABLE
>
You can also download a sample <TT
CLASS="filename"
>XF86Config-4</TT
> here:
<A
HREF="ftp://ftp.parisc-linux.org/XFree86/XF86Config-4"
TARGET="_top"
>ftp://ftp.parisc-linux.org/XFree86/XF86Config-4</A
>,
adjust color depth and resolution, and put it in your
<TT
CLASS="filename"
>/etc/X11/</TT
>.
</P
></LI
></OL
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="USB24"
></A
>5.2.1.2. <SPAN
CLASS="acronym"
>USB</SPAN
> Support in 2.4</H3
><P
>&#13; <SPAN
CLASS="acronym"
>USB</SPAN
> support on HP-PA is still experimental, therefore it is
only configured as modules in default kernel configuration.
We have tried to install a B2000 with builtin <SPAN
CLASS="acronym"
>USB</SPAN
> support,
both 32 and 64bit, and it worked fine, despite some keyboard problems.
Don't worry, nothing critical: the range of keys located between
the main part of the keyboard (the letters, backspace, enter...)
and the numeric pad are broken. They do not behave at all as expected.
</P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; You can use the numeric pad as arrow keys: when <B
CLASS="keycap"
>NumLock</B
>
is not activated, it behaves as a navigation pad. <EM
>e.g.</EM
>
<B
CLASS="keycap"
>8</B
> is <B
CLASS="keycap"
>Up Arrow</B
>, <B
CLASS="keycap"
>4</B
> is
<B
CLASS="keycap"
>Left Arrow</B
> and so on.
</P
></TD
></TR
></TABLE
></DIV
><P
></P
><OL
TYPE="1"
><LI
><P
>Make sure you have a 2.4.18 or higher kernel source.</P
></LI
><LI
><P
>&#13; Look at your kernel configuration for the following options:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;CONFIG_SUPERIO=y
CONFIG_HOTPLUG=y
CONFIG_INPUT=y
CONFIG_INPUT_KEYBDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_OHCI=y
CONFIG_HID=y
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; On your target system, check that the following devices
are available:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;/dev/input/mice
/dev/input/mouseX
/dev/input/eventX
</PRE
></FONT
></TD
></TR
></TABLE
>
If they are not yet present, create them as <TT
CLASS="literal"
>root</TT
> by running:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<TT
CLASS="prompt"
>[user@machine ~/dir]&#62;</TT
> <B
CLASS="command"
>cd /dev; MAKEDEV input</B
>
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; Configure <B
CLASS="command"
>gpm</B
> with the following options
in <TT
CLASS="filename"
>/etc/gpm.conf</TT
>:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;device=/dev/input/mice
type=imps2
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; The XF86-Config-4 is similar to the
<TT
CLASS="literal"
>HIL</TT
> one, as it is also using the <EM
>Linux
Input Driver</EM
>.
</P
></LI
></OL
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="MUX24"
></A
>5.2.1.3. <SPAN
CLASS="acronym"
>MUX</SPAN
> Console Support in 2.4</H3
><P
>&#13; <TT
CLASS="literal"
>MUX Console</TT
> has been improved by
<EM
>Richard Hirst</EM
> in 2.4.18-pa37 kernel,
though it is still a very <EM
>experimental</EM
> feature.
It is expected to provide adequate <TT
CLASS="literal"
>MUX Console</TT
>
support to <TT
CLASS="literal"
>E-</TT
> and <TT
CLASS="literal"
>K-Class</TT
> machines.
Feedback would be really appreciated.
</P
><P
>Now follow these steps to get it to work:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Make sure you have a 2.4.18-pa37 or higher kernel source.
</P
></LI
><LI
><P
>&#13; Look at your kernel configuration for the following options:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_GSC=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_SERIAL_MUX=y
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; On your target system, check that the following devices are available:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;/dev/ttyB0
</PRE
></FONT
></TD
></TR
></TABLE
>
If they are not yet present, create them as <TT
CLASS="literal"
>root</TT
> by running:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<TT
CLASS="prompt"
>[user@machine ~/dir]&#62;</TT
> <B
CLASS="command"
>cd /dev; MAKEDEV ttyB0</B
>
</PRE
></FONT
></TD
></TR
></TABLE
>
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; It needs a recent <TT
CLASS="literal"
>MAKEDEV</TT
> package to be
created this way.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>&#13; Now you can boot your system, taking care that <B
CLASS="command"
>PALO</B
> uses
<TT
CLASS="computeroutput"
>console=ttyB0</TT
>.
</P
></LI
></OL
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="IDE24"
></A
>5.2.1.4. <SPAN
CLASS="acronym"
>IDE</SPAN
> Devices Support in 2.4</H3
><P
>&#13; There is nothing really special about <SPAN
CLASS="acronym"
>IDE</SPAN
>
support. You have to check that the <EM
>IDE Chipset</EM
>
in use in your box is supported by the kernel. A common chipset
found on PA-RISC hardware is <TT
CLASS="literal"
>NS87415</TT
>.
You can find it on B2000, J5000 and C3000 for instance. You will
need <SPAN
CLASS="acronym"
>IDE</SPAN
> support to use some CD-ROM devices.
</P
><P
>&#13; Here is an example to get <SPAN
CLASS="acronym"
>IDE</SPAN
> to work with this chipset:
</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Make sure you have a recent kernel source.</P
></LI
><LI
><P
>&#13; Look at your kernel configuration for the following options:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;CONFIG_IOMMU_CCIO=y
CONFIG_PCI=y
CONFIG_PCI_LBA=y
CONFIG_IOSAPIC=y
CONFIG_IOMMU_SBA=y
CONFIG_SUPERIO=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_NS87415=y
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#13; On your target system, check that the following devices
are available:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;/dev/hd*
</PRE
></FONT
></TD
></TR
></TABLE
>
If they are not yet present, create them as <TT
CLASS="literal"
>root</TT
> by running:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<TT
CLASS="prompt"
>[user@machine ~/dir]&#62;</TT
> <B
CLASS="command"
>cd /dev; MAKEDEV hda hdb hdc hdd hde</B
>
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
></OL
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Of course we didn't mention much of the architecture
independent options. Moreover, the above settings may vary depending
on your hardware. This is just an example.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="kernelconf26"
></A
>5.2.2. Configuring 2.6 kernels</H2
><DIV
CLASS="highlights"
><A
NAME="AEN1552"
></A
><P
>&#13; Here is a brief list of architecture dependent menus for 2.6 kernels.
You should take a look at them, to see if the values set match
your hardware:
</P
></DIV
><P
></P
><UL
><LI
><P
><EM
>Processor type and features</EM
> - indicates your CPU model
and some specific features such as SMP or Discontigmem support</P
></LI
><LI
><P
><EM
>Bus options</EM
> - tells you what bus support is going to be
enabled in your kernel (U2/Uturn, USC/GSC/HSC, Lasi, Wax, Dino, LBA/Elroy, SuperIO)</P
></LI
><LI
><P
><EM
>PA-RISC specific drivers</EM
> - enables/disables some PA-RISC specific
drivers, such as LED support, GSP and Stable Storage support.</P
></LI
></UL
><P
>&#13; As you can see, menus specifically concerned by PA-RISC hardware are not
that numerous, and everything else is much generic by now. Still,
you must configure the kernel accordingly to what you plan to use
this box for and what features you want supported. Many other drivers are found in
their respective submenus, such as SCSI, with the Zalon, Lasi SCSI and SYM2 drivers being
there, or the Framebuffer devices (STI) in the Graphics Support menu, or the sound drivers
(Harmony and AD1889) in the Sound menu. Help is often provided, feel free to look at it.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Most of what was said for 2.4 is somewhat still applicable to 2.6.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gcc.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="kernelinstall.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>GCC compiler</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="vmlinux.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Kernel installation</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>