public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tranchant <mark@tranchant.plus.com>
To: linux-kernel@vger.kernel.org
Subject: Writing to PCI registers before probe?
Date: Tue, 02 Mar 2004 09:46:13 +0000	[thread overview]
Message-ID: <404457E5.10300@tranchant.plus.com> (raw)

I have an old Pentium 100 machine running 2.6.3, with onboard PIIXa 
controller. I'm trying to enable DMA, but the controller doesn't even 
recognize its own IDE interface. Here's the snipped output from lspci:

root@mauve:~# lspci
00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
(other devices)

If I use setpci to write to an appropriate register, the device then 
recognizes its IDE interface if I tell lspci to do a direct access scan:

root@mauve:~# setpci -s 00:07.0 6a.w=0005
root@mauve:~# lspci -H 1
00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
(other devices)

However, the bus has already been scanned, so a straight lspci gives the 
same results as before, and hdparm still can't turn on DMA. Compiling PIIX 
support as a module and insmoding after the setpci makes no difference.

I want to do the register write prior to the bus being scanned. I've seen 
solutions with older kernels, but the bus scan has been significantly 
re-written since then. Would anyone familiar with the 2.6 PCI subsystem 
kindly help me out here? This is a production server, so I don't want too 
much downtime experimenting.

Many thanks,

-- 
Mark.
mark@tranchant.plus.com
http://tranchant.plus.com/



                 reply	other threads:[~2004-03-02  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=404457E5.10300@tranchant.plus.com \
    --to=mark@tranchant.plus.com \
    --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