From: Tim Waugh <twaugh@redhat.com>
To: Bjorn Wesen <bjorn@sparta.lu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: parport initialisation
Date: Mon, 9 Apr 2001 14:38:54 +0100 [thread overview]
Message-ID: <20010409143854.K1136@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010409141107.9826A-100000@medusa.sparta.lu.se>
In-Reply-To: <Pine.LNX.3.96.1010409141107.9826A-100000@medusa.sparta.lu.se>; from bjorn@sparta.lu.se on Mon, Apr 09, 2001 at 02:13:10PM +0200
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
On Mon, Apr 09, 2001 at 02:13:10PM +0200, Bjorn Wesen wrote:
> Is it just because nobody has gotten around to "fixing" it or is there a
> deeper reason ?
There's no deeper reason. But there are dependencies involved:
parport needs to be initialised before any parport lowlevel drivers,
and they need to be initialised before things like lp and ppdev.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-04-09 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 12:13 parport initialisation Bjorn Wesen
2001-04-09 13:38 ` 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=20010409143854.K1136@redhat.com \
--to=twaugh@redhat.com \
--cc=bjorn@sparta.lu.se \
--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