From: Tim Waugh <twaugh@redhat.com>
To: Philip Blundell <philb@gnu.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: parport_pc tries to load parport_serial automatically
Date: Tue, 26 Jun 2001 20:50:54 +0100 [thread overview]
Message-ID: <20010626205054.J7663@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106260308100.1730-100000@freak.distro.conectiva> <20010626102303.K7663@redhat.com> <twaugh@redhat.com> <E15Ex7I-0008TV-00@kings-cross.london.uk.eu.org>
In-Reply-To: <E15Ex7I-0008TV-00@kings-cross.london.uk.eu.org>; from philb@gnu.org on Tue, Jun 26, 2001 at 06:59:11PM +0100
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Tue, Jun 26, 2001 at 06:59:11PM +0100, Philip Blundell wrote:
> This would be a bit bad, because it would require people to guess
> whether they might have a card that parport_serial can drive and/or
> try loading the module to see what happens.
Not necessarily. The module has a PCI device table, so a user-space
utility can figure it out and adjust /etc/modules.conf accordingly.
> I guess one option would be for parport_pc to somehow "know" what cards are
> really multi-I/O ones, and only load parport_serial when it will be able to
> find something to do. Doesn't seem all that appealing though.
Replace parport_pc's "knowledge" with parport_serial's PCI device
table and a user-space utility, and that's kind of what I had in
mind.
> If you do that then the code will effectively be there all the time,
> even when it's not needed. You might as well just compile it in to
> parport_pc. To be honest, there isn't all that much of it so maybe
> this wouldn't be such a bad idea.
Perhaps.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-06-26 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 6:17 parport_pc tries to load parport_serial automatically Marcelo Tosatti
2001-06-26 9:23 ` Tim Waugh
2001-06-26 12:55 ` Simon Huggins
2001-06-26 12:56 ` Simon Huggins
2001-06-26 13:37 ` Keith Owens
2001-06-26 13:53 ` Tim Waugh
2001-06-26 14:34 ` Keith Owens
2001-06-26 13:30 ` Marcelo Tosatti
2001-06-26 15:21 ` Tim Waugh
2001-06-27 10:32 ` Marcelo Tosatti
2001-07-04 12:36 ` Tim Waugh
2001-07-04 12:38 ` Alan Cox
2001-07-04 12:38 ` Tim Waugh
2001-06-26 17:59 ` Philip Blundell
2001-06-26 19:50 ` Tim Waugh [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=20010626205054.J7663@redhat.com \
--to=twaugh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.