linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Neil Wilson" <nwilson@airspan.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: forcing pci device start address ?
Date: Sat, 30 Mar 2002 17:14:24 -0000	[thread overview]
Message-ID: <001201c1d80e$57e12840$479b883e@m5axc> (raw)


Hi,

We have a new 7450/107 board that I have got to boot and run 2.4.17.  The
hardware designer has got some non-standard pci devices ie, a large fpga
 that lives in pci space but does not have a configuration register and also
 some standard pci devices like the AMD79C973 ethernet controller.

 Is it possible to force the start address for the devices to be at specific
 addresses as determined by the hardware map using the existing pci
 controller code ?  An example is the ethernet controller which is at
 0xe0000000 in the hardware map yet when it it is detected during the pci
 probing the pcnet32 driver has its ioaddr set to somewhere like 0xfbeffxxx.


I am looking through the other setups in the platforms directory and trying
 to search the archives but this pci is all a bit of a mystery to me a the
 momment.

 Thanks for any help/comments.

 Neil


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-03-30 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-30 17:14 Neil Wilson [this message]
2002-03-30 23:24 ` forcing pci device start address ? Matt Porter
  -- strict thread matches above, loose matches on Subject: below --
2002-03-31 20:02 Neil Wilson
2002-04-01  4:04 ` Matt Porter
2002-04-01 20:21 Neil Wilson
2002-04-01 20:35 ` Matt Porter

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='001201c1d80e$57e12840$479b883e@m5axc' \
    --to=nwilson@airspan.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nwilsn@airspan.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;
as well as URLs for NNTP newsgroup(s).