From: Adrian Cox <adrian@humboldt.co.uk>
To: daz@tiscali.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exception on host-PCI-bridge master-abort
Date: 10 Nov 2003 09:34:16 +0000 [thread overview]
Message-ID: <1068456857.6750.22.camel@newt> (raw)
In-Reply-To: <3FAA85C400002BAB@mail-6.tiscali.it>
On Fri, 2003-11-07 at 19:34, daz@tiscali.it wrote:
> I'm developing i386 linux drivers for a custom PCI card basically built
> on
> a programmable FPGA.
>
> Every time I re-program the FPGA (without re-booting the PC), the PCI
> configuration regs of the card are resetted, which makes memory and I/O
> aperture of the card disappearing from the PCI bus.
>
> By calling pci_restore_state() I restore the proper configuration, but
> unfortunately sometimes I'm not fast enough, and the PC issues a read or
> write requests when the card is still wrong configured.
> In such bad situation the PC freezes!
I've dealt with cards like that, but without that sort of problem.
Here's some things to think about:
1) Linux should not issue read or write requests to PCI devices
randomly. If the request is directed to your card, are you sure that it
isn't coming from your own driver code? If so, fix your driver.
2) If the fatal access is to another device, then does your device pass
through an intermediate state where it corrupts accesses to other cards
on the same bus? If so, you need to use a PCI-PCI bridge to put it on a
bus by itself.
3) If it's a new custom card, worry about electrical issues. Maybe the
FPGA configuration fails sometimes.
- Adrian Cox
http://www.humboldt.co.uk/
next prev parent reply other threads:[~2003-11-10 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 19:34 Exception on host-PCI-bridge master-abort daz
2003-11-10 9:34 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-07 11:45 daz
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=1068456857.6750.22.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=daz@tiscali.it \
--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 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.