mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Huggins <huggie@earth.li>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: parport_pc tries to load parport_serial automatically
Date: Tue, 26 Jun 2001 14:55:31 +0200	[thread overview]
Message-ID: <20010626145531.J3776@paranoidfreak.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0106260308100.1730-100000@freak.distro.conectiva> <20010626102303.K7663@redhat.com>
In-Reply-To: <20010626102303.K7663@redhat.com>

Hi lkml,

On Tue, Jun 26, 2001 at 10:23:03AM +0100, Tim Waugh wrote:
> > If the initialization of parport_serial fails, we obviously get an
> > error message, which is really annoying:
> [This is different to the issue that is fixed in the -ac tree about
> parport_serial getting probed for even when disabled in config.]

> The idea was that people who have multi-IO cards but don't know what
> modules are can have things Just Work: parport_serial gets loaded
> automagically and detects their cards for them.  But yes, the flip
> side is that people who _don't_ have multi-IO cards are going to get
> that error.

> - change parport_pc so that it doesn't request parport_serial at
>   init.  In this case, how will parport_serial get loaded at all?
>   Perhaps with some recommended /etc/modules.conf lines (perhaps
>   parport_lowlevel{1,2,3,...})?

Can't people who have such things just put:
pre-install insmod parport-serial
post-rm rmmod parport-serial
in modules.conf?

> - people who get the error and don't like it can put 'alias
>   parport_serial off' in /etc/modules.conf.  Not especially pleasant,
>   I guess.

That's the opposite of the above I suppose.

> - parport_serial could be made to initialise successfully even if it
>   doesn't see any devices that it can drive.

That sounds icky IMHO.


Simon.

-- 
UK based domain, email and web hosting ***/     "An excellent suggestion /*
http://www.blackcatnetworks.co.uk/     **/     sir, with only two minor /**
sales@blackcatnetworks.co.uk           */          flaws...." - Kryten /***
Black Cat Networks                     /                              /****

  reply	other threads:[~2001-06-26 12:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  6:17 Marcelo Tosatti
2001-06-26  9:23 ` Tim Waugh
2001-06-26 12:55   ` Simon Huggins [this message]
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

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=20010626145531.J3776@paranoidfreak.co.uk \
    --to=huggie@earth.li \
    --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

all inboxes | Powered by JetHome®