From: Jeff Lessem <Jeff.Lessem@Colorado.EDU>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
Date: Sat, 24 Feb 2001 02:41:51 -0700 [thread overview]
Message-ID: <200102240941.CAA09708@ibg.colorado.edu> (raw)
In-Reply-To: Your message of Fri, 23 Feb 2001 09:48:04 PST.
In-Reply-To: <Pine.LNX.4.10.10102230938360.20762-100000@penguin.transmeta.com>
In your message of: Fri, 23 Feb 2001 09:48:04 PST, you write:
>The much more likely cause is the "magic registers" for the Texas
>Instruments PCI1225, namely
>
> works broken
>
> 81: b0 90
> a8: 11 10
>
>Although it worries me a bit that your second controller also seems to
>have differences in the BridgeCtl thing (16bInt).
>
>Can you try if a broken setup is fixed by doing a
>
> setpci -s 00.04.0 81.b=b0
> setpci -s 00.04.0 a8.b=11
> setpci -s 00.04.1 81.b=b0
> setpci -s 00.04.1 81.b=11
I ran setpci -s 00:04.0 81.b=b0, etc., but it didn't make any
difference. Checking with lspci -vvxxx after running setpci it
appears that register 81 and a8 have stayed at 90 and 10 despite
setpci running without an error, using -G and -v setpci claims to be
running through /proc/bus/pci and adjusting the appropriate location.
Either I am making a fundamental error (yes, I am running it as root)
or the changes simply don't matter.
>Also, how much memory does this machine have? That "13ff0000" does worry
>me a bit..
The comptuer has 320MB. At this point I am ready to conclude that the
computer is broken in some way, because nobody else with an Inspiron
5000e that I have heard from has anything like this problem.
I really appreciate the help everybody is providing with what is
really only an annoyance, and I wouldn't have even brought it to the
attention of linux-kernel, except that something that changed between
2.2.17 and 2.4.x has produced a regression in functionality. If
anybody thinks it would be useful, I would be willing to do a binary
search between 2.2.17 and 2.4.2 to find out at which release things
stopped being setup correctly.
--
Jeff Lessem.
next prev parent reply other threads:[~2001-02-24 9:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 7:18 Jeff Lessem
[not found] ` <000201c09d0c$d53a73c0$25040a0a@zeusinc.com>
2001-02-23 3:27 ` Jeff Lessem
2001-02-23 4:45 ` Tom Sightler
2001-02-23 7:01 ` Barry K. Nathan
2001-02-23 8:40 ` Brad Douglas
[not found] ` <200102230340.TAA19644@penguin.transmeta.com>
2001-02-23 4:06 ` Jeff Lessem
2001-02-23 4:37 ` Linus Torvalds
2001-02-23 5:34 ` Jeff Lessem
2001-02-23 17:48 ` Linus Torvalds
2001-02-24 9:41 ` Jeff Lessem [this message]
2001-02-24 13:36 ` Linus Torvalds
2001-02-24 15:54 ` Philipp Rumpf
2001-02-24 17:25 ` Jeff Lessem
2001-02-24 17:55 ` Philipp Rumpf
2001-02-24 18:36 ` Jeff Lessem
2001-02-24 22:28 ` Tom Sightler
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=200102240941.CAA09708@ibg.colorado.edu \
--to=jeff.lessem@colorado.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®