From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: pci: add to global list before sysfs?
Date: Sat, 5 Apr 2008 20:27:09 +0200 [thread overview]
Message-ID: <20080405202709.2cd03212@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080405171209.GA28388@suse.de>
On Sat, 5 Apr 2008 10:12:09 -0700
Greg KH <gregkh@suse.de> wrote:
> On Sat, Apr 05, 2008 at 06:55:01PM +0200, Pierre Ossman wrote:
> > If I do this threaded, I'd have to return success to the driver core
> > and then act like a possum later.
>
> Yes.
>
> > Doable, but not very clean.
>
> Hey, take it up with the hardware designers compensating for an
> "unclean" operating system :)
>
I have. And unfortunately that other operating system is just too big
of a market to ignore. :/
This is a cooperating vendor though, which is why I'm trying to put a
bit more extra effort into actually getting their devices fully
supported. Telling them to ditch Windows support is asking too much.
Anyway, a big part of my reluctance to go this route is that this chip
is just one of many the driver supports. So I'm not thrilled to do some
funky architecture for this device as it'll most certainly cause me
pain for the others...
> I don't think that a time-out would be a big deal, it shouldn't be very
> long (a second or two). Also note that all distros would not have this
> problem as they do pci discovery first, and then start loading all of
> the modules in the initramfs after the pci tree has been properly
> scanned. So the very large majority of users would not have a problem.
>
> Or are you doing this on an embedded system?
>
No, it's primarily desktop. But these chips are available as
ExpressCards, so I'm trying to get them to work when hot-plugged as
opposed to when permantently wired into the machine.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2008-04-05 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 17:13 Pierre Ossman
2008-04-04 21:01 ` Greg KH
2008-04-05 9:57 ` Pierre Ossman
2008-04-05 15:53 ` Greg KH
2008-04-05 16:55 ` Pierre Ossman
2008-04-05 17:12 ` Greg KH
2008-04-05 18:27 ` Pierre Ossman [this message]
2008-04-08 3:41 ` Greg KH
2008-04-13 12:33 ` Pierre Ossman
2008-04-13 17:51 ` Greg KH
2008-04-13 21:37 ` Benjamin Herrenschmidt
2008-04-14 8:35 ` Pierre Ossman
2008-04-14 8:57 ` Benjamin Herrenschmidt
2008-04-14 8:58 ` Benjamin Herrenschmidt
2008-04-14 10:58 ` Pierre Ossman
2008-04-13 21:35 ` Benjamin Herrenschmidt
2008-04-15 19:13 ` Greg KH
2008-04-15 21:53 ` Benjamin Herrenschmidt
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=20080405202709.2cd03212@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=gregkh@suse.de \
--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®