From: Marc Zyngier <mzyngier@freesurf.fr>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EISA & sysfs.
Date: Wed, 18 Feb 2004 10:42:49 +0100 [thread overview]
Message-ID: <wrpfzd87mg6.fsf@panther.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20040217235431.GF6242@redhat.com> (Dave Jones's message of "Tue, 17 Feb 2004 23:54:31 +0000")
>>>>> "Dave" == Dave Jones <davej@redhat.com> writes:
Dave> Wouldn't it make sense to have eisa_driver_register() check that the
Dave> root EISA bus actually got registered, and if not, -ENODEV
Dave> immediately ?
Most of the time, the bus driver kicks in *after* the device driver is
registered to the EISA framework (eisa is second to last in the driver
list, so if the driver is built-in, it is guaranted to init before the
root driver has a chance to discover the bus).
So, returning -ENODEV immediatly in this case prevents you from using
any built-in EISA driver. A possible solution to this problem would be
to move eisa just after the pci init (and even that would cause some
trouble, because the virtual_root driver would register before the
parisc root driver has a chance to be probed...).
So yes, this sucks, but I can't come up with a better solution...
Regards,
M.
--
Places change, faces change. Life is so very strange.
next prev parent reply other threads:[~2004-02-18 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 23:54 Dave Jones
2004-02-18 9:42 ` Marc Zyngier [this message]
2004-02-18 11:16 ` Dave Jones
2004-02-18 15:24 ` Marc Zyngier
2004-02-18 15:40 ` Dave Jones
2004-02-18 15:53 ` Dave Jones
2004-02-18 16:12 ` Marc Zyngier
2004-02-18 17:23 ` Bartlomiej Zolnierkiewicz
2004-02-18 18:01 ` Greg KH
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=wrpfzd87mg6.fsf@panther.wild-wind.fr.eu.org \
--to=mzyngier@freesurf.fr \
--cc=davej@redhat.com \
--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®