Hi guys:
I am a Chinese. I 've join in this mailgroup for a while. But I find it
hard to join in these discussion, because I am a newb for linux and my English
is just at the beginning. So I want to find a partner to do some language
exchange, that I help you improving your Chinese and you t
Yes that's right Mulyadi, As this was my first encounter with ksymoops
hence i didn't know much about it. Last night i was going through the
back trace for this oops and got lost while trying to figure the root cause
Keeping track of function calls in large project can be
very perplexing. Right now
Hi...
On Thu, Apr 23, 2009 at 2:29 PM, amit mehta wrote:
> Thanks for your replies, i just wanted to know how to debug
> such kernel OOPS, Forget about this particular OOPS, i just wanted to know
> how you proceed further when you get something similar. As Ramesh told,
> 'ksymoops' can be
> helpf
On Thu, Apr 23, 2009 at 11:55:12AM +0300, Behzat wrote:
>
> Hello everyone,
>
> I've some trouble with usb webcam driver. I think it's really strange.
>
>
> static struct video_device usbcam_videodev_template = {
> .name = "usbcam-unknown",
> .type
i think this use to diff kernel space or user space or iomem like cpu
ring 0 to ring 3.
include/Linux/compiler.h:
#ifdef __CHECKER__
# define __user __attribute__((noderef, address_space(1)))
# define __kernel /* default address space */
# define __iomem __attribute__((noderef, address_space(2)))
I think in the embedded system always use "mem=" parameter to boot
kernel and reserve a continuous memory then provide for some device
use as their private "buffer",like io-mem remap in the kernel space to
use.
BRs
Lin
2009/3/31 Peter Teoh :
> On Tue, Mar 31, 2009 at 11:11 AM, Peter Chen wrote:
Hello everyone,
I've some trouble with usb webcam driver. I think it's really strange.
static struct video_device usbcam_videodev_template = {
.name = "usbcam-unknown",
.type = VFL_TYPE_GRABBER,
.type2 = VID_TYPE_CA
Hi,
I recently came across the below #define
# define __iomem __attribute__((noderef, address_space(2)))
Browsing the internet I could find the following detail:
"iomem" means two separate things: it means that sparse should complain
if the pointer is ever dereferenced (it's a "noderef" p
On Thu, Apr 23, 2009 at 2:20 AM, Greg Freemyer wrote:
> On Wed, Apr 22, 2009 at 3:38 PM, Rohit Sharma wrote:
>> Arun, i suggest that if you are using this for IPC then , better use pipes.
>>
>> And if you really want to use fd in another application then
>> pass the file descriptor to exec after
Thanks for your replies, i just wanted to know how to debug
such kernel OOPS, Forget about this particular OOPS, i just wanted to know
how you proceed further when you get something similar. As Ramesh told,
'ksymoops' can be
helpful.
__amit
On Thu, Apr 23, 2009 at 11:18 AM, Himanshu Chauhan wrote
10 matches
Mail list logo
