Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: Gill Robles-Thome <gill.robles@exterity.co.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: No PCI memory response
Date: Tue, 05 Apr 2005 09:27:40 -0700	[thread overview]
Message-ID: <4252BC7C.6060806@embeddedalley.com> (raw)
In-Reply-To: <CEA5455795C8AA44AA1E18EF32379B2105CF93@exterity-serv1.Exterity.local>

Gill Robles-Thome wrote:
> ...we found the cause of the problem!  Need to select "Support for
> 64-bit physical address space" option!

That option should be in the defconfig already - was it not?

I should just hardcode that option and get it over with.

Pete

> 
> Gill
> 
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Gill Robles-Thome
> Sent: 05 April 2005 09:11
> To: linux-mips@linux-mips.org
> Subject: RE: No PCI memory response
> 
> 
> Hi -
> 
> I'm certainly seeing what looks like random reads...however, is the
> static bus controller actually implicated in PCI bus operations?  The
> product brief for the Au1100 doesn't mention PCI, so I'm not sure that
> we're looking at the same problem.
> 
> Thanks,
> Gill
> 
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Ulrich Eckhardt
> Sent: 04 April 2005 15:53
> To: linux-mips@linux-mips.org
> Subject: Re: No PCI memory response
> 
> 
> Gill wrote:
> 
>>Can anyone help?  We're trying to talk to a RealTek RTL8139 device
>>across the PCI bus, and, although linux can access configuration 
>>registers on the device, it does not access memory space correctly, 
>>and we are unable to read back any sensible values from the RTL8139 
>>registers.
>>
>>We are using the latest 2.6 linux on an Alchemy DB1550 board.
> 
> 
> Random reads, discarded data after writing? I had the same problem and
> solved 
> it by simply configuring the static bus controller of my Au1100 properly
> (of 
> which before I didn't even know it existed...).
> 
> hth
> 
> Uli
> 
> 
> 
> 
> 
> 

  parent reply	other threads:[~2005-04-05 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 15:28 No PCI memory response Gill Robles-Thome
2005-04-05 15:28 ` Gill Robles-Thome
2005-04-05 16:27 ` Pete Popov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05  8:11 Gill Robles-Thome
2005-04-05  8:11 ` Gill Robles-Thome
2005-04-04 14:44 Gill
2005-04-04 14:44 ` Gill
2005-04-04 14:52 ` Ulrich Eckhardt

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=4252BC7C.6060806@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=gill.robles@exterity.co.uk \
    --cc=linux-mips@linux-mips.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