All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Sheard <greg@ecsc.co.uk>
To: Martin Mares <mj@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Intel chipset development documents
Date: 03 Nov 2001 11:12:04 +0000	[thread overview]
Message-ID: <1004785924.23134.8.camel@lemsip> (raw)
In-Reply-To: <20011103120455.B676@ucw.cz>
In-Reply-To: <1004721050.20610.7.camel@lemsip> <20011102183829.A31651@atrey.karlin.mff.cuni.cz> <1004735023.21120.12.camel@lemsip>  <20011103120455.B676@ucw.cz>

On Sat, 2001-11-03 at 11:04, Martin Mares wrote:
> Hello!
> 
> > I already have the configuration type down (it's 1), but the 430VX and
> > also the VIA 585 seem only to report host bridges. I'm unable to spot
> > the piece of code which does different PCI-related things for these
> > chipsets in the kernel. Does anybody know if a workaround is applied?
> 
> It's quite strange -- can you send me 'lspci -vvx -MH1' output, please?
> 

Well I would, but with the assistance of Martin Bligh from IBM I've
found my bug. Major thinko - there seems to be something funky in the
440BX chipset that allowed me to do something like:

  outl(PCI_CONF1_ADDRESS(bus, 0, dev, fn), 0xCF8);

but still returned the correct PCI information! The problem was that I'd
done my own inline for the addressing and, since I wasn't using reg, I'd
left it out. Somehow I'd managed to shift the important stuff around...

Thanks to everyone who's offered suggestions and documents, it's much
appreciated.

Cheers,
Greg.


  reply	other threads:[~2001-11-03 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 17:10 [OT] Intel chipset development documents Greg Sheard
2001-11-02 17:38 ` Martin Mares
2001-11-02 21:03   ` Greg Sheard
2001-11-02 22:11     ` Charles Marslett
2001-11-06 18:22       ` Maciej W. Rozycki
2001-11-03 11:04     ` Martin Mares
2001-11-03 11:12       ` Greg Sheard [this message]
2001-11-02 18:03 ` Marc Haber
2001-11-02 20:31   ` Robert Love
2001-11-02 21:07     ` Greg Sheard
2001-11-02 21:09       ` Robert Love
2001-11-06 18:18 ` Maciej W. Rozycki

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=1004785924.23134.8.camel@lemsip \
    --to=greg@ecsc.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.