From: "Max T. Woodbury" <max.teneyck.woodbury@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: PCI configuration changes getting lost.
Date: Thu, 15 Jul 2004 20:25:50 +0100 [thread overview]
Message-ID: <40F693EE.5D65D02F@verizon.net> (raw)
I'm having trouble with an old Thinkpad 760 ED.
The BIOS puts junk (0xFF) in the INTERRUPT_LINE register of the PCMCIA
configuration registers. I can put the correct value (0x05) in with
'setpci', but the information is not propagated to the /proc space.
The information is not preserved after an 'init 6'.
(There is at least one other BIOS induced problem with this machine
and PCI configuration registers but it is a bit less serious. I do
have the latest BIOS.)
What would be involved in updating the /proc information when 'setpci'
is used to change the configuration?
Does the other pci 'fixer' 'pcitweak' do a better job?
[Don't remove PCI from the subject line. I'm using it to keep track
of interesting things in this otherwise very noisy mailing list.]
max@mtew.isa-geek.net
next reply other threads:[~2004-07-15 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 19:25 Max T. Woodbury [this message]
2004-07-15 19:49 ` PCI configuration changes getting lost Martin Mares
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=40F693EE.5D65D02F@verizon.net \
--to=max.teneyck.woodbury@verizon.net \
--cc=linux-kernel@vger.kernel.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