public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hood <jdthood@mail.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parport_pc to use pnpbios_register_driver()
Date: 13 Nov 2001 16:41:46 -0500	[thread overview]
Message-ID: <1005687707.21561.14.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.33.0111120921110.16450-100000@chaos.tp1.ruhr-uni-bochum.de>
In-Reply-To: <Pine.LNX.4.33.0111120921110.16450-100000@chaos.tp1.ruhr-uni-bochum.de>

On Mon, 2001-11-12 at 03:30, Kai Germaschewski wrote:
> On Mon, 12 Nov 2001, Keith Owens wrote:
> > Does this combination make sense?  If you are building a pnpbios driver
> > into the kernel then the configuration should force pnpbios support to
> > be built in as well.  We don't allow this combination for things like
> > scsi or ide, they require the common support to be built in if any
> > drivers are built in.  IMHO this problem should be fixed in .config,
> > not in driver source.
> 
> The affected drivers usually support different interfaces to the hardware, 
> like ISA, ISAPnP, PCI, so it makes sense to build them w/o ISAPnP support.

True.

> For instance, people may want to have built-in serial support (w/o ISAPnP 
> support is fine, because they've only got a standard SuperI/O chip), but 
> also modular isapnp and sound driver support, so they can demand load 
> sound support if necessary.

Fine.

> Making ISAPnP mandatory only because you build a driver which supports
> ISAPnP hardware is not an option IMO. This would force people to build
> ISAPnP support who don't even have an ISA bus (only because the driver for
> their PCI card also supports an ISAPnP variant).

You misunderstand.  Obviously we don't want to force anyone
to build in isa-pnp or pnpbios support.  What Keith is saying
is that IF isa-pnp code is enabled in a driver then the isa-pnp
driver should also be built.  Furthermore if isa-pnp code is
enabled in an _integral_ (i.e., non-modular) driver, then the
isa-pnp driver should also be built integrally.  The combination
of integral-driver-with-isa-pnp-support-enabled and modular
isa-pnp driver should be disallowed by the configurator.

Thomas


  reply	other threads:[~2001-11-13 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-10  5:36 [PATCH] parport_pc to use pnpbios_register_driver() Thomas Hood
     [not found] ` <200111102104.fAAL4pk19362@spf4.us4.outblaze.com>
2001-11-11  4:52   ` [PATCH] parport_pc to use pnpbios_register_driver() #2 Thomas Hood
2001-11-11 20:42 ` [PATCH] parport_pc to use pnpbios_register_driver() Kai Germaschewski
2001-11-12  1:56   ` Keith Owens
2001-11-12  8:30     ` Kai Germaschewski
2001-11-13 21:41       ` Thomas Hood [this message]
2001-11-14  9:25         ` Kai Germaschewski
2001-11-14 10:17           ` David Woodhouse
2001-11-14 15:46             ` Thomas Hood
2001-11-15 13:30               ` [PATCH] parport_pc to use pnpbios_register_driver() #4 Thomas Hood

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=1005687707.21561.14.camel@thanatos \
    --to=jdthood@mail.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.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