From: Matthew Wilcox <willy@debian.org>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: Stephan Trajkoff <stephan@itp.bg>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] k210/819 Zalon driver
Date: Tue, 9 Jul 2002 14:03:42 +0100 [thread overview]
Message-ID: <20020709140342.X27706@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020709072916.GH6681@sleepie.demon.co.uk>; from rhirst@linuxcare.com on Tue, Jul 09, 2002 at 08:29:16AM +0100
On Tue, Jul 09, 2002 at 08:29:16AM +0100, Richard Hirst wrote:
> On Tue, Jul 09, 2002 at 10:56:01AM +0300, Stephan Trajkoff wrote:
> > Hi,
> > why I need to enable PCI/EISA to make available option zalon driver in
> > SCSI drivers?
> > My HP K210 don't have PCIs and EISA?!!?!?!?
>
> At the moment you have to enable PCI because that is the way the config
> script is organised. I don't know if zalon support would build without
> PCI because it uses the ncr53c8xx driver which normally drives only PCI
> chips. It is an area that needs attention anyway, because if you enable
> sym53c8xx_2 you wont get the zalon option at all (which is obviously
> wrong).
>
> Richard?!!?!?!?
Something else is that even if you don't have PCI slots, some of the cards
you have may contain a GSC<->PCI adapter and a PCI device. The 100Mbit
& Gigabit lan cards are definitely like this and there may be others.
It probably is possible to compile the zalon driver without having PCI
enabled but it'll take a small amount of work to verify.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-07-09 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 7:56 [parisc-linux] k210/819 Zalon driver Stephan Trajkoff
2002-07-09 7:29 ` Richard Hirst
2002-07-09 11:23 ` Stephan Trajkoff
2002-07-09 11:09 ` Andy Walker
2002-07-09 11:34 ` Stephan Trajkoff
2002-07-09 18:48 ` Grant Grundler
2002-07-09 13:03 ` Matthew Wilcox [this message]
2002-07-20 12:27 ` Richard Hirst
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=20020709140342.X27706@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.com \
--cc=stephan@itp.bg \
/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