> From: Anton Vorontsov
> Subject: Re: MPC8313: fsl_elbc_nand and MDR
> To: "Scott Wood"
> Cc: linuxppc-...@ozlabs.org, "Ron Madrid"
> Date: Monday, April 26, 2010, 12:29 PM
> On Mon, Apr 26, 2010 at 02:28:00PM
> -0500, Scott Wood wrote:
> > Ron Ma
> From: Scott Wood
> Subject: Re: MPC8313: fsl_elbc_nand and MDR
> To: "Ron Madrid"
> Cc: linuxppc-...@ozlabs.org
> Date: Monday, April 26, 2010, 12:10 PM
> Ron Madrid wrote:
> > When you say current UPM code are you talking about
> > fsl_upm.c? Caus
> From: Scott Wood
> Subject: Re: MPC8313: fsl_elbc_nand and MDR
> To: "Ron Madrid"
> Cc: linuxppc-...@ozlabs.org
> Date: Monday, April 26, 2010, 11:34 AM
> Ron Madrid wrote:
> > I am having what appears to be a little conflict
> > with this driver, par
I am having what appears to be a little conflict
with this driver, particularly with the MDR. My
hardware uses NAND flash and an FPGA connected
through the UPM. After the kernel is up and
running, sometimes I cannot verify the data in
the UPM RAM array. I am guessing right now that
this is due t
I'm getting a bunch of these after I 'reboot' or 'poweroff'
several times.
Empty flash at 0x0056205c ends at 0x00562800
Empty flash at 0x00565334 ends at 0x00565800
Empty flash at 0x00576104 ends at 0x00576800
JFFS2 notice: (848) check_node_data: wrong data CRC
in data node at 0x00577034: read 0x
Quick question. I have a 8313 based custom board. If I wanted
to include my config file and dts into mainline are there any
restrictions or requirements? Just curious.
Thanks, please let me know.
Ron
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.o
--- On Fri, 11/13/09, Scott Wood wrote:
> > And when this
> > does happen in usually causes a lockup, so I haven't
> > been able to check the
> > status of any arbiter registers.
>
> The system is up long enough to print an oops; you could
> stick some output in the trap handler.
I've never done
--- On Fri, 11/13/09, Scott Wood wrote:
> From: Scott Wood
> Subject: Re: Bus Error on MPC8313
> To: "Ron Madrid"
> Cc: linuxppc-...@ozlabs.org
> Date: Friday, November 13, 2009, 11:33 AM
> Ron Madrid wrote:
> > I wrote a custom driver for an MPC8313 b
I wrote a custom driver for an MPC8313 based board. Everything seems to
have been working for a long time, but now one of my IOCTL functions seems
to be having a problem. I'm getting a "Bus error" reported by my
application and also a kernel "Oops". Here's what the kernel is reporting.
Oops: M
I have a custom board based on the MPC8313ERDB and have communications
capabilities over Ethernet using internet sockets. Basically, just data
transfer from the host (my board) to a client (a PC). I want to be able to
perform similar transactions across USB.
I have done some cursory reading but
--- On Thu, 3/26/09, Michael Ellerman wrote:
> From: Michael Ellerman
> Subject: Re: Bootlog bug?
> To: ron_mad...@sbcglobal.net
> Cc: linuxppc-dev@ozlabs.org
> Date: Thursday, March 26, 2009, 3:51 PM
> On Thu, 2009-03-26 at 11:25 -0700, Ron Madrid wrote:
> > I have
I have a little problem with my boot messages. I'm not sure what this is, but
does anyone have any ideas as to what it could be or what further information I
could give to help track this down. As of now this is not manifesting itself,
but I don't know what it might do.
Using MPC831x RDB mac
Thank you. That took care of it. I knew it was something small.
Ron
- Original Message
> From: Kumar Gala
> To: Ron Madrid
> Cc: linuxppc-dev@ozlabs.org
> Sent: Thursday, December 11, 2008 4:21:26 PM
> Subject: Re: Problem building kernel
>
>
> On Dec 1
Hello all,
I got the latest kernel from git://git.denx.de/linux-2.6-denx.git and after
configuring with menuconfig I am seeing these errors. I feel like this
could be something simple that I am just unaware of, but I'm not sure
and haven't been able to find anything useful when doing a web search
Thank you. I will send it to the netdev list.
Ron Madrid
- Original Message
> From: Kumar Gala <[EMAIL PROTECTED]>
> To: Ron Madrid <[EMAIL PROTECTED]>
> Cc: linuxppc-dev@ozlabs.org
> Sent: Wednesday, November 5, 2008 3:33:55 PM
> Subject: Re: [PATCH] Add
This patch will add support for the Marvell 88E1118 PHY which supports gigabit
ethernet among other things.
Signed-off-by: Ron Madrid <[EMAIL PROTECTED]>
---
drivers/net/phy/marvell.c | 66 +
1 files changed, 66 insertions(+), 0 deletions(-)
Thank you (once again). I found the information.
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > /* Large Page FLASH with FMR[ECCM] = 0 */
> > static struct nand_ecclayout fsl_elbc_oob_lp_eccm0 = {
> > .eccbytes = 12,
> > .eccpos =
11, 13}, {27, 13}, {43, 13}, {59, 5} },
+ .oobfree = { {2, 6}, {11, 13}, {27, 13}, {43, 13}, {59, 5} },
.oobavail = 48,
};
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I know I asked about this in the past, but I can't remember where it was
> &
Scott,
I know I asked about this in the past, but I can't remember where it was left.
Did this get
resolved in some other repository that isn't the main linux-2.6 repository? If
it didn't I think
I might have a solution. BTW I'm using 2.6.26-rc8
Ron
__
Thank you for the help (again). I've got my driver registering the isr on it's
own now. In the
end the problem was the dts and also not using irq_of_parse_and_map.
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I don't see a "dma"
t;fsl,elo-dma-channel";
cell-index = <3>;
reg = <0x180 0x80>;
interrupt-parent = <&ipic>;
interrupts = <71 0x8>;
printk(kModuleName "-SIMPC_open: found IRQ %d\n", pdx.irq);
--- Kumar Gala <[EMAIL PROTECTED]> wrote:
> What does your code actually look like. In your driver how are you
> getting the IRQ value that you pass to request_irq?
>
> - k
>
> On Jun
So are you implying that the request_irq function should work without any other
initialization
function before it?
Ron
--- Timur Tabi <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I don't know why request_irq is succeeding when the fsldma and dmaengine
> &g
using the same .dts in both cases?
>
> - k
>
> On Jun 13, 2008, at 2:02 PM, Ron Madrid wrote:
>
> > So after I've built the kernel to include the dmaengine and fsldma
> > drivers, my driver is allowed
> > to register its ISR via request_irq. However, if th
t
> set of APIs.
>
> - k
>
> On Jun 12, 2008, at 3:04 PM, Ron Madrid wrote:
>
> > Well in that case wouldn't I need to use the fsldma driver? Or is
> > dmaengine a generic dma driver?
> >
> > Ron
> > --- Kumar Gala <[EMAIL PROTE
Well in that case wouldn't I need to use the fsldma driver? Or is dmaengine a
generic dma driver?
Ron
--- Kumar Gala <[EMAIL PROTECTED]> wrote:
>
> On Jun 12, 2008, at 2:35 PM, Ron Madrid wrote:
>
> > I'm trying to write a driver that would make use of the
I'm trying to write a driver that would make use of the DMA on the MPC8313.
I'm attempting to
register the interrupt with request_irq but it is not passing. Is there
something that I need to
do before I call request_irq, maybe in the dts or somewhere else?
Ron
_
d for
ECC, bad block marker, and so on. This is causing a
large problem as now my blocks are being marked as
bad.
So my second question is, where is the code that
performs this "formatting" of the NAND device
immediately after mounting of the rootfs?
Ron Madrid
__
e a patch if someone could point me in the right
direction.
Let me know if I'm off base here, but I think this is
where my problem is.
Ron Madrid
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> You may want to try increasing the OR[SCY] field or
> other timing
> parameters associated with the NAND flash.
So are you saying that when this happened in the past
it was a timing issue? This change would need to
happen in u-boot correct?
Ron
__
In which function should I start searching for this
problem? What would cause a block to be marked bad?
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I have tried the latest code and now, I'm able to
> > write a limited amount. After which when
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I'm trying to make new directories, create files,
> save
> > changes to files, etc. and when I reboot my
> changes
> > are not being saved. I'm sorry if this is vague,
> but
>
:cc:53:ba:fd:e3:e9:86:3d:90:c7:9b:22
Starting the dropbear ssh server:
I see this when rebooting
/ # reboot
/ # Stopping the dropbear ssh server:
Stopping inetd:
Unmounting filesystems
The system is going down NOW !!
Sending SIGTERM to all processes.
Please stand by w
33 matches
Mail list logo
