On 03/28/2012 10:30 PM, Bryan Hundven wrote:
> It is not at 0xffa0. According to current u-boot source the NAND
> controller is always at 0xff80 and it is either at CS0 or CS1
> depending on NAND or NAND+NOR mode. In 36bit mode it is shifted to
> 0xfff80 but it has always an eight
On Wed, 2012-03-28 at 22:02 -0700, Linus Torvalds wrote:
> On Wed, Mar 28, 2012 at 9:42 PM, Stephen Rothwell
> wrote:
> >
> > How about this (build tested on powerpc allyesconfig):
>
> Looks better.
>
> Grant - what's the plan about that CONFIG_VIRQ_DEBUG thing? In theory
> something like it co
Hi, all
In function "of_find_node_with_property", why use "raw_spin_lock_irqsave" to
disable preemption and disable interrupt?
If enable them, what impact will be observed?
This function just finds the node from the DTS file, it can't be interrupted or
preempted?
I have done one test: remove "ra
On Mar 29, 2012, at 2:26 AM, Sebastian Andrzej Siewior wrote:
> On 03/28/2012 10:30 PM, Bryan Hundven wrote:
>> > It is not at 0xffa0. According to current u-boot source the NAND
>> > controller is always at 0xff80 and it is either at CS0 or CS1
>> > depending on NAND or NAND+NOR mode. In
On Tue, 27 Mar 2012, Marek Szyprowski wrote:
> From: Andrzej Pietrasiewicz
> -static inline void *dma_alloc_coherent(struct device *dev, size_t size,
> -dma_addr_t *daddr, gfp_t gfp)
> +#define dma_alloc_coherent(d,s,h,f) dma_alloc_attrs(d,s,h,f,NULL)
Please m
On Thu, Mar 29, 2012 at 5:01 AM, Huang Changming-R66093
wrote:
> Hi, all
>
> In function “of_find_node_with_property”, why use “raw_spin_lock_irqsave” to
> disable preemption and disable interrupt?
Where do you see raw_spin_lock_irqsave?
struct device_node *of_find_node_with_property(struct devi
On 03/28/2012 11:13 AM, Fabio wrote:
> Hi all,
> I am a newbie trying to get the FCC1 ethernet interface to work on a
> custom board.
> The hardware used is based on mpc8270 which is connected via FCC1 to a
> phy-less interface linked to another microcontroller.
> FCC1 should be recognized as eth0
Kumar,
Sorry, i should have posted to the ml.
Thank you, I was looking in the wrong spot.
Cheers,
-Bryan
Kumar Gala wrote:
On Mar 29, 2012, at 2:26 AM, Sebastian Andrzej Siewior wrote:
> On 03/28/2012 10:30 PM, Bryan Hundven wrote:
>> > It is not at 0xffa0. According to current u-bo
> Which old kernel driver? Why do you need to mess with fs_platform_info?
I have to port a custom platform driver written for 2.6.10 to support
this custom board.
That driver directly initializes the fs_platform_info data structure,
so after some failed attempts I thought to directly assign some v
On 03/29/2012 02:56 PM, Fabio wrote:
>> Which old kernel driver? Why do you need to mess with fs_platform_info?
> I have to port a custom platform driver written for 2.6.10 to support
> this custom board.
So it's old arch/ppc stuff. Now fs_platform_info is driver-internal and
info comes from the
Ben,
A few minor bug fixes and missing dts updates for 3.4. There got lost in
the mix. Sorry for the delay
- k
The following changes since commit 1ce447b90f3e71c81ae59e0062bc305ef267668b:
powerpc/perf: Fix instruction address sampling on 970 and Power4 (2012-03-28
11:33:24 +1100)
are avai
As long as there is no other non-const variable marked __initdata in the
same compilation unit it doesn't hurt. If there were one however
compilation would fail with
error: $variablename causes a section type conflict
because a section containing const variables is marked read only and so
On Thu, Mar 29, 2012 at 2:11 AM, Benjamin Herrenschmidt
wrote:
> On Wed, 2012-03-28 at 22:02 -0700, Linus Torvalds wrote:
>> On Wed, Mar 28, 2012 at 9:42 PM, Stephen Rothwell
>> wrote:
>> >
>> > How about this (build tested on powerpc allyesconfig):
>>
>> Looks better.
>>
>> Grant - what's the p
Hello,
this series fixes a common error to use __initdata to mark const
variables. Most of the time this works well enough to go unnoticed
(though I wonder why the linker doesn't warn about that).
Just try adding something like
int something __initdata;
to one of the patched files and co
On Thu, Mar 29, 2012 at 3:44 PM, Kumar Gala wrote:
>
> A few minor bug fixes and missing dts updates for 3.4. There got lost in
> the mix. Sorry for the delay
What about my "don't call of_platform_bus_probe() twice" patch?
That's still an important fix for the P1022DS.
--
Timur Tabi
Linux ker
On Thu, 29 Mar 2012, Grant Likely wrote:
> On Thu, Mar 29, 2012 at 2:11 AM, Benjamin Herrenschmidt
> The rightmost fields of /proc/interrupts are a weird set of
> conditional outputs that don't really have any parsable formatting to
> them. It may be safe to apply my patch because it adds another
On Thu, Mar 29, 2012 at 3:48 PM, Thomas Gleixner wrote:
> On Thu, 29 Mar 2012, Grant Likely wrote:
>> On Thu, Mar 29, 2012 at 2:11 AM, Benjamin Herrenschmidt
>> The rightmost fields of /proc/interrupts are a weird set of
>> conditional outputs that don't really have any parsable formatting to
>> t
One final question on this change is: If the nand base address was wrong in the
kernel, but right in u-boot, how did this work before this change and what
kinds of problems would I see with the old base address value in the kernel.
Thanks for your time in advance,
-Bryan
___
Freescale PowerPC SoCs share a number of IP blocks with Freescale
ARM/IMX SoCs, FlexCAN, SSI, FEC, eSDHC, USB, etc. There are some
effort consolidating those drivers to make them work for both
architectures.
One outstanding difference between two architectures is ARM/IMX will
turn off module cloc
19 matches
Mail list logo
