* parport initialisation
@ 2001-04-09 12:13 Bjorn Wesen
2001-04-09 13:38 ` Tim Waugh
0 siblings, 1 reply; 2+ messages in thread
From: Bjorn Wesen @ 2001-04-09 12:13 UTC (permalink / raw)
To: linux-kernel
Hi,
regarding drivers/parport/*
is there any particular reason as to why the different parport drivers
aren't initialized using module_init() ? Like weird init order
dependencies and stuff.
Looking at parport_init itself (which has hardcoded init calls to the
different drivers right now) it does not look like it does anything
particularly special except some proc filesystem registering.
Is it just because nobody has gotten around to "fixing" it or is there a
deeper reason ?
Regards
Bjorn
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: parport initialisation
2001-04-09 12:13 parport initialisation Bjorn Wesen
@ 2001-04-09 13:38 ` Tim Waugh
0 siblings, 0 replies; 2+ messages in thread
From: Tim Waugh @ 2001-04-09 13:38 UTC (permalink / raw)
To: Bjorn Wesen; +Cc: linux-kernel
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-04-09 13:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-09 12:13 parport initialisation Bjorn Wesen
2001-04-09 13:38 ` Tim Waugh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox