Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Frank Neuber <frank.neuber@kernelport.de>
To: linux-mips <linux-mips@linux-mips.org>
Subject: (SOLVED) Re: Au1550 with kernel linux-2.6.28.1 PCI Cardbus mappings too large (SOLVED)
Date: Wed, 28 Jan 2009 20:28:24 +0100	[thread overview]
Message-ID: <1233170905.28527.559.camel@t60p> (raw)
In-Reply-To: <1232965296.28527.427.camel@t60p>

Hi,
I found a woking solution to use my pci wired ehci controller on the
au1550 :-)
I did this in drivers/pci/pci.c here is the patch:
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index e491fde..3422ff4 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -29,7 +29,7 @@ int pci_domains_supported = 1;
 #endif
 
 #define DEFAULT_CARDBUS_IO_SIZE                (256)
-#define DEFAULT_CARDBUS_MEM_SIZE       (64*1024*1024)
+#define DEFAULT_CARDBUS_MEM_SIZE       (32*1024*1024)
 /* pci=cbmemsize=nnM,cbiosize=nn can override this */
 unsigned long pci_cardbus_io_size = DEFAULT_CARDBUS_IO_SIZE;
 unsigned long pci_cardbus_mem_size = DEFAULT_CARDBUS_MEM_SIZE;

Because this code is working on i386 with 64 bit memsize we need a
au1550 specific solution. 
I don't know how is the rigth way.

Kind Regards,
 Frank

Am Montag, den 26.01.2009, 11:21 +0100 schrieb Frank Neuber:
> Hello again,
> as I sad I want to use a USB controller wired on the pci bus.
> The EHCI Probe (usb_hcd_pci_probe) fails with "controller already in
> use" error because the request_mem_region gives an error.
> 
> I think the Problem is that the CardBus bridge eat the mem.
> As a refence you can compare the CadrBus mem window on 2.6.28.1 with
> 2.6.16.11.
> At the moment I have no idea how can I fix this resource conflict ...
> 
> I found a pcibios_fixup_bus fuction that reorganize the dev->resource[i]
> values but I'm not sure if this is called during pci init. I'll check
> this now.
> Is there a PCI guru for mips on the list?
> 
> Kind regards,
>  Frank
>  
> Kernel 2.6.28.1 output
> pci 0000:00:0c.0: PME# supported from D1 D3hot D3cold
> pci 0000:00:0c.0: PME# disabled
> pci 0000:00:0c.1: PME# supported from D1 D3hot D3cold
> pci 0000:00:0c.1: PME# disabled
> pci 0000:00:0c.2: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:00:0c.2: PME# disabled
> pci 0000:00:0d.0: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:00:0d.0: PME# disabled
> pci 0000:00:0d.1: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:00:0d.1: PME# disabled
> pci 0000:00:0c.0: BAR 0: can't allocate mem resource
> [0x50000000-0x4fffffff]
> pci 0000:00:0c.1: BAR 0: can't allocate mem resource
> [0x50000000-0x4fffffff]
> pci 0000:00:0d.0: BAR 0: can't allocate mem resource
> [0x50000000-0x4fffffff]
> pci 0000:00:0d.1: BAR 0: can't allocate mem resource
> [0x50000000-0x4fffffff]
> pci 0000:00:0c.2: BAR 0: can't allocate mem resource
> [0x50000000-0x4fffffff]
> pci 0000:00:0d.0: CardBus bridge, secondary bus 0000:01
> pci 0000:00:0d.0:   IO window: 0x001000-0x0010ff
> pci 0000:00:0d.0:   IO window: 0x001400-0x0014ff
> pci 0000:00:0d.0:   PREFETCH window: 0x40000000-0x43ffffff
> pci 0000:00:0d.0:   MEM window: 0x44000000-0x47ffffff
> pci 0000:00:0d.1: CardBus bridge, secondary bus 0000:05
> pci 0000:00:0d.1:   IO window: 0x001800-0x0018ff
> pci 0000:00:0d.1:   IO window: 0x001c00-0x001cff
> pci 0000:00:0d.1:   PREFETCH window: 0x48000000-0x4bffffff
> pci 0000:00:0d.1:   MEM window: 0x4c000000-0x4fffffff
> PCI: Enabling device 0000:00:0d.0 (0000 -> 0003)
> PCI: Enabling device 0000:00:0d.1 (0000 -> 0003)
> 
> 
> Kernel 2.6.16.11 output
> PCI: Bus 1, cardbus bridge: 0000:00:0d.0
>   IO window: 00001000-000010ff
>   IO window: 00001400-000014ff
>   PREFETCH window: 40000000-41ffffff
>   MEM window: 42000000-43ffffff
> PCI: Bus 5, cardbus bridge: 0000:00:0d.1
>   IO window: 00001800-000018ff
>   IO window: 00001c00-00001cff
>   PREFETCH window: 44000000-45ffffff
>   MEM window: 46000000-47ffffff
> PCI: Enabling device 0000:00:0d.0 (0000 -> 0003)
> PCI: Setting latency timer of device 0000:00:0d.0 to 64
> PCI: Enabling device 0000:00:0d.1 (0000 -> 0003)
> PCI: Setting latency timer of device 0000:00:0d.1 to 64
> 
> 

      reply	other threads:[~2009-01-28 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 19:40 Au1550 with kernel linux-2.6.28.1 Frank Neuber
2009-01-24  7:57 ` Manuel Lauss
2009-01-24  8:57   ` Frank Neuber
2009-01-24 23:20     ` Frank Neuber
2009-01-25  8:20       ` Au1550 with kernel linux-2.6.28.1 (SOLVED) Frank Neuber
2009-01-26 10:21         ` Au1550 with kernel linux-2.6.28.1 PCI Cardbus mappings too large Frank Neuber
2009-01-28 19:28           ` Frank Neuber [this message]

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=1233170905.28527.559.camel@t60p \
    --to=frank.neuber@kernelport.de \
    --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