t be accessed using mmap("/dev/mem", ...)
in application, the data read in mapped virtual address is not the
data writing by
FPGA.
Should I write a kernel driver, or use another device for mmap()?
--
Cyberman Wu
On Fri, Nov 9, 2012 at 9:11 AM, Tejun Heo wrote:
> Hello,
>
> On Fri, Nov 09, 2012 at 08:53:49AM +0800, Cyberman Wu wrote:
>> A lot of these message on many CPU:
>
> What I'm really curious about is the *first* exception.
>
> Is the following the first one?
that
problem. Then I checked
the newest kernel and it seems should have the same issue.
I only tested it on Gx platform from Tilera, but that second exception
should occur on
any platform if kworker got exception and can't be recovered.
On Thu, Nov 8, 2012 at 12:28 AM, Tejun Heo wrote:
&g
;ve checked code
of kernel version 3.6.5,
it seems have the same process, only with files and functions split.
--
Cyberman Wu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
7;s a good bias? (I'm
>> inclined to think 64K rather than 4K.)
>
> I/O space is very limited to begin with (many architectures only
> *have* 64K), so I hesitate to add a bias in the PCI core. But we do
> something similar in arch_remove_reservations(), and I think you could
is
not really used.
When the same card inserted into x86 platform, the allocated I/O space
is not start from 0,
so it works fine.
On Fri, Oct 26, 2012 at 4:03 PM, Bjorn Helgaas wrote:
> [+cc Chris, also a few comments below]
>
> On Fri, Oct 26, 2012 at 12:59 AM, Cyberman Wu wrote:
>&
kernel/pci_gx.c
2012-10-22
14:56:59.783096378 +0800
+++ Tilera_src/src/linux-2.6.40.38/arch/tile/kernel/pci_gx.c2012-10-26
13:55:02.731947886 +0800
@@ -368,6 +368,10 @@
int num_trio_shims = 0;
int ctl_index = 0;
int i, j;
+// Modified by Cyberman Wu on Oct 25th, 2012.
een so some output lost)
The first time Ctrl-C quit strace, but it doesn't work second time.
It seem ps hang while it read /proc/5/stat, which I've check it 'comm'
and is some thing like
'kworker/u:0'. The system now stop response for any input, even in
serial port, so I ca
tus, its stack can't be dumped. Is there
any exist mechanism can be used to
get it stack, or other information, to help me figure out what's the
cause of ps pend on *RUNNING*?
System information:
# uname -a
Linux localhost 2.6.38.8-MDE-4.0.0.141101 #7 SMP Fri Sep 28 21:46:08
CST 2
9 matches
Mail list logo
