Re: linux-next: build failure after merge of the final tree (powerpc tree related)

2010-12-02 Thread Stephen Rothwell
On Fri, 03 Dec 2010 16:59:58 +1100 Benjamin Herrenschmidt wrote: > > This toolchain is a bit ancient I suppose... Anton, do you reckon we > should use .long based macros for these for the time being or just > require a newer binutils ? The currently documented minimum binutils is 2.12 ... -- C

Re: linux-next: build failure after merge of the final tree (powerpc tree related)

2010-12-02 Thread Benjamin Herrenschmidt
On Fri, 2010-12-03 at 16:32 +1100, Stephen Rothwell wrote: > > After merging the tree, today's linux-next build (powerpc allmodconfig) > failed like this: > > arch/powerpc/lib/hweight_64.S: Assembler messages: > arch/powerpc/lib/hweight_64.S:52: Error: Unrecognized opcode: `popcntw' > arch/power

linux-next: build failure after merge of the final tree (powerpc tree related)

2010-12-02 Thread Stephen Rothwell
Hi all, After merging the tree, today's linux-next build (powerpc allmodconfig) failed like this: arch/powerpc/lib/hweight_64.S: Assembler messages: arch/powerpc/lib/hweight_64.S:52: Error: Unrecognized opcode: `popcntw' arch/powerpc/lib/hweight_64.S:77: Error: Unrecognized opcode: `popcntw' arc

RE: [PATCH 2/2][v3] rapidio, powerpc/85xx: Error interrupt handler for sRIO.

2010-12-02 Thread Xie Shaohui-B21989
Hi Alex, May I ask when would these patches be applied to mainline? Best Regards, Shaohui Xie From: Bounine, Alexandre [mailto:alexandre.boun...@idt.com] Sent: Wednesday, December 01, 2010 4:49 AM To: Xie Shaohui-B21989; linuxppc-dev@lists.ozlabs.org Cc: a...@linux-foundation.org;

Re: Problem with MPC5121 custom board.

2010-12-02 Thread Wolfgang Denk
Dear =?iso-8859-1?Q?CTAG_/_Mois=E9s_Dom=EDnguez?=, In message <765b188b547a48e7951d86acc3544...@ctag> you wrote: > > We have a problem with custom design based on ads5121. May be you could > provide us any clue about what may be happening. > > Sometimes, when the board is powered-on: > > - U-bo

Re: Getting the IRQ number (Was: Basic driver devel questions ?)

2010-12-02 Thread Benjamin Herrenschmidt
On Thu, 2010-12-02 at 18:47 +0100, Guillaume Dargaud wrote: > > OK, learning by example then. > > Another basic question: > what's the difference between of_register_platform_driver() and > platform_driver_register() ? > I assume I must use the first one if I want to use > irq_of_parse_and_map.

Re: Getting the IRQ number (Was: Basic driver devel questions ?)

2010-12-02 Thread Guillaume Dargaud
> grep -r irq_of_parse_and_map * > > will give you plenty of examples. OK, learning by example then. Another basic question: what's the difference between of_register_platform_driver() and platform_driver_register() ? I assume I must use the first one if I want to use irq_of_parse_and_map

RE: [v4] ppc44x:PHY fixup for USB on canyonlands board

2010-12-02 Thread Rupjyoti Sarmah
>>I prepared these comments for v1, but aparently forgot to send them, >>so I'll do so now. Thanks for your inputs. I will resubmit an updated patch soon with the changes. Regards, Rup ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://

Re: Getting the IRQ number (Was: Basic driver devel questions ?)

2010-12-02 Thread Timur Tabi
On Thu, Dec 2, 2010 at 9:36 AM, Guillaume Dargaud wrote: > Sounds like what I need... But I don't find irq_of_parse_and_map() in LDD 3rd > ed and very few info in google. Are there some examples of use somewhere ? grep -r irq_of_parse_and_map * will give you plenty of examples. -- Timur

Re: Getting the IRQ number (Was: Basic driver devel questions ?)

2010-12-02 Thread Guillaume Dargaud
> How was your driver probed? If you can get a pointer to the device > node, use irq_of_parse_and_map() to get a virtual irq that you can pass > to request_irq(). Sounds like what I need... But I don't find irq_of_parse_and_map() in LDD 3rd ed and very few info in google. Are there some examples

Problem with MPC5121 custom board.

2010-12-02 Thread CTAG / Moisés Domínguez
Hi all, We have a problem with custom design based on ads5121. May be you could provide us any clue about what may be happening. Sometimes, when the board is powered-on: - U-boot does not start (at least serial port does not output anything, I don't know if some piece of u-boot is executed). -