Hi Kumar,
On 10/18/2011 07:44 AM, Kumar Gala wrote:
>
> On Aug 16, 2011, at 10:32 PM, Robin Holt wrote:
>
>> David,
>>
>> The following set of patches have been reviewed by the above parties and
>> all comments have been integrated. Although the patches stray from the
>> drivers/net/can directo
On Mon, Oct 17, 2011 at 11:40:54PM +0200, nello martuscielli wrote:
> i'm trying to enable marvel gigabit ethernet support but it doesn't work.
> Here my dmesg instead my config is attached.
[snipped]
> via_rhine: v1.10-LK1.5.0 2010-10-09 Written by Donald Becker
> mv643xx_eth: MV-643xx 10/100/1000
Hi Robert,
On Mon, Oct 17, 2011 at 8:34 PM, Robert Sciuk wrote:
>
>
>> -Original Message-
>> From: patrickdeping...@gmail.com [mailto:patrickdeping...@gmail.com] On
>> Behalf Of Thomas De Schampheleire
>> Sent: Monday, October 17, 2011 5:01 AM
>> To: Robert Sciuk
>> Cc: linuxppc-dev@lists
Hi ,
I want to use IRQ2 and IRQ3 in my driver. How do I add them in the device tree
file.
Regard,
Smitha
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to
this message are intended for the exclusive
Hi ,
I want to use IRQ2 and IRQ3 in my driver. How do I add them in the device tree
file.
Regard,
Smitha
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to
this message are intended for the exclusi
Hi,
Is not some interrupt vector number defined for i2c in your soc
specification(IIRC mpc9247 and I do not have this).
Thanks
-Bharat
> -Original Message-
> From: smitha.va...@wipro.com [mailto:smitha.va...@wipro.com]
> Sent: Tuesday, October 18, 2011 1:36 PM
> To: Wood Scott-B07421;
Yes , there is a vector numbe defined in the specifications .
IRQ2 - 20
IRQ3 - 21
But I don't know how to specify them in the .dts file .
Regards,
Smitha
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments t
On Tue, Oct 18, 2011 at 12:44:07AM -0500, Kumar Gala wrote:
>
> On Aug 16, 2011, at 10:32 PM, Robin Holt wrote:
>
> > David,
> >
> > The following set of patches have been reviewed by the above parties and
> > all comments have been integrated. Although the patches stray from the
> > drivers/ne
>> Robin,
>>
>> Do you remember why we went with just 'fsl,p1010-flexcan' as the device tree
>> compatible? Do we feel the flex can on P1010 isn't the same as on MPC5xxx?
>> or the ARM SoCs?
>
> The decision was due to the fact there is no true "generic" fsl.flexcan
> chip free of any SOC imp
On 10/18/2011 01:43 PM, Kumar Gala wrote:
> Thanks, I'll look into this internally at FSL. I think its confusing
> as hell to have "fsl,p1010-flexcan" in an ARM .dts and don't think
> any reasonable ARM customer of FSL would know to put a PPC SOC name
> in their .dts. I'll ask the HW guys what's
On Tue, Oct 18, 2011 at 06:43:13AM -0500, Kumar Gala wrote:
>
> >> Robin,
> >>
> >> Do you remember why we went with just 'fsl,p1010-flexcan' as the device
> >> tree compatible? Do we feel the flex can on P1010 isn't the same as on
> >> MPC5xxx? or the ARM SoCs?
> >
> > The decision was due t
Hi,
For detail please look at ePAPR specification.
Say i2c interrupt number is 21 then you can try
"interrupts = <21 8>;" in device tree.
Thanks
-Bharat
> -Original Message-
> From: smitha.va...@wipro.com [mailto:smitha.va...@wipro.com]
> Sent: Tuesday, October 18, 2011 2:35 PM
> To: B
Since commit 8a0a9bd4db63bc45e301, this comment in mmap_rnd() does not
hold true as the value returned by get_random_int() will in fact be
different every single call. Remove the comment and simplify the code
back to its original desired form.
This reverts commit a5adc91a4b44b5d1 which is no longe
On Mon, Oct 17, 2011 at 4:51 PM, David Miller wrote:
> From: Dan McGee
> Date: Mon, 17 Oct 2011 15:17:36 -0500
>
>> Since commit 8a0a9bd4db63bc45e301, this comment in mmap_rnd() does not
>> hold true as the value returned by get_random_int() will in fact be
>> different every single call. Remove
Since commit 8a0a9bd4db63bc45e301, this comment in mmap_rnd() does not
hold true as the value returned by get_random_int() will in fact be
different every single call. Remove the comment and simplify the code
back to its original desired form.
This reverts commit a5adc91a4b44b5d1 which is no longe
interrupts
i2c@3000 {
#address-cells = <1>;
#size-cells = <0>;
cell-index = <0>;
compatible = "fsl-i2c";
reg = <0x3000 0x100>;
interrupts = <43 2>;
interrupt-parent = <&mpic>;
dfsrr;
};
O
[snip]
>
> How and what type of packets are you sending? Raw MAC frames, IP? Are
> you using custom code, or can you try things like ping?
> If you are using IP, I trust you checked the Linux configuration (like
> assigning a valid IP address to the interface and making sure the
> routing table
Hi Robert,
On Tue, Oct 18, 2011 at 11:38 PM, Robert Sciuk wrote:
>
>
> [snip]
>
>>
>> How and what type of packets are you sending? Raw MAC frames, IP? Are
>> you using custom code, or can you try things like ping?
>> If you are using IP, I trust you checked the Linux configuration (like
>> assig
18 matches
Mail list logo
