From: Pavel Machek <pavel@ucw.cz>
To: dtor_core@ameritech.net
Cc: Kristen Accardi <kristen.c.accardi@intel.com>,
linux-kernel@vger.kernel.org, greg@kroah.com,
pcihpd-discuss@lists.sourceforge.net, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: [Pcihpd-discuss] Re: [patch 0/4] Hot Dock/Undock support
Date: Wed, 18 Jan 2006 14:51:16 +0000 [thread overview]
Message-ID: <20060118145116.GA2757@ucw.cz> (raw)
In-Reply-To: <d120d5000601190723k3339f92eufc3bc1d0832f6058@mail.gmail.com>
Hi!
> > > Hope this helps.
> > > Pavel
> >
> >
> > so the problem that I see is that this dsdt defines two separate dock
> > devices, one outside the scope of pci, and one within it. The one
> > outside the scope of pci defines the _EJ0 and _DCK methods. So, when
> > acpiphp loads, it scans the pci slots for ejectable slots, finds none
> > (because _EJ0 is defined in the dock device that is outside the scope of
> > pci) and exits. This dsdt is different from the others I've used in
> > that most of them define all methods related to docking under the actual
> > dock bridge (within the scope of pci). perhaps some acpi people can
> > shed some light on the best way to handle this - otherwise I'm sure I
> > can hack something up that will be less than acceptable :).
> >
>
> ACPI has (had?) a braindamage - it drops devices that do not present
> when initially scanning ACPI namespace. So if you boot undocked - too
> bad. Driver won't ever see your docking station.
I think I booted docked....
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-19 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 0:56 [patch 0/4] Hot Dock/Undock support Kristen Accardi
2006-01-18 12:16 ` Pavel Machek
2006-01-18 13:04 ` Pavel Machek
2006-01-18 18:42 ` [Pcihpd-discuss] " Kristen Accardi
2006-01-18 19:45 ` Pavel Machek
2006-01-18 21:06 ` Kristen Accardi
2006-01-18 21:47 ` Matthew Garrett
2006-01-18 22:08 ` Pavel Machek
2006-01-18 22:23 ` Pavel Machek
2006-01-19 0:06 ` Kristen Accardi
2006-01-19 15:23 ` Dmitry Torokhov
2006-01-18 14:51 ` Pavel Machek [this message]
2006-01-20 1:27 ` Kristen Accardi
2006-01-18 20:42 ` Pavel Machek
2006-01-18 21:43 ` Kristen Accardi
2006-01-18 21:11 ` Pavel Machek
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=20060118145116.GA2757@ucw.cz \
--to=pavel@ucw.cz \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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