Hello Paul,
Paul Mundt wrote:
> On Tue, Jan 25, 2011 at 08:20:31AM +0100, Heiko Schocher wrote:
>> @@ -1934,7 +1943,29 @@ static int __devinit sm501fb_probe(struct
>> platform_device *pdev)
>> }
>>
>> if (info->pdata == NULL) {
>> -dev_info(dev, "using default configuratio
Hello Paul,
Paul Mundt wrote:
> On Mon, Jan 24, 2011 at 10:57:27AM +0100, Heiko Schocher wrote:
>> @@ -1884,7 +1935,6 @@ static int __devinit sm501fb_probe(struct
>> platform_device *pdev)
>>
>> if (info->pdata == NULL) {
>> dev_info(dev, "using default configuration data\n");
> -Original Message-
> From: Gala Kumar-B11780
> Sent: Tuesday, January 25, 2011 3:01 PM
> To: Liu Yu-B13201
> Cc: linuxppc-dev@lists.ozlabs.org; Gala Kumar-B11780
> Subject: Re: [PATCH] e500: Erratum cpu a005 workaround
>
>
> On Jan 25, 2011, at 12:02 AM, Liu Yu wrote:
>
> > This er
> I'm trying to use FSL DMA engine to perform DMA transfer from
> memory buffer obtained by kmalloc() to PCI memory. This is on
> custom board based on P2020 running linux-2.6.35. The PCI
> device is Altera FPGA, connected directly to SoC PCI-E controller.
You'll need to use the dma engine that
Hi Ira,
On 01/25/2011 02:18 AM, Ira W. Snyder wrote:
On Tue, Jan 25, 2011 at 01:39:39AM +0200, Felix Radensky wrote:
Hi Ira, Scott
On 01/25/2011 12:26 AM, Ira W. Snyder wrote:
On Mon, Jan 24, 2011 at 11:47:22PM +0200, Felix Radensky wrote:
Hi,
I'm trying to use FSL DMA engine to perform DMA
> memcpy_toio() works fine, the data is written correctly. After
> DMA, the correct data appears at offsets 0xC, 0x1C, 0x2C, etc.
> of the destination buffer. I have 12 bytes of junk, 4 bytes of
> correct data, then again 12 bytes of junk and so on.
Does your Avalon MM slave decode the 4 byte enab
On Tue, Jan 25, 2011 at 04:32:02PM +0200, Felix Radensky wrote:
> Hi Ira,
>
> On 01/25/2011 02:18 AM, Ira W. Snyder wrote:
> > On Tue, Jan 25, 2011 at 01:39:39AM +0200, Felix Radensky wrote:
> >> Hi Ira, Scott
> >>
> >> On 01/25/2011 12:26 AM, Ira W. Snyder wrote:
> >>> On Mon, Jan 24, 2011 at 11:
> > custom board based on P2020 running linux-2.6.35. The PCI
> > device is Altera FPGA, connected directly to SoC PCI-E
controller.
> This sounds like your FPGA doesn't handle burst mode accesses
> correctly.
> A logic analyzer will help you prove it.
He is doing PCIe, not PCI.
A
On Tue, 25 Jan 2011 16:34:49 +
David Laight wrote:
>
> > > custom board based on P2020 running linux-2.6.35. The PCI
> > > device is Altera FPGA, connected directly to SoC PCI-E
> controller.
>
>
> > This sounds like your FPGA doesn't handle burst mode accesses
> > correctly.
-Original Message-
From: Greg KH [mailto:g...@kroah.com]
Sent: Saturday, January 22, 2011 7:02 PM
To: tma...@apm.com
Cc: linux-...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V8 00/10] Add-Synopsys-DesignWare-HS-USB-OTG-driver
On Wed, Jan 19, 2011 at 02:57:16PM -0800
Hi,
The cpufreq driver I wrote for the 750gx causes a kernel panic in 2.6.36.
This is from a screen shot:
[c6035f30] [c001014c] timer_interrupt+0x13c/0x19c
[c6035f40] [c0013294] ret_from_except+0x0/0x14
--- Exception: 901 at 0x1000c694
LR = 0x1000f3e4
Instruction dump:
4b48 38610008 4be7
On Tue, 2011-01-25 at 17:54 -0600, kevin diggs wrote:
> Hi,
>
> The cpufreq driver I wrote for the 750gx causes a kernel panic in 2.6.36.
>
> This is from a screen shot:
>
> [c6035f30] [c001014c] timer_interrupt+0x13c/0x19c
> [c6035f40] [c0013294] ret_from_except+0x0/0x14
> --- Exception: 901 at
- add commandline options:
sm501fb.mode:
Specify resolution as "x[-][@]"
sm501fb.bpp:
Specify bit-per-pixel if not specified mode
- Add support for encoding display mode information
in the device tree using verbatim EDID block.
If the "edid" entry in the "smi,sm501" node is presen
- add binding to OF, compatible name "smi,sm501"
Signed-off-by: Heiko Schocher
cc: linux-fb...@vger.kernel.org
cc: devicetree-disc...@ozlabs.org
cc: Ben Dooks
cc: Vincent Sanders
cc: Samuel Ortiz
cc: linux-ker...@vger.kernel.org
cc: Randy Dunlap
cc: Paul Mundt
---
- changes since v1:
add
14 matches
Mail list logo
