Re: PCI device not working

2012-10-25 Thread Davide
Hi Kumar, On Fri, Oct 05, 2012 at 07:47:24AM -0500, Kumar Gala wrote: > > On Oct 5, 2012, at 3:54 AM, Davide Viti wrote: > > >> On Oct 4, 2012, at 7:24 AM, Davide Viti wrote: > >> > >>> Hi, > >>> it turns out that if define CONFIG_PCI_NOSCAN

Re: PCI device not working

2012-10-31 Thread Davide
th CONFIG_PCI_NOSCAN defined): 0x9000: 0x8048 (not working) -> 0x8003007c (ok) 0x9004: 0x (not working) -> 0x0800 (ok) The register values were obtained with the devmem utility. Thanx very much for your help, Davide [1] http://permalink.gmane.org/gmane.linu

PCI device not working

2012-09-21 Thread Davide Viti
n uboot. I can provide any log (didn't want to post tons of details on the first message) Thanx in advance for your help, regards Davide ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: PCI device not working

2012-09-21 Thread Davide Viti
e04600-ffe04607 : serial thanx for your help, Davide I mean that the kernel detects the first controller and the device attached to it, plus the second controller: the device on the second controller is not detected (same device as the one detected on the first controller) 2012/9/21 Kumar Gala

Re: PCI device not working

2012-09-24 Thread Davide Viti
2012/9/21 Davide Viti > I mean there are two controllers and both of them have a device > "subtended" (both 0x1b65:0xabba). > u-boot can see both devices, linux detects only the device attached to the > first controller. > > Here's the output of lspci and /proc

Re: PCI device not working

2012-09-24 Thread Davide Viti
Hi, does the output I've included show anything wrong or should I post something else to help identifying the cause of the problem? thank you in advance, Davide 2012/9/21 Davide Viti > I mean there are two controllers and both of them have a device > "subtended" (both 0x1

Re: PCI device not working

2012-09-24 Thread Davide Viti
CONFIG_SYS_PCIE2_IO_PHYS 0xFFC0 #define CONFIG_SYS_PCIE2_IO_SIZE 0x0001/* 64k */ I'd really appreciate I you could take a look at it Thanx alot in advance Davide 2012/9/24 Davide Viti > Hi, > does the output I've included show anything wrong

Re: PCI device not working

2012-09-26 Thread Davide Viti
Hi, as you've suggested, I've added a printout inside fsl_pcie_check_link() which is called twice and returns 0 both times. Here follows the PCI-related part of dmesg with some extra printouts enabled. thank you, Davide ... Adding PCI host bridge /pcie@ffe09000 *** [/pci

R: Re: PCI device not working

2012-09-27 Thread Davide Viti
4) val=0x4 PCIBIOS_SUCCESSFUL the entire log is about 116Kb and is available in [1] or [2] (didn't feel like pasting so much data on the ML) thanx alot, Davide [1] http://pastebin.com/JaPGmmfs [2] http://paste2.org/p/2273728 Invita i tuoi amici e Tiscali ti premia! Il consiglio di un am

R: Re: PCI device not working

2012-09-27 Thread Davide Viti
Hi Kumar, >Messaggio originale >Da: ga...@kernel.crashing.org >Data: 27/09/2012 14.27 >A: "Davide Viti" >Cc: >Ogg: Re: PCI device not working > ... >Can you see what bus_no actually gets set to in the case we scan 0001:03 ? > >If its set to 03,

R: Re: PCI device not working

2012-09-28 Thread Davide Viti
settings, please refer to: http://www.mail-archive. com/linuxppc-dev@lists.ozlabs.org/msg62007.html thanx alot, Davide * *[1]* * PCIE1 used as Root Complex (base addr ffe09000) Scanning PCI bus 01 01 00 1b65 abba 0280 00

R: Re: PCI device not working

2012-10-04 Thread Davide Viti
Hi, it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the devide behind the second controller is detected by the Linux kernel. Would you suggest any particular patch I should apply to fix this (I'm using kernel 2.6.34) thanx alot in advance Davide [1]

Fwd: PCI device not working

2012-10-05 Thread Davide Viti
(just realized I did not send this to the mailing list: sorry for the noise) Hi Kumar, 2012/10/4 Kumar Gala : > > On Oct 4, 2012, at 7:24 AM, Davide Viti wrote: > >> Hi, >> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the >> device behi

Re: 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared

2007-11-28 Thread Davide Libenzi
ncorrectly) picked those up. My fault. I forgot to update sys_ni.c with the new functions (and with the sys_timerfd->sys_timerfd_create name change). Do you want a patch Andrew? - Davide ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev

[PATCH] powerpc/configs: fix default values for NF_CT_PROTO_*

2017-06-05 Thread Davide Caratti
NF_CT_PROTO_{SCTP,UDPLITE,DCCP} can't be set to 'm' anymore, since they have been redefined as 'bool': fix defconfig for linkstation, mvme5100 and ppc6xx platforms accordingly. Signed-off-by: Davide Caratti --- arch/powerpc/configs/linkstation_defconfig | 2

Re: [PATCH] powerpc/configs: fix default values for NF_CT_PROTO_*

2017-06-13 Thread Davide Caratti
On Tue, 2017-06-13 at 20:49 +1000, Michael Ellerman wrote: > Davide Caratti writes: > > > NF_CT_PROTO_{SCTP,UDPLITE,DCCP} can't be set to 'm' anymore, since they > > have been redefined as 'bool': fix defconfig for linkstation, mvme5100 and > >