I'm recently porting Linux 2.6.32 to our custom board with MPC8247. We have a
NAND flash connected using GPCM mode of local bus. But after I search
through the Linux
source, there is no compatible like "fsl,gpcm-nand". And I can not
find any driver
that seems works for our scene.
Does Linux 2.6.32
2010/2/27 Scott Wood :
> On Fri, Feb 26, 2010 at 10:08:09AM +0800, Peter Pan wrote:
> There isn't one. I was not under the impression that such a configuration
> was even possible (how do you control ALE/CLE, for example?). There is a
> NAND driver that uses UPM, though -- perh
2010/2/27 Peter Pan :
> 2010/2/27 Scott Wood :
>> On Fri, Feb 26, 2010 at 10:08:09AM +0800, Peter Pan wrote:
>> There isn't one. I was not under the impression that such a configuration
>> was even possible (how do you control ALE/CLE, for example?). There is a
&g
e Makefile,
everything works fine.
2010/3/2 Peter Pan :
>
> We use Address A20 and A21 connect to ALE and CLE, the data bus is
> connected through a buffer.
> The RE is OE AND with CS. the WE is PBS0 AND with CS. CE pin is
> connect to ground. It works
> fine in VxWorks. And als
Recently, I'm porting Linux 2.6.32.6 to our customized MPC8247 based
board. Everything is fine out except my ethernets. I uses
cpm2-scc-enet and cpm2-fcc-enet drivers.
My ethernet works fine in U-Boot with the same setting, and our
previous Linux 2.6.22 is also working, so there should be nothing
w
driving it to 1). Will try to ask the hw guy if he
> remembers when he comes in tomorrow.
> Paul
>
> On 3/30/2010 8:46 PM, Peter Pan wrote:
>> Recently, I'm porting Linux 2.6.32.6 to our customized MPC8247 based
>> board. Everything is fine out except my ethernets.
or our external hardware watchdog, it works fine. Then I
use the low level driver in the mii-bitbang.c, it still works
incorrect, all I get from MDIO is 1.
I'm really confused.
2010/3/31 Scott Wood :
> Peter Pan wrote:
>>
>> Recently, I'm porting Linux 2.6.32.6 to our customiz
the old kernel, but
> since the TA bit as not checked we never knew.
> Not sure if this is applicable but might be worth verifying.
> Paul
>
>
> On 3/31/2010 7:56 PM, Peter Pan wrote:
>> Yes, the PHY address is correct, I've checked the schematics, and
>> 2.6.22 is
I'm porting Linux 2.6.32.6 to our MPC8247 based board. We use SCC3 and
SCC4 as ethernet port. These two ports are connect with LXT905 PHY
chip.
I'm now using fs_enet driver, how should I config the scc port in dtc
file. I copied from mgcoge.dts file, and my dtc file of scc enet is
follows:
Wood :
> Peter Pan wrote:
>>
>> I'm porting Linux 2.6.32.6 to our MPC8247 based board. We use SCC3 and
>> SCC4 as ethernet port. These two ports are connect with LXT905 PHY
>> chip.
>> I'm now using fs_enet driver, how should I config the scc port in dtc
>
I'm porting Linux 2.6.32.6 to my MPC8247 based board. Our FCC1 and
FCC2 are used as 100MBps ethernet ports. MDIO is used to connect with
PHY chip. During boot, the of driver is checking the PHYID, it gets
all Fs. But after I comment the following lines:
//if ((phy_id & 0x1fff) == 0x1fff)
//
linux 2.6.22 is working correctly on my board. So, I think this is due
to the difference between them.
I will check the boot time difference between 2.6.22 and my new port.
Hope that will give me a clue.
2010/4/23 Andy Fleming :
> On Thu, Apr 22, 2010 at 9:36 PM, Peter Pan wrote:
>> I&
12 matches
Mail list logo
