public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristen Accardi <kristen.c.accardi@intel.com>
To: len.brown@intel.com, greg@kroah.com
Cc: linux-acpi@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, mochel@linux.intel.com,
	arjan@linux.intel.com, muneda.takahiro@jp.fujitsu.com,
	pavel@ucw.cz, temnota@kmv.ru
Subject: [patch 0/3] Redesigned Dock Patches
Date: Wed, 12 Apr 2006 15:18:38 -0700	[thread overview]
Message-ID: <1144880318.11215.42.camel@whizzy> (raw)

After getting more laptop/dock combos tested, it's apparent to me that
I need to redesign the dock patches to not exclusively use acpiphp to
handle dock events.  This is because there are dock stations with no
pci on them at all, and it doesn't make sense for the apci pci hotplug
driver to handle the dock event in this case.  So, I moved the dock
event handling to the acpi directory, in a separate driver called "dock".
The acpiphp driver will still handle hotplugging any new pci devices
(including dock bridges) that will be need to be inserted after a dock
event.

To use these driver, you will need to select CONFIG_ACPI_DOCK in the
.config file, and make sure if you are using an IBM laptop that you have
NOT selected the option to allow ibm_acpi to handle the docking events.  Then,
you modprobe dock as well as acpiphp.

Please take a look at these patches and test them if you can.  Every time
another person tests the dock patches I find another combination I didn't
think of :).  Thanks for your feedback, and thanks to all the testers who
are helping make the dock patches work for as many systems as we can.

Kristen

--

                 reply	other threads:[~2006-04-12 22:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1144880318.11215.42.camel@whizzy \
    --to=kristen.c.accardi@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@linux.intel.com \
    --cc=muneda.takahiro@jp.fujitsu.com \
    --cc=pavel@ucw.cz \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=temnota@kmv.ru \
    /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