On Mon, Mar 8, 2010 at 9:53 AM, Grant Likely wrote:
> On Mon, Mar 8, 2010 at 9:32 AM, Albrecht Dreà wrote:
>> Hi Anatolij:
>>
>>> > Anatolij, could you please look into this?
>>>
>>> I'll look into this tomorrow, need to finish USB support now.
>>> Unfortunately the patch doesn't apply on top of
On Thu, Mar 11, 2010 at 10:58 PM, Roman Fietze
wrote:
> Hello,
>
> This patch avoids unbalanced enable/disable messages for the DMA
> interrupts when running the 5200 platform SCLPC/BestComm driver in DMA
> mode.
>
>
> Signed-off-by: Roman Fietze
Applied, thanks.
g.
I've not got time to review this patch right now, but Sergey and
Steven, you both posted MPMC drivers on the same day; Steven on the
microblaze list and Sergey on the powerpc list. Can you two please
coordinate and figure out how to mork toward a single driver that will
meet both your needs? I do
On Fri, Mar 26, 2010 at 11:17:07PM +0100, Wolfgang Wegner wrote:
> Hi Josh,
>
> On Fri, Mar 26, 2010 at 02:32:02PM -0700, Josh Triplett wrote:
> > On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
> > >
> > > Not all CF adapters have all the pins wired up that are needed for
> > > *DM
On Fri, Mar 26, 2010 at 4:42 PM, Timur Tabi wrote:
> Define a binding for embedding a QE firmware blob into the device tree. Also
> define a new property for the QE node that links to a firmware node.
>
> Signed-off-by: Timur Tabi
> ---
> .../powerpc/dts-bindings/fsl/cpm_qe/qe.txt | 5
On Fri, Mar 26, 2010 at 4:17 PM, Wolfgang Wegner wrote:
> Hi Josh,
>
> On Fri, Mar 26, 2010 at 02:32:02PM -0700, Josh Triplett wrote:
>> On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
>> >
>> > Not all CF adapters have all the pins wired up that are needed for
>> > *DMA modes. That
Define a binding for embedding a QE firmware blob into the device tree. Also
define a new property for the QE node that links to a firmware node.
Signed-off-by: Timur Tabi
---
.../powerpc/dts-bindings/fsl/cpm_qe/qe.txt | 54
1 files changed, 54 insertions(+), 0 de
Hi Josh,
On Fri, Mar 26, 2010 at 02:32:02PM -0700, Josh Triplett wrote:
> On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
> >
> > Not all CF adapters have all the pins wired up that are needed for
> > *DMA modes. That is the most likely problem.
>
> True, but we bought a card that
From: Julia Lawall
Use set_cpus_allowed_ptr rather than set_cpus_allowed.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@@
expression E1,E2;
@@
- set_cpus_allowed(E1, cpumask_of_cpu(E2))
+ set_cpus_allowed_ptr(E1, cpumask_of(E2))
@@
expression E;
id
On Fri, Mar 26, 2010 at 3:32 PM, Josh Triplett wrote:
> On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
>> On Tue, Mar 16, 2010 at 11:17 PM, Josh Triplett
>> wrote:
>> > Hello,
>> >
>> > We've tried both 2.6.33 and DENX-v2.6.33.1, and we haven't managed to
>> > successfully use any
On Fri, Mar 26, 2010 at 12:22:32PM -0600, Grant Likely wrote:
> On Tue, Mar 16, 2010 at 11:17 PM, Josh Triplett wrote:
> > Hello,
> >
> > We've tried both 2.6.33 and DENX-v2.6.33.1, and we haven't managed to
> > successfully use any form of DMA with the TQM5200 and a CompactFlash
> > card. We kno
On Tue, 2010-03-23 at 19:37 +0530, K.Prasad wrote:
> plain text document attachment (ppc64_hbkpt_02)
> Implement perf-events based hw-breakpoint interfaces for PPC64 processors.
> These interfaces help arbitrate requests from various users and schedules
> them as appropriate.
>
> Signed-off-by: K.
Hi, I am having trouble building u-boot (from u-boot-2009.11-mpc8572ds.spec)
from LTIB for the MPC8572DS platform using just the Makefile and freescale
cross tools. The build machine is CentOS 5.3. This is procedure I am
following (on LTIB for MPC8572DS, 20100115):
# cd ltib-mpc8572ds-20100115
#
On Fri, Mar 26, 2010 at 1:50 PM, Timur Tabi wrote:
> Grant Likely wrote:
>> The node must be a child of a QE node. A QE node can reference the
>> firmware from another QE node by using the fsl,firmware-phandle
>> property.
>
> Ok.
>
> I'll post a V3 once everyone else has a chance to comment.
Al
Grant Likely wrote:
> The node must be a child of a QE node. A QE node can reference the
> firmware from another QE node by using the fsl,firmware-phandle
> property.
Ok.
I'll post a V3 once everyone else has a chance to comment.
--
Timur Tabi
Linux kernel developer at Freescale
__
On Fri, Mar 26, 2010 at 1:35 PM, Timur Tabi wrote:
> Define a binding for embedding a QE firmware blob into the device tree. Also
> define a new property for the QE node that links to a firmware node.
>
> Signed-off-by: Timur Tabi
> ---
> .../powerpc/dts-bindings/fsl/cpm_qe/qe.txt | 5
Define a binding for embedding a QE firmware blob into the device tree. Also
define a new property for the QE node that links to a firmware node.
Signed-off-by: Timur Tabi
---
.../powerpc/dts-bindings/fsl/cpm_qe/qe.txt | 54
1 files changed, 54 insertions(+), 0 de
[cc'ing linuxppc-...@lists.ozlabs.org]
On Wed, Mar 17, 2010 at 3:30 PM, Mark Schaefer wrote:
> Hi Grant,
>
> I was able to get kernel 2.6.16 running on a Media5200 using ltib, but
> what I would really like to do is build a current kernel with SocketCAN.
> I've read and read the various grou
On Fri, Mar 26, 2010 at 12:58 PM, Mitch Bradley wrote:
> a) Firmware blob in some random place - requires strong naming of either
> firmware blob property or node containing it.
BTW, this exactly the reason for all the bikesheding earlier; but I
don't care at all if it is under a QE node.
g.
___
Timur Tabi wrote:
Grant Likely wrote:
Nah. That looks totally fine. Not having the firmware under a qe
node would look bad to me.
You don't think it weird to have one QE node reference data from another QE
node, or that the DTS implies that the firmware belongs to one QE more than
On Fri, Mar 26, 2010 at 12:48 PM, Timur Tabi wrote:
> Grant Likely wrote:
>
>> Nah. That looks totally fine. Not having the firmware under a qe
>> node would look bad to me.
>
> You don't think it weird to have one QE node reference data from another QE
> node, or that the DTS implies that the
Grant Likely wrote:
> Nah. That looks totally fine. Not having the firmware under a qe
> node would look bad to me.
You don't think it weird to have one QE node reference data from another QE
node, or that the DTS implies that the firmware belongs to one QE more than it
belongs to the other?
Timur Tabi wrote:
Grant Likely wrote:
Without the compatible property, the only way I'd know that the child node
contains a firmware is to look at the actual name of the child node, which (as
Scott and I believe) is not better than a compatible property.
If it is always a child of a
On Fri, Mar 26, 2010 at 12:39 PM, Timur Tabi wrote:
> Grant Likely wrote:
>>> Without the compatible property, the only way I'd know that the child node
>>> contains a firmware is to look at the actual name of the child node, which
>>> (as Scott and I believe) is not better than a compatible pro
Grant Likely wrote:
>> Without the compatible property, the only way I'd know that the child node
>> contains a firmware is to look at the actual name of the child node, which
>> (as Scott and I believe) is not better than a compatible property.
> If it is always a child of a qe node, then I've g
On 2010-03-25, at 17:46, Timur Tabi wrote:
> The more I think about it, the more I believe that this is how we're going to
> have to do it. Whether or not Freescale can embed a non-GPL firmware into a
> device tree is still undecided. It may require relicensing all of our device
> trees as d
On Tue, Mar 16, 2010 at 11:17 PM, Josh Triplett wrote:
> Hello,
>
> We've tried both 2.6.33 and DENX-v2.6.33.1, and we haven't managed to
> successfully use any form of DMA with the TQM5200 and a CompactFlash
> card. We know the CF card supports DMA (or, at least, it says "UDMA"
> right on the ca
On Fri, Mar 26, 2010 at 9:17 AM, Timur Tabi wrote:
> Grant Likely wrote:
>
>> +- fsl,firmware:
>> + Usage: Optional.
>> + Value type: , encoded array of bytes
>> + Definition: Contains the QUICC engine firmware blob.
>> [plus any other properties needed for firmware metadata]
>
> This wou
Greetings,
I am new to the mpc5121 and MBX...wondering if anyone has been successful with
ELDK and MBX and MPC5121 platform. What are the gotchas? Does the Flattened
Device Tree (fdt) need to be modified for support?
Thanks for your help, any pointers would be appreciated.
Jayne
Grant Likely wrote:
> +- fsl,firmware:
> +Usage: Optional.
> +Value type: , encoded array of bytes
> +Definition: Contains the QUICC engine firmware blob.
> [plus any other properties needed for firmware metadata]
This would place the firmware metadata properties inside the QE node it
On (Fri) Mar 26 2010 [11:52:33], Alan Cox wrote:
> > >> mount: can't find /root/proc in /etc/fstab or /etc/mtab
> > >> /sbin/smart_agetty: can not determine 'console' speed
> > >>
> > >
> > > OK, this gets even murkier. I don't know why taking a few krefs modifies
> > > hvc_console behaviour t
On (Fri) Mar 26 2010 [17:12:22], Sachin Sant wrote:
> Amit Shah wrote:
>> On (Fri) Mar 26 2010 [14:43:56], Sachin Sant wrote:
>>
And this suggests that hvc_kick() is called before hvc_task is
initialised, ie, before hvc_init() is called.
Does this help?
>>> Hi A
On Fri, 2010-03-26 at 11:20 +0100, Romain Goyet wrote:
> 2010/3/25 Michel Dänzer :
> > On Wed, 2010-03-24 at 11:32 +0100, Romain Goyet wrote:
> >>
> >> By the way, as of writing this, grub2 on PPC from debian gives a "out
> >> of memory" issue. Known bug.
> >
> > That's on the G5? It's working on
Yes, the missing 64-bit conversion is the key problem, I will try removing
isync later.
Thanks for your support.
2010/3/26 Segher Boessenkool
> > Yes indeed. Could you post the relevant piece if disassembly from
> > your original binary (the one that has the problem)? Or send me the
> > bina
> >> mount: can't find /root/proc in /etc/fstab or /etc/mtab
> >> /sbin/smart_agetty: can not determine 'console' speed
> >>
> >
> > OK, this gets even murkier. I don't know why taking a few krefs modifies
> > hvc_console behaviour to such an extent.
Can you see if the agetty is getting a han
Amit Shah wrote:
On (Fri) Mar 26 2010 [14:43:56], Sachin Sant wrote:
And this suggests that hvc_kick() is called before hvc_task is
initialised, ie, before hvc_init() is called.
Does this help?
Hi Amit,
I too ran into this issue as reported by Anton. Unfortunately in my
case the
Hi Amit,
On Fri, 26 Mar 2010 15:28:21 +0530 Amit Shah wrote:
>
> On (Fri) Mar 26 2010 [14:43:56], Sachin Sant wrote:
> >
> > I too ran into this issue as reported by Anton. Unfortunately in my
> > case the following suggested patch does not help boot the powerpc
> > box successfully. The boot sti
2010/3/25 Michel Dänzer :
> On Wed, 2010-03-24 at 11:32 +0100, Romain Goyet wrote:
>>
>> Here's a summary about "how to boot a PowerMac G5 without a screen
>> attached". As many people have noticed, default yaboot install won't
>> boot unless a screen is attached.
>>
>> Actually, the workaround
On (Fri) Mar 26 2010 [14:43:56], Sachin Sant wrote:
>> And this suggests that hvc_kick() is called before hvc_task is
>> initialised, ie, before hvc_init() is called.
>>
>> Does this help?
>>
> Hi Amit,
>
> I too ran into this issue as reported by Anton. Unfortunately in my
> case the following
Amit Shah wrote:
On (Sun) Mar 21 2010 [10:07:25], Amit Shah wrote:
On (Sun) Mar 21 2010 [08:04:39], Benjamin Herrenschmidt wrote:
On Fri, 2010-03-19 at 08:18 -0700, Greg Kroah-Hartman wrote:
From: Amit Shah
Alan pointed out a race in the code where hvc_remove is invoked. The
r
> Yes indeed. Could you post the relevant piece if disassembly from
> your original binary (the one that has the problem)? Or send me the
> binary (not to the mailing list), I'll do it then.
Ah scratch that. I compiled your original code (after fixing the
compile errors -- there is no such type
[please do not top-post]
>> Do you now ever get two consecutive time readings that are closer
>> that 64 tick together? If not, it's simply hiding the problem.
>>
>> Do you ever now read a value that does not have the bit with value
>> 0x40 set?
> I enabled the printing of all values. There is b
We need to keep track of the backing pages that get allocated by
vmemmap_populate() so that when we use kdump, the dump-capture kernel can
find these pages in memory.
We use a linked list of structures that contain the physical address of the
backing page and corresponding virtual address to track
43 matches
Mail list logo
