Hi Steven,
Steven King wrote:
On Tuesday 23 June 2009 10:57:35 Greg Ungerer wrote:
Hi Steven,
This looks pretty good to me.
Do you want me to apply the the m68knommu git tree?
(Ideally I'll push it to Linus in the 2.6.32 merge window).
That would be great. There are some things I'd like to
Hi,
I find one interrupt issue on my coldfire platform on linux-2.6.29
version (mcf54451evb board, mmu, NFS as rootfs).
After system boot up, I do following test:
on target board, run command: nc -l -p > /dev/null &
on host PC, run command: dd if=/dev/zero | nc 10.192.208.230 (target ip)
333
Thanks Greg/Matt/Cris' reply. I know it's not the issue now :)
> Most of the ColdFire UART blocks have no transmit FIFO, so you
> are going to get 1 interrupt per character. The above block has
> at least 500 characters in it (including white space). Then include
> the extra command prompt and y
Hi Lanttor,
Lanttor wrote:
Hi,
I find one issue of UART on my coldfire platforms (mcf54451evb board).
I use the linux-2.6.29, and use drivers/serial/mcf.c and
drivers/serial/serial_core.c as my uart driver source.
Following is my test steps -- run command: cat /proc/interrupts two
times contig
Mike Frysinger wrote:
There is a common macro now for testing mixed pointer/errno values, so use
that rather than handling the casts ourself.
Signed-off-by: Mike Frysinger
Acked-by: Greg Ungerer
---
fs/binfmt_flat.c | 22 ++
1 files changed, 10 insertions(+), 12 d
Jivin Mike Frysinger lays it down ...
> There is a common macro now for testing mixed pointer/errno values, so use
> that rather than handling the casts ourself.
>
> Signed-off-by: Mike Frysinger
Acked-by: David McCullough
Cheers,
Davidm
> ---
> fs/binfmt_flat.c | 22 ++---
There is a common macro now for testing mixed pointer/errno values, so use
that rather than handling the casts ourself.
Signed-off-by: Mike Frysinger
---
fs/binfmt_flat.c | 22 ++
1 files changed, 10 insertions(+), 12 deletions(-)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_
Oh, I should stipulate that I also went through the sources of U-boot etc.
Could it also be possible that the DataFlash "environment" section has
something in it
that is read during start up ?
Best Regards,
Kris
> -Original Message-
> From: uclinux-dev-boun...@uclinux.org
> [mailto:uc
On Tue 30 Jun 2009 23:54, Haitao Zhang pondered:
> Hi,
>
> in mmu less system, stack overflow is extremely danger for userland
application,
> so i just try to take advantage from using GCC stack check options,
> BTW: our system is running on a ARM7TDMI, mmuless platform,
> and we use GCC 4.3.3, a
> I'm currently working on a driver for an I2C device (which is a bridge to SPI,
> just FYI) using the "new" driver model with probe/remove. My used uClinux
> version is 20080808. As this is done on a board (Coldfire 5208) with a fixed
> configuration I added a new I2C_BOARD_INFO to my i2c_board_in
Hi all,
I'm new to this list and (uC)linux overall.
However, with some persistence (and great interest in uClinux :-) I got the
uCLinux-dist
(20080808) ported and running smoothly on the Olimex SAM9-L9260 board
(similar to Atmel AT91SAM9260-EK).
I don't know yet how to go about patches or imple
Hi,
Wouldn't the mere output on your console cause UART transmit interrupts for
each character anyway ?
(I can't imagine that the debug console is polled.. ? :-)
The amount of console data would equate to 500+ TX interrupts, so AFAIK
that would make sense.
Unless the UART has a FIFO and the code *
12 matches
Mail list logo
