From: Grant Grundler <grundler@puffin.external.hp.com>
To: Thomas Marteau <marteaut@esiee.fr>
Cc: "parisc-linux@parisc-linux.org" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] First Draft of the help for the kernel options
Date: Wed, 26 Sep 2001 11:29:04 -0600 [thread overview]
Message-ID: <200109261729.LAA16546@puffin.external.hp.com> (raw)
In-Reply-To: Message from Thomas Marteau <marteaut@esiee.fr> of "Wed, 26 Sep 2001 00:42:01 +0200." <3BB10839.D23F2ED6@esiee.fr>
Thomas Marteau wrote:
> Hi all,
>
> As you know, PA/Linux source needs some help to guide their users.
> That's why I tried to complete the documentation for the kernel.
Excellent - I had forgotten about this already again.
> GSC/Gecko bus support
> CONFIG_GSC
> This option gives to the kernel the capability to manage GSC buses
> of HP computers.
It's really more than that. Or at least it was.
All code in drivers/gsc is enabled with this flag.
It's worth noting that systems with GSC slots, LASI, EISA or
Dino (GSCtoPCI) bridge need this defined.
> This option is compulsory if you want it working.
All MMIO access once required CONFIG_GSC.
IIRC, someone fixed this dependency (willy maybe?).
A real test is if A500 and/or C3000 can build/run w/o CONFIG_GSC.
...
> GSCtoPCI/DINO PCI support
> CONFIG_GSC_DINO
> By selecting this item, you add the use of your PCI extension slots.
I would say:
Add PCI support for Dino PCI Host Bus bridge.
PCI devices are sometimes embedded in GSC add-on cards (aka "card-mode Dino").
> In order to be useful, you need a quite recent HP computer like those
> based on PA7300LC or PA8X00.
"recent" means "not the oldest and not the newest".
I think mentioning some examples would be helpful (eg B132L, C200).
> HP Lasi SCSI support
> CONFIG_SCSI_LASI
> If you have an old HP system like a 712, you should keep this on.
> This will enable the
> For quite recent computers, you may be able to turn this off.
If this can be a module, then we should mention that.
Again, some example systems with LASI/ASP built-in would be good.
(712/715/720/735/B132L/et al).
> Lasi ethernet
> CONFIG_LASI_82596
> This option adds the driver for one of most used network cards.
It's not a seperate card. It's integrated in the LASI chip.
The question really is if apricot signals are exported out the
back of the machine. Off hand, I suspect only B180 (systems with
100BT instead of 10BT) falls into this category.
Otherwise all systems with LASI chip use this.
...
> PA Harmony audio driver
> CONFIG_SOUND_HARMONY
> This option enables the audio part of the LASI controller. Since it is
> standard to all the boxes, this option should be set for any
> workstation.
Not true. Newer workstations with suckyio use AD1889 (IIRC).
thanks,
grant
prev parent reply other threads:[~2001-09-26 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 22:42 [parisc-linux] First Draft of the help for the kernel options Thomas Marteau
2001-09-26 17:29 ` Grant Grundler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200109261729.LAA16546@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=marteaut@esiee.fr \
--cc=parisc-linux@parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox