On Fri, 2010-04-30 at 14:34 +1000, Anton Blanchard wrote:
> Firmware changed the way it represents memory and cpu affinity on POWER7.
> Unfortunately the old method now caps the topology to work around issues
> with legacy operating systems. For Linux to get the correct topology we
> need to use th
Hi Ben,
> I sent your previous version of that one to Linus, it's already up. Can
> you check it's allright ?
No change to this patch, but I thought I would send them as a series since they
build on each other. I'll double check mainline looks good.
Anton
__
On Thu, 29 Apr 2010 20:39:02 -0500
Timur Tabi wrote:
> On Thu, Apr 29, 2010 at 6:49 PM, Anatolij Gustschin wrote:
> > This patch series rework DIU support patches submitted
> > previously. Comments to the previos patch series have
> > been addressed, not related changes are dropped and some
> >
On Thu, 29 Apr 2010 20:44:12 -0500
Timur Tabi wrote:
> On Thu, Apr 29, 2010 at 6:49 PM, Anatolij Gustschin wrote:
>
> > +Optional properties:
> > +- EDID : verbatim EDID data block describing attached display.
> > + Data from the detailed timing descriptor will be used to
> > + program the di
Adds support for encoding display mode information
in the device tree using verbatim EDID block.
If the EDID entry in the DIU node is present, the
driver will build mode database using EDID data
and allow setting the display modes from this database.
Otherwise display mode will be set using mode
e
On Thu, 29 Apr 2010 21:05:26 -0500
Timur Tabi wrote:
> On Thu, Apr 29, 2010 at 6:49 PM, Anatolij Gustschin wrote:
>
>
> > +void __init mpc5121_ads_init_early(void)
> > +{
> > + mpc512x_init_diu();
> > +}
> > +
> > define_machine(mpc5121_ads) {
> > .name = "MPC51
MPC5121 DIU configuration/setup as initialized by the boot
loader currently will get lost while booting Linux. As a
result displaying the boot splash is not possible through
the boot process.
To prevent this we reserve configured DIU frame buffer
address range while booting and preserve AOI descri
Anatolij Gustschin (2):
powerpc/mpc5121: move PSC FIFO memory init to platform code
spi: Add SPI master driver for MPC5121 PSC
arch/powerpc/include/asm/mpc52xx_psc.h |1 +
arch/powerpc/platforms/512x/mpc512x_shared.c | 78
drivers/serial/mpc52xx_uart.c| 69 -
Since PSC could also be used in other modes than UART mode
we move PSC FIFO memory initialization from serial driver to
common platform code. The initialized FIFO memory slices may
not overlap, so the most easy way would be to configure them
all at once at init time for all PSC devices. This is now
Signed-off-by: John Rigby
Signed-off-by: Anatolij Gustschin
---
arch/powerpc/include/asm/mpc52xx_psc.h |1 +
drivers/spi/Kconfig|7 +
drivers/spi/Makefile |1 +
drivers/spi/mpc512x_psc_spi.c | 576
4 fil
On Tue, 2010-04-27 at 16:56 -0500, Tseng-Hui (Frank) Lin wrote:
> On Sat, 2010-04-24 at 10:55 +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2010-04-23 at 17:04 -0500, Tseng-Hui (Frank) Lin wrote:
> > > Add Power7 icswx co-processor instruction support.
> >
> > Please provide a -much- more detai
On Fri, Apr 30, 2010 at 7:21 AM, Anatolij Gustschin wrote:
> Since PSC could also be used in other modes than UART mode
> we move PSC FIFO memory initialization from serial driver to
> common platform code. The initialized FIFO memory slices may
> not overlap, so the most easy way would be to conf
inted
(2.6.34-rc5-autotest-next-20100430)
MSR: 80009032 CR: 2428 XER: 2005
DAR: , DSISR: 4000
TASK = ccf3ced0[730] 'modprobe' THREAD: cc514000 CPU: 0
GPR00: c002614c cc517a90 c0c96358 000
On Fri, Apr 30, 2010 at 5:19 AM, Anatolij Gustschin wrote:
>> How about just doing this?
>>
>> .init_early = mpc512x_init_diu,
>
> I thought it should be prepared for adding other code here.
> mpc5121_ads_init_early() is generic and could contain other
> things as well. I would vote f
On Fri, Apr 30, 2010 at 10:08:45AM -0500, Timur Tabi wrote:
> On Fri, Apr 30, 2010 at 5:19 AM, Anatolij Gustschin wrote:
>
> >> How about just doing this?
> >>
> >> .init_early = mpc512x_init_diu,
> >
> > I thought it should be prepared for adding other code here.
> > mpc5121_ads_init
On Fri, 30 Apr 2010 10:08:45 -0500
Timur Tabi wrote:
> On Fri, Apr 30, 2010 at 5:19 AM, Anatolij Gustschin wrote:
>
> >> How about just doing this?
> >>
> >> .init_early = mpc512x_init_diu,
> >
> > I thought it should be prepared for adding other code here.
> > mpc5121_ads_init_earl
0:2:0/type
Modules linked in: ehea(+) sr_mod cdrom sg sd_mod crc_t10dif ibmvscsic
scsi_transport_srp scsi_tgt scsi_mod
NIP: c04e8d7c LR: c002614c CTR: c0026314
REGS: cc517810 TRAP: 0300 Not tainted
(2.6.34-rc5-autotest-next-20100430)
MSR: 80009032
On Fri, Apr 30, 2010 at 11:27 AM, Sachin Sant wrote:
> Sachin Sant wrote:
>>
>> With today's next eHEA drivers fails to initialize.
>
> If i revert the following patch eHEA network interface is initialized
> properly.
>
> commit cebfe0b6709abdab997c1a00499d67efa32ee1f0
> drivercore: Add of_match_t
On Fri, Apr 30, 2010 at 11:35 AM, Grant Likely
wrote:
> On Fri, Apr 30, 2010 at 11:27 AM, Sachin Sant wrote:
>> Sachin Sant wrote:
>>>
>>> With today's next eHEA drivers fails to initialize.
>>
>> If i revert the following patch eHEA network interface is initialized
>> properly.
>>
>> commit cebf
On Fri, Mar 12, 2010 at 02:38:02PM -0700, Grant Likely wrote:
[...]
> How to proceed: I'd like to leave this series out for the 2.6.34
> cycle and I'll pick it into my OF tree before the 2.6.35 merge window,
> but I'll probably modify it to call the OF hooks directly and leave
> out the unnecessar
On Fri, Apr 30, 2010 at 11:22 AM, Scott Wood wrote:
>> That's what I meant. Actually, I think it's ULL. Regardless, I think
>> the compiler will see the "10 ... * 1000" and just combine
>> them together. You're not actually outsmarting the compiler.
>
> The compiler will do no such th
On Fri, Apr 30, 2010 at 12:00 PM, Anatolij Gustschin wrote:
> Thanks. Sorry for my wrong answer above, now I remember the logic
> behind this and will try to explain. Actually the reason I do not
> use kmalloc() here is that I do not want to _copy_ bitmap data to
> newly allocated frame buffer ar
Allow board selection in a drop-down board sub-menu
like many other platforms do.
Before the patch:
...
[ ] Freescale MPC5121E ADS
[ ] Generic support for simple MPC5121 based boards
[ ] 52xx-based boards
...
Patched:
...
[*] 512x-based boards
[ ] Freescale MPC5121E ADS
[ ] Generic support fo
Adds IFM PDM360NG device tree, and platform code.
Currently following is supported:
- Spansion S29GL512P 256 MB NOR flash
- ST Micro NAND 1 GiB flash
- DIU, please use "fbcon=map:5 video=fslfb:800x480...@60"
at the kernel command line to enable PrimeView PM070WL3
Display support.
- FEC
Timur Tabi wrote:
On Fri, Apr 30, 2010 at 11:22 AM, Scott Wood wrote:
That's what I meant. Actually, I think it's ULL. Regardless, I think
the compiler will see the "10 ... * 1000" and just combine
them together. You're not actually outsmarting the compiler.
The compiler will do n
On Tue, Apr 27, 2010 at 10:20 AM, Liam Girdwood wrote:
>> Another problem is that ASoC won't let me probe the DMA channels
>> independently. That is, I cannot tell ASoC that I have a playback DMA
>> and a capture DMA. ASoC does not recognize two DMA devices for a
>> single SSI. If you can fix
On Fri, Apr 30, 2010 at 4:46 PM, Timur Tabi wrote:
> When I boot Linux, I get this:
>
> asoc: cs4270 <-> /s...@e000/s...@16000 mapping ok
> sysfs: cannot create duplicate filename '/devices/platform/soc-audio/cs4270'
*sigh* never mind. The problem was that the stream_name was the same
for b
27 matches
Mail list logo
