I need 2 different major # for 1 pci device. Are there any examples of how to do this? I'm wondering about whether this would be a problem with pci_register_driver. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

Not any problem. Just register two character devices. Rene. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

FREE for download (YES, FREE): http://portal.acm.org/toc.cfm?id=1400097 Minding the gap: R&D in the Linux kernel Muli Ben-Yehuda, Eric Van Hensbergen, Marc Fiuczynski Introducing technology into the Linux kernel: a case study Paul E. McKenney, Jonathan Walpole Extending futex for kernel to user notification Helge Bahmann, Konrad Froitzheim Plan 9 authentication in Linux Ashwin Ganti Towards achieving fairness in the Linux scheduler Chee Siang Wong, Ian Tan, Rosalind Dee...

On Wed, Aug 13, 2008 at 1:28 AM, Santosh Pradhan p_name and q_name are variable allocated from the stack, and it will always be different address from the stack. Yes, the optimizer can shrink them to the same address, but whether the optimizer does it or it does not matter. Because u are not comparing the address - which is &p_name == &q_name, but u are comparing the value inside the addresses. But since u have assigned it to the same address of NAME, it will always print HELLO world...

Hello Rene and everyone, Ah....ok I agreed, the program below meet exactly your two statement above: #include<stdio.h> #define NAME "santosh" #define NAME1 "santosh" int main() { char *p_name = NAME; char *q_name = NAME1; if (p_name == q_name) printf("Hello, World\n"); return 0; } And of course, now if p_name and q_name are the same value, it is an optimization. After compiling without optimization gcc -O0, the output is as below: 0x080483b4 &lt...

Thank you all. Regards, Santosh

It clearly says that gcc version 3.4.6 will do so. And it makes perfect sense to do so ofcourse but as far as C the language is concerned, it's unspecified and I can assure you that I've used compilers that did not. (whether or not I was happy to be using those compilers is secondary) Rene. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

Yeah... I completely agree :-) ... the output will be compiler dependant.......was just saying that if you use gcc you are guaranteed -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

Thank you for comment. Are there any other persons who use ramfs/ramdisk with special -- Kinds regards, MinChan Kim -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

not sure what u mean. but i think what u are asking is how to find out at any point, when the CPU is stopped, which part of the kernel it is executing at that point, right? One way, how programmers can find that out is to do stack dump. The function is dump_stack() in the kernel source. but to understand the meaning of the stack dump, u need to know how the stack is organized, frame pointer and it usage by GCC, stack frame per function called, what is stack walking etc. Not really pertaining...

You don't even need to do that, just ask the kernel to emit the hotplug messages for the hardware it found and the modules will be automatically loaded. See the startup code for any modern distro for how to do this in a few lines of shell script, or a simple .c program. thanks, greg k-h -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ