public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Mike Mohr <akihana@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: expresscard hotplug not working
Date: Mon, 31 Aug 2009 09:11:39 -0400	[thread overview]
Message-ID: <4A9BCC0B.1010107@rtr.ca> (raw)
In-Reply-To: <20090831125609.GA11121@srcf.ucam.org>

Matthew Garrett wrote:
> On Mon, Aug 31, 2009 at 08:45:47AM -0400, Mark Lord wrote:
> 
>> With acpiphp loaded, hotplug works on the ExpressCard slot
>> of my Dell i9400 notebook.  Well, it *mostly* works.
> 
> Ok, that's good.
> 
>> The part that is still b0rked is that inserted cards get
>> "forgotten" about over suspend/resume (RAM) cycles.
> 
> I can entirely believe that that's broken. Thanks, I'll take a look at that.
..

Great!  Email me directly (or CC: me) if/when you'd like some more testing.

Another thing that could be a factor here, is that neither method
(acpiphp or pciehp) seems "automatic".  The user has to know to load
one or the other module, or at least manually add them to /etc/modules.

This could account for some reports of the mechanism failing.

Shouldn't one or the other module be loaded automatically somehow
when a system has hotpluggable slots?

Probably a chicken-and-egg issue, I suppose, or something for a distro to fuss over.

Cheers

  reply	other threads:[~2009-08-31 13:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  1:17 expresscard hotplug not working Mike Mohr
2009-08-26  6:45 ` Greg KH
2009-08-26 18:19   ` Mike Mohr
2009-08-26 21:02     ` Greg KH
2009-08-27 12:52 ` Mark Lord
2009-08-27 13:18   ` Mark Lord
2009-08-30 22:55   ` Matthew Garrett
2009-08-31 12:29     ` Mark Lord
2009-08-31 12:45       ` Mark Lord
2009-08-31 12:56         ` Matthew Garrett
2009-08-31 13:11           ` Mark Lord [this message]
2009-08-31 13:15             ` Matthew Garrett

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=4A9BCC0B.1010107@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akihana@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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