mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: PCI resource unavailable on mips
Date: Fri, 14 Dec 2007 13:32:40 -0500	[thread overview]
Message-ID: <1197657160.3420.11.camel@microwave.infinitevideocorporation.com> (raw)
In-Reply-To: <20071214093945.GA25186@linux-mips.org>


> 
> Odd.  I knew the resource allocation stuff has it's issues for some
> non-trivial configuration but that one is a new one.  Which makes me
> wonder if your platform runs the PCI code in probe-only mode where it
> will not actually assign resources but only inherit the whole PCI setup
> except interrupt routing from the firmware.
> 
> What MIPS platform do you use?  I'd like to take a look at its PCI setup
> code.
> 

I am using the MDS 810 STB as provided by MDS
(http://www.mds.com/products/product.asp?prod=MDS-810). The kernel and
entire environment (except my driver) was set up by MDS. uname output is
as follows.

 # uname -a
Linux 10.41.13.87 2.6.19PNX8550 #1 Wed Nov 21 14:55:52 EST 2007 mips
unknown

If I can provide additional information for you I'd be happy to help.

Thanks,
Jon


  reply	other threads:[~2007-12-14 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 14:56 Jon Dufresne
2007-12-14  9:39 ` Ralf Baechle
2007-12-14 18:32   ` Jon Dufresne [this message]
2007-12-14 21:12   ` Jon Dufresne
2007-12-16 22:46     ` Ralf Baechle
2007-12-17 15:16       ` Jon Dufresne
2007-12-17 15:47         ` Sergei Shtylyov
2007-12-18 18:11           ` Jon Dufresne
     [not found] <fa.vbvzhsk+kDPCopbmajO8EsxAnKE@ifi.uio.no>
2007-12-13 23:38 ` Robert Hancock
2007-12-18 18:40   ` Jon Dufresne

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=1197657160.3420.11.camel@microwave.infinitevideocorporation.com \
    --to=jon.dufresne@infinitevideocorporation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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
all inboxes | Powered by JetHome®