public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: corentincj@iksaif.net, acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: eeepc: rfkill on 900A defunct
Date: Wed, 24 Nov 2010 14:57:50 +0000	[thread overview]
Message-ID: <20101124145750.GA32033@srcf.ucam.org> (raw)
In-Reply-To: <4CED26EF.5000109@suse.cz>

On Wed, Nov 24, 2010 at 03:53:35PM +0100, Jiri Slaby wrote:

> but without hotplug support (pciehp cannot be bound to it). However the
> eeepc-laptop driver expects the wifi on the 1st bus (pci_find_bus(0,
> 1)), so it operates on a NIC on this machine instead of wifi.

Yeah, this really needs to be fixed. We need to shift this code out of 
eeepc-laptop and just have the PCI core handle it - that is, if we get a 
hotplug notification, we need to rescan the slot even if we don't have a 
hotplug driver bound to it. Let me look into that.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-11-24 14:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 14:53 eeepc: rfkill on 900A defunct Jiri Slaby
2010-11-24 14:57 ` Matthew Garrett [this message]
2010-11-24 20:18 ` Matthew Garrett
2010-11-26 13:01   ` Woody Suwalski
2010-12-13 10:19   ` Jiri Slaby
2011-02-28  9:49   ` Jiri Slaby
2011-03-08 10:06     ` Jiri Slaby
2011-03-08 10:22       ` Corentin Chary
2011-03-08 10:51         ` Jiri Slaby
2011-03-09 12:50           ` Woody Suwalski
2011-04-19 13:53             ` [ping] " Jiri Slaby

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=20101124145750.GA32033@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentincj@iksaif.net \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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