From: Michael Buesch <mb@bu3sch.de>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: "Török Edvin" <edwintorok@gmail.com>,
zambrano@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, power@bughost.org
Subject: Re: [PATCH] b44: power down PHY when interface down
Date: Sun, 1 Jul 2007 12:23:16 +0200 [thread overview]
Message-ID: <200707011223.17235.mb@bu3sch.de> (raw)
In-Reply-To: <20070630231734.GF2553@xi.wantstofly.org>
On Sunday 01 July 2007 01:17:34 Lennert Buytenhek wrote:
> More or less. You can't add the resistances like that, since the
> bus isolation chip buffers the IDSEL signal, but it is correct that
> if the host's IDSEL resistor is larger than a certain value, the
> combination of the resistive coupling of IDSEL plus the extra buffer
> in the isolator might be causing the IDSEL input on the 'guest' PCI
> board to assert too late (or not assert at all), causing config
> accesses to fail.
>
> (This also depends on the specific 'guest' PCI board used, as you
> noted, due to differing IDSEL trace lengths/capacitances and input
> pin capacitances on different PCI boards. Also, it might work at
> 33 MHz but not work at 66 MHz, etc.)
It doesn't work on any of my boards :(
> If you feel adventurous, you could try to hack around this by
> figuring out which AD[31:16] line this PCI slot's IDSEL line is
> resistively coupled to (depends on the slot), and then adding
> another parallel resistor on the board itself to make the bus
> isolator's input buffer charge faster. Note that this does
> increase the load on that specific AD[] line, which might cause
> other funny effects.
Well, but how to find out to which address line it's connected to?
Pretty hard to follow the PCB traces, especially since it's
multilayered.
--
Greetings Michael.
next prev parent reply other threads:[~2007-07-01 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 11:47 [PATCH] b44: power down PHY when interface down Török Edvin
2007-06-30 12:05 ` Matthew Garrett
2007-06-30 14:44 ` Arjan van de Ven
2007-06-30 15:19 ` Matthew Garrett
2007-06-30 15:25 ` Lennert Buytenhek
2007-07-01 13:02 ` Török Edvin
2007-06-30 16:42 ` PM policy, hotplug, power saving (was Re: [PATCH] b44: power down PHY when interface down) Jeff Garzik
2007-06-30 18:10 ` Stephen Hemminger
2007-06-30 18:31 ` PM policy, hotplug, power saving and WoL Henrique de Moraes Holschuh
2007-07-01 4:51 ` PM policy, hotplug, power saving (was Re: [PATCH] b44: power down PHY when interface down) Kyle Moffett
[not found] ` <4354d3270706300447ladcda4by987b1f87963112f9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-30 12:13 ` [PATCH] b44: power down PHY when interface down Stephen Hemminger
2007-07-01 12:49 ` Török Edvin
2007-07-01 12:55 ` Michael Buesch
2007-06-30 21:53 ` Michael Buesch
2007-06-30 22:03 ` Lennert Buytenhek
2007-06-30 22:24 ` Michael Buesch
2007-06-30 23:17 ` Lennert Buytenhek
2007-07-01 10:23 ` Michael Buesch [this message]
2007-07-01 15:00 ` Lennert Buytenhek
2007-07-01 15:29 ` Michael Buesch
2007-07-01 20:20 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2007-07-01 13:25 Török Edvin
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=200707011223.17235.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=buytenh@wantstofly.org \
--cc=edwintorok@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=power@bughost.org \
--cc=zambrano@broadcom.com \
/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;
as well as URLs for NNTP newsgroup(s).