From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alessio Sangalli <alesan@manoweb.com>,
Andrew Morton <akpm@osdl.org>,
alan@lxorguk.ukuu.org.uk, penberg@cs.Helsinki.FI,
linux-kernel@vger.kernel.org, ink@jurassic.park.msu.ru,
dtor_core@ameritech.net
Subject: Re: [PATCH] cardbus: revert IO window limit
Date: Fri, 30 Jun 2006 15:19:14 -0400 [thread overview]
Message-ID: <20060630191914.GP32729@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606301200400.12404@g5.osdl.org>
On Fri, Jun 30, 2006 at 12:10:32PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 22 Jun 2006, Alessio Sangalli wrote:
> >
> > # /sbin/lspci -vvx
> > 00:00.0 Host bridge: Intel Corp. 82440MX Host Bridge (rev 01)
> > Subsystem: Compaq Computer Corporation: Unknown device 000d
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> > Latency: 64
> > 00: 86 80 94 71 06 00 00 22 01 00 00 06 00 40 80 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 11 0e 0d 00
> > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> Ok. We don't actually have any quirks at all for the 82440MX, and that's
> almost certainly _not_ because it doesn't do something strange (all Intel
> host bridges have magic IO ranges), but simply because we haven't hit it
> yet.
>
> And I can't find the docs for the PCI config space for that dang thing.
>
> I bet that there's some magic SMBus IO-range that the 440MX decodes using
> a special magic config setting.
>
> Has anybody found the config space docs for the 82440MX?
http://www.codemonkey.org.uk/cruft/440/
There's an assortment of docs for the other flavour Intel PCIsets from
that era in the same dir.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-30 19:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 6:48 [PATCH] cardbus: revert IO window limit Pekka J Enberg
2006-06-22 7:11 ` Andrew Morton
2006-06-22 7:53 ` Alessio Sangalli
2006-06-22 11:35 ` Alan Cox
2006-06-22 16:18 ` Linus Torvalds
2006-06-22 16:36 ` Andrew Morton
2006-06-22 17:07 ` Linus Torvalds
2006-06-22 20:01 ` Alessio Sangalli
2006-06-22 21:27 ` Alessio Sangalli
2006-06-30 4:34 ` Pekka Enberg
2006-06-30 19:10 ` Linus Torvalds
2006-06-30 19:19 ` Dave Jones [this message]
2006-06-30 19:26 ` Dave Jones
2006-06-30 22:15 ` Linus Torvalds
2006-06-22 16:16 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 22:03 Daniel Ritz
2006-06-30 22:18 ` Linus Torvalds
2006-06-30 23:09 ` Daniel Ritz
2006-06-30 23:21 ` Linus Torvalds
2006-07-05 6:56 ` Pekka J Enberg
2006-07-12 7:55 ` Alessio Sangalli
2006-07-12 15:18 ` Linus Torvalds
2006-07-13 6:29 ` Alessio Sangalli
2006-07-12 7:29 ` Alessio Sangalli
2006-07-12 6:54 ` Alessio Sangalli
2006-07-05 18:29 Mallick, Asit K
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=20060630191914.GP32729@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alesan@manoweb.com \
--cc=dtor_core@ameritech.net \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
--cc=torvalds@osdl.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