Mail Index

• Thread Index

• Re: Inter Module communication
  • From: Jon Masters
• Re: Can a module block?
  • From: Jon Masters
• Plzzz help me
  • From: cranium2003
• Re: how does kernel know?
  • From: mohanlal jangir
• RE: Seek Help !!! (about getting a pointer to sys_call_table)
  • From: Thekkedath, Gopakumar
• Re: Plzzz help me
  • From: Raghav K
• Re: Read operation on Block device.
  • From: manish regmi
• Re: Seek Help !!! (about getting a pointer to sys_call_table)
  • From: sainath vellal
• Re: Seek Help !!!
  • From: Prasad
• Re: Can a module block?
  • From: Raghav K
• Re: how does kernel know?
  • From: Zeeshan Ali
• RE: Seek Help !!! (about getting a pointer to sys_call_table)
  • From: Dhiman, Gaurav
• Re: Seek Help !!!
  • From: Brandon Niemczyk
• Re: Plzzz help me
  • From: Ravi Kumar
• Re: Kgdb related prob. (err - "Cannot find bounds of current funtion"!!)
  • From: Mandeep Sandhu
• Re: how does kernel know?
  • From: Greg KH
• RE: Seek Help !!!
  • From: Dhiman, Gaurav
• Reading from keyboard in the module
  • From: Rakesh Jagota
• library call in modules
  • From: Rakesh Jagota
• sockfd_put(sock)
  • From: Rakesh Jagota
• register_disk query
  • From: gautham hegde
• mutual excluision/synchronisation in the kernel
  • From: Rakesh Jagota
• RE: Inter Module communication
  • From: Dhiman, Gaurav
• sys_close
  • From: Rakesh Jagota
• Re: how does kernel know?
  • From: Zeeshan Ali
• Re: how does kernel know?
  • From: Greg KH
• Re: library call in modules
  • From: manish regmi
• RE: library call in modules
  • From: Dhiman, Gaurav
• RE: Seek Help !!! (about getting a pointer to sys_call_table)
  • From: Thekkedath, Gopakumar
• compilation issue
  • From: Rakesh Jagota
• Re: compilation issue
  • From: Fawad Lateef
• One query
  • From: Geetha S.L
• Re: RE: library call in modules
  • From: jhoney jhoney
• Re: One query
  • From: suneesh
• Re: Data strcuture during insmode
  • From: Shine Mohamed Jabbar
• Re: One query
  • From: Geetha S.L
• Re: One query
  • From: Geetha S.L
• RE: One query
  • From: Bollapalli.Chakravarthy
• RE: library call in modules
  • From: manish regmi
• RE: library call in modules
  • From: manish regmi
• Re: Seek Help !!!
  • From: Ashish Mishra
• Re: how does kernel know?
  • From: Mark Hounschell
• Re: mutual excluision/synchronisation in the kernel
  • From: Frank.A.Uepping
• Re: Kgdb related prob. (err - "Cannot find boundsof current funtion"!!)
  • From: patil_a . etech . haw-hamburg
• Re: One query
  • From: Rakesh Jagota
• Re: compilation issue
  • From: Rakesh Jagota
• Understanding Interrupts
  • From: mbrennan
• Re: Understanding Interrupts
  • From: Mandeep Sandhu
• RE: Understanding Interrupts
  • From: Thekkedath, Gopakumar
• RE: Understanding Interrupts
  • From: Thekkedath, Gopakumar
• RE: Understanding Interrupts
  • From: Naidu, Venkata
• RE: Understanding Interrupts
  • From: Naidu, Venkata
• Real Estate Investment Software
  • From: Real Estate Investment Software - InvestSoft
• RE: Understanding Interrupts
  • From: Dhiman, Gaurav
• Re: Plzzz help me
  • From: Shakthi Kannan
• Re: how does kernel know?
  • From: Jon Masters
• Re: Inter Module communication
  • From: Jon Masters
• Re: Reading from keyboard in the module
  • From: Alberto Rodriguez Galdo
• Re: sockfd_put(sock)
  • From: Alberto Rodriguez Galdo
• md hangs while rebuilding
  • From: Shesha B.
• about reference counter
  • From: lml
• Re: about reference counter
  • From: Greg KH
• Re: md hangs while rebuilding
  • From: bert hubert
• Re: about reference counter
  • From: lml
• Re: about reference counter
  • From: Greg KH
• Re: about reference counter
  • From: lml
• Re: md hangs while rebuilding
  • From: Shesha B.
• Re: about reference counter
  • From: Greg KH
• Re: about reference counter
  • From: Robert Love
• Re: Understanding Interrupts
  • From: Michael Brennan
• Re: Understanding Interrupts
  • From: Michael Brennan
• Kernel string implementation I386.
  • From: manish regmi
• Query related with Book Linux Device Drivers
  • From: Dinesh Ahuja
• Re: Seek Help !!!
  • From: matrix reloaded
• Seek Help !!!
  • From: seshu
• RE: Seek Help !!!
  • From: Dhiman, Gaurav
• understanding /proc/cmdline
  • From: aq
• Re: understanding /proc/cmdline
  • From: Jon Masters
• Accessing memory with /dev/port
  • From: aq
• help for reserving HIGHMEM for my module on x86, but not using mem=<memory>
  • From: Fawad Lateef
• why does switch_to need three arguments?
  • From: Bao zhao
• Re: understanding /proc/cmdline
  • From: manish regmi
• Re: Accessing memory with /dev/port
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: manish regmi
• Re: Seek Help !!!
  • From: manish regmi
• Re: Query related with Book Linux Device Drivers
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Bao zhao
• Re: u-boot and NOR flash
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Jon Masters
• Re: Query related with Book Linux Device Drivers
  • From: Dinesh Ahuja
• Re: why does switch_to need three arguments?
  • From: Rik van Riel
• Re: Seek Help !!!
  • From: Jon Masters
• Re: Query related with Book Linux Device Drivers
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Rik van Riel
• Re: why does switch_to need three arguments?
  • From: Jon Masters
• Re: why does switch_to need three arguments?
  • From: Rik van Riel
• Help on sock pack option
  • From: Vanitha Ramaswami
• test mail
  • From: gautham hegde
• vsyscall example?
  • From: aq
• Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Dinesh Ahuja
• RE: Understanding Interrupts
  • From: Naidu, Venkata
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Arjan van de Ven
• Re: Understanding Interrupts
  • From: Jon Masters
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Greg KH
• Re: vsyscall example?
  • From: Jirka Kosina
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Prasad
• Error in Close(closing sockets)
  • From: Rakesh Jagota
• changes required for making modular driver -> a buitl-in one
  • From: Mandeep Sandhu
• Re: compilation issue
  • From: matrix reloaded
• Re: changes required for making modular driver -> a buitl-in one
  • From: mohanlal jangir
• Request for subscription
  • From: santosh gondi
• Problem with close in Kernel
  • From: Rakesh Jagota
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Dinesh Ahuja
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Dinesh Ahuja
• Re: changes required for making modular driver -> a buitl-in one
  • From: Kiran Kumar Immidi
• Re: compilation issue
  • From: Anupam Kapoor
• Re: Re: compilation issue
  • From: matrix reloaded
• Re: changes required for making modular driver -> a buitl-in one
  • From: Anupam Kapoor
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jon Masters
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jon Masters
• Re: changes required for making modular driver -> a buitl-in one
  • From: Mandeep Sandhu
• fork, clone and vfork
  • From: sanjayk
• prob. getting exact line of oops using kgdb.
  • From: Mandeep Sandhu
• Re: prob. getting exact line of oops using kgdb.
  • From: Kiran Kumar Immidi
• Re: prob. getting exact line of oops using kgdb.
  • From: Anupam Kapoor
• RAM or "empty"?
  • From: Ribamar Santarosa de Sousa
• Mutual Exclusion in Kernel
  • From: Rakesh Jagota
• RE: Mutual Exclusion in Kernel
  • From: Dhiman, Gaurav
• Re: Mutual Exclusion in Kernel
  • From: Omanakuttan
• Re: RAM or "empty"?
  • From: Omanakuttan
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Dinesh Ahuja
• How to read a file from kernel ?
  • From: Danett song
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jon Masters
• How to read from kernel ?
  • From: Danett song
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Prasad
• Re: Re: compilation issue
  • From: Rakesh Jagota
• Re: compilation issue
  • From: Rakesh Jagota
• Problem with Server socket
  • From: Rakesh Jagota
• Implementation of netstat program
  • From: Rakesh Jagota
• RE: How to read from kernel ?
  • From: Brandon Niemczyk
• RE: Mutual Exclusion in Kernel
  • From: Brandon Niemczyk
• Re: RAM or "empty"?
  • From: Learner
• RE: Mutual Exclusion in Kernel
  • From: peyush
• RE: RAM or "empty"?
  • From: Thekkedath, Gopakumar
• mmap
  • From: Cristina Rivera
• RE: Mutual Exclusion in Kernel
  • From: matrix reloaded
• RE: RAM or "empty"?
  • From: Learner
• RE: RAM or "empty"?
  • From: Thekkedath, Gopakumar
• Plz enter ur birthday
  • From: Vijay Kumar Agrawal, Noida
• Re: changes required for making modular driver -> a buitl-in one
  • From: Pavan Kumar
• Re: Mutual Exclusion in Kernel
  • From: Jan Hudec
• Re: RAM or "empty"?
  • From: Jon Masters
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jon Masters
• Re: RAM or "empty"?
  • From: Mandeep Sandhu
• calling sys_ipc with linux 2.6
  • From: Simone Vellei
• RE: RAM or "empty"?
  • From: Thekkedath, Gopakumar
• Re: RAM or "empty"?
  • From: Ribamar Santarosa de Sousa
• Re: RAM or "empty"?
  • From: Ribamar Santarosa de Sousa
• RE: RAM or "empty"?
  • From: Thekkedath, Gopakumar
• Re: calling sys_ipc with linux 2.6
  • From: Arjan van de Ven
• Re: RAM or "empty"?
  • From: Ribamar Santarosa de Sousa
• Re: RAM or "empty"?
  • From: Learner
• Re: RAM or "empty"?
  • From: Learner
• Re: RAM or "empty"?
  • From: Om
• Re: RAM or "empty"?
  • From: Ribamar Santarosa de Sousa
• Re: Implementation of netstat program
  • From: Malita, Florin
• Re: Implementation of netstat program
  • From: Alberto Rodriguez Galdo
• using NMI watchdog for debugging "hanging"
  • From: Ed L Cashin
• Association between block device and block_device struct
  • From: Ahmed A
• context switch values "C"
  • From: FD
• Re: context switch values "C"
  • From: Robert Love
• Re: Association between block device and block_device struct
  • From: Vinod Sreedharan
• Obtaining property of block device.
  • From: Ahmed A
• Re: Association between block device and block_device struct
  • From: Ahmed A
• Re: Association between block device and block_device struct
  • From: Bijoy Thomas
• Re: Association between block device and block_device struct
  • From: Ahmed A
• Re: changes required for making modular driver -> a buitl-in one
  • From: Kiran Kumar Immidi
• Re: context switch values "C"
  • From: FD
• Crypto API history.
  • From: patryk
• Re: Obtaining property of block device.
  • From: Vinod Sreedharan
• __request_resource implemenation doubt
  • From: Mandeep Sandhu
• How to intercept sys_exit()...
  • From: Prasad
• Re: Re: Association between block device and block_device struct
  • From: Vinod Sreedharan
• Crypto API history.
  • From: patryk
• Re: How to intercept sys_exit()...
  • From: matrix reloaded
• Re: How to intercept sys_exit()...
  • From: Arjan van de Ven
• Re: Crypto API history.
  • From: Jon Masters
• RE: __request_resource implemenation doubt
  • From: Thekkedath, Gopakumar
• RE: __request_resource implemenation doubt
  • From: Mandeep Sandhu
• RE: __request_resource implemenation doubt
  • From: Thekkedath, Gopakumar
• RE: __request_resource implemenation doubt
  • From: Mandeep Sandhu
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jirka Kosina
• Re: How to read a file from kernel ?
  • From: Jirka Kosina
• Virus Found in message "Test"
  • From: West, Jonathan
• Problem creating an RTAI-enabled kernel
  • From: Raja . Hayek
• Re: Problem creating an RTAI-enabled kernel
  • From: Stephane List
• Re: mmap
  • From: Ribamar Santarosa de Sousa
• RE: How to intercept sys_exit()...
  • From: Dhiman, Gaurav
• Re: using NMI watchdog for debugging "hanging"
  • From: Ed L Cashin
• RE: How to intercept sys_exit()...
  • From: Aboo Valappil
• RE: How to intercept sys_exit()...
  • From: Aboo Valappil
• Re: How to intercept sys_exit()...
  • From: Jon Masters
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: Jon Masters
• exec-shield improved ?
  • From: aq
• RE: How to intercept sys_exit()...
  • From: Dhiman, Gaurav
• Free itanium TUTORIAL kernekl
  • From: tuomo kortesmaa
• Free Itanium TUTORIAL kernel
  • From: tuomo kortesmaa
• inode in the read
  • From: Zeeshan Ali
• Re: Problem in calling System call [sys_mknod] in Kernel Module.
  • From: matrix reloaded
• problem in shared library.
  • From: prashanth M.N
• RE: inode in the read
  • From: Aboo Valappil
• memory used by kernel?
  • From: Mandeep Sandhu
• Re: memory used by kernel?
  • From: manish regmi
• Do intel smp machines always have an 8259A alike external PIC?
  • From: Bao zhao
• Re: memory used by kernel?
  • From: Mandeep Sandhu
• Re: exec-shield improved ?
  • From: Arjan van de Ven
• Re: memory used by kernel?
  • From: matrix reloaded
• Re: How to intercept sys_exit()...
  • From: aq
• Re: exec-shield improved ?
  • From: aq
• libpcap.a
  • From: Rakesh Jagota
• Re: How to intercept sys_exit()...
  • From: Arjan van de Ven
• Re: exec-shield improved ?
  • From: Arjan van de Ven
• Re: libpcap.a
  • From: suneesh
• RE: memory used by kernel?
  • From: Anand
• Character device interface over existing socket interface.
  • From: shankar krishnamurthy
• Re: exec-shield improved ?
  • From: aq
• Re: exec-shield improved ?
  • From: Arjan van de Ven
• Re: exec-shield improved ?
  • From: aq
• Re: exec-shield improved ?
  • From: Arjan van de Ven
• Re: memory used by kernel?
  • From: Jon Masters
• Clearning concepts mentioned in Linux Device Drivers
  • From: Dinesh Ahuja
• Re: Clearning concepts mentioned in Linux Device Drivers
  • From: SiM
• ASSIST.
  • From: lee
• struct buffer_head
  • From: prasanna wakhare
• Re: Clearning concepts mentioned in Linux Device Drivers
  • From: Dinesh Ahuja
• Re: struct buffer_head
  • From: Jon Masters
• Re: Clearning concepts mentioned in Linux Device Drivers
  • From: Jon Masters
• Re: problem in shared library.
  • From: Jon Masters
• excluding memory and accessing it.
  • From: Om
• where is __setup_start?
  • From: Om
• Re: excluding memory and accessing it.
  • From: Yuval Tanny
• Re: where is __setup_start?
  • From: Clemens Buchacher
• Re: Clearning concepts mentioned in Linux Device Drivers
  • From: Dinesh Ahuja
• Appending functionality in Character Device Driver
  • From: Dinesh Ahuja
• RE: where is __setup_start?
  • From: Huang, Roy
• RE: Appending functionality in Character Device Driver
  • From: Aboo Valappil
• copy_to/from_use query?
  • From: mohanlal jangir
• Problem killing a kernel_thread.
  • From: Praveen Nair
• RE: memory used by kernel?
  • From: Mandeep Sandhu
• Re: memory used by kernel?
  • From: Kiran Kumar Immidi
• RE: memory used by kernel?
  • From: Aboo Valappil
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: Problem killing a kernel_thread.
  • From: Jan Hudec
• RE: Problem killing a kernel_thread.
  • From: Aboo Valappil
• Switching back to real mode -Please help
  • From: Aboo Valappil
• Switching back to real mode -Please help
  • From: Aboo Valappil
• (no subject)
  • From: Daniele Zampollo
• Re: copy_to/from_use query?
  • From: Pavan Kumar
• Re: copy_to/from_use query?
  • From: Mandeep Sandhu
• USB Function driver
  • From: Narendra Kulkarni
• Re: copy_to/from_use query?
  • From: matrix reloaded
• Re: copy_to/from_use query?
  • From: Mandeep Sandhu
• Re: memory used by kernel?
  • From: Learner
• Re: copy_to/from_use query?
  • From: Pavan Kumar
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: copy_to/from_use query?
  • From: 200410
• Re: copy_to/from_use query?
  • From: Jon Masters
• Re: copy_to/from_use query?
  • From: Om
• Re: USB Function driver
  • From: Greg KH
• RE: Appending functionality in Character Device Driver
  • From: Dhiman, Gaurav
• RE: Appending functionality in Character Device Driver
  • From: Dinesh Ahuja
• RE: Appending functionality in Character Device Driver
  • From: Dinesh Ahuja
• Page/Buffer Cache: Traversing Dirty Buffers
  • From: Can Sar
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: copy_to/from_use query?
  • From: Jon Masters
• RE: memory used by kernel?
  • From: Naidu, Venkata
• Why should I include highmem.h?
  • From: Timur Tabi
• How to partition HardDisk
  • From: Rakesh Jagota
• Kernel stack
  • From: suthambhara nagaraj
• Re: Page/Buffer Cache: Traversing Dirty Buffers
  • From: Vinod Sreedharan
• RE: memory used by kernel?
  • From: Thekkedath, Gopakumar
• Re: How to partition HardDisk
  • From: Athul Acharya
• RE: Kernel stack
  • From: Dhiman, Gaurav
• Re: Kernel stack
  • From: suthambhara nagaraj
• RE: copy_to/from_use query?
  • From: Aboo Valappil
• unresolved_symbols_from_dcache.c
  • From: prasanna wakhare
• RE: Kernel stack
  • From: Thekkedath, Gopakumar
• RE: copy_to/from_use query?
  • From: Thekkedath, Gopakumar
• Re: copy_to/from_use query?
  • From: Jan Hudec
• request_firmware() example ?
  • From: aq
• Re: Kernel stack
  • From: aq
• Re: Why should I include highmem.h?
  • From: Jan Hudec
• Re: unresolved_symbols_from_dcache.c
  • From: Jan Hudec
• Re: memory used by kernel?
  • From: Jan Hudec
• Re: Kernel stack
  • From: Jan Hudec
• Re: request_firmware() example ?
  • From: Jan Hudec
• RE: unresolved_symbols_from_dcache.c
  • From: Aboo Valappil
• RE: unresolved_symbols_from_dcache.c
  • From: Aboo Valappil
• RE: copy_to/from_use query?
  • From: Aboo Valappil
• Re: Kernel stack
  • From: Jan Hudec
• Re: copy_to/from_use query?
  • From: Jon Masters
• Re: copy_to/from_use query?
  • From: Jon Masters
• RE: Page/Buffer Cache: Traversing Dirty Buffers
  • From: Aboo Valappil
• thread awareness of the scheduler
  • From: Nilanjan Roychowdhury
• Re: thread awareness of the scheduler
  • From: Anupam Kapoor
• Re: copy_to/from_use query?
  • From: Jan Hudec
• Re: Kernel stack
  • From: aq
• Re: Kernel stack
  • From: Jan Hudec
• RE: memory used by kernel?
  • From: Naidu, Venkata
• Re: memory used by kernel?
  • From: Jon Masters
• Re: Kernel stack
  • From: Jon Masters
• Re: Switching back to real mode -Please help
  • From: Jon Masters
• Re: Kernel stack
  • From: Jan Hudec
• orig_eax in user_regs_struct ?
  • From: aq
• Re: request_firmware() example ?
  • From: aq
• Re: request_firmware() example ?
  • From: Greg KH
• Re: orig_eax in user_regs_struct ?
  • From: Robert Love
• Last warning please update your account
  • From: eBay Billing department
• RE: memory used by kernel?
  • From: Aboo Valappil
• Re: kernel stack
  • From: suthambhara nagaraj
• RE: Kernel stack
  • From: Dhiman, Gaurav
• RE: Kernel stack
  • From: Thekkedath, Gopakumar
• Re: Kernel stack
  • From: suthambhara nagaraj
• reentrant ?
  • From: aq
• RE: reentrant ?
  • From: Dhiman, Gaurav
• Re: reentrant ?
  • From: Suresh Jayaram
• Re: thread awareness of the scheduler
  • From: matrix reloaded
• contributing to the kernel
  • From: Zeeshan Ali
• Getting page usage info from /proc/slabinfo
  • From: Learner
• RE: Getting page usage info from /proc/slabinfo
  • From: Aboo Valappil
• Re: thread awareness of the scheduler
  • From: Jan Hudec
• DMA through PCI
  • From: jhoney jhoney
• Re: contributing to the kernel
  • From: Jan Hudec
• RE: reentrant ?
  • From: Naidu, Venkata
• RE: thread awareness of the scheduler
  • From: Nilanjan Roychowdhury
• Would Giving Profit You Than Receiving?
  • From: Darren Wheeler
• RE: DMA through PCI
  • From: Curran, Dominic
• Re: DMA through PCI
  • From: Om
• Re: orig_eax in user_regs_struct ?
  • From: Robert Love
• Re: orig_eax in user_regs_struct ?
  • From: aq
• scheduler question
  • From: jnf
• Re: scheduler question
  • From: Robert Love
• RE: Getting page usage info from /proc/slabinfo
  • From: Aboo Valappil
• IDEs for kernel development
  • From: Rishi Sampat
• RE: scheduler question
  • From: Aboo Valappil
• Re: IDEs for kernel development
  • From: Om
• Re: thread awareness of the scheduler
  • From: Jon Masters
• RE: scheduler question
  • From: jnf
• Re: scheduler question
  • From: Jon Masters
• Re: RE: scheduler question
  • From: Bijoy Thomas
• Re: kernel stack
  • From: suthambhara nagaraj
• RE: memory used by kernel?
  • From: Learner
• Re: copy_to/from_use query?
  • From: mohanlal jangir
• Re: copy_to/from_use query?
  • From: Mandeep Sandhu
• Re: copy_to/from_use query?
  • From: Kiran Kumar Immidi
• Re: thread awareness of the scheduler
  • From: Jan Hudec
• Re: thread awareness of the scheduler
  • From: Momchil Velikov
• Re: thread awareness of the scheduler
  • From: Jan Hudec
• kernel panic
  • From: t capacci
• Kernel space socket programming
  • From: Prasanth Jose
• RE: copy_to/from_use query?
  • From: Aboo Valappil
• PCI MAP
  • From: jhoney jhoney
• Proc filesystem
  • From: jhoney jhoney
• ATA/133 Problems with multiple cards
  • From: James Stevenson
• Re: Proc filesystem
  • From: mohanlal jangir
• Re: PCI MAP
  • From: Om
• Re: Kernel stack
  • From: Denis Vlasenko
• Re: ATA/133 Problems with multiple cards
  • From: Bartlomiej Zolnierkiewicz
• Re: ATA/133 Problems with multiple cards
  • From: Ian Pilcher
• RE: memory used by kernel?
  • From: Aboo Valappil
• Re: memory used by kernel?
  • From: Jan Hudec
• Re: kernel panic
  • From: Kiran Kumar Immidi
• Re: memory used by kernel?
  • From: Kiran Kumar Immidi
• Re: orig_eax in user_regs_struct ?
  • From: neo linux
• Re: orig_eax in user_regs_struct ?
  • From: Robert Love
• patch for /dev/mem of FC
  • From: aq
• Re: thread awareness of the scheduler
  • From: matrix reloaded
• Re: ATA/133 Problems with multiple cards
  • From: Hans-Peter Jansen
• make_modules_error
  • From: prasanna wakhare
• RE: memory used by kernel?
  • From: Learner
• lspci -v
  • From: jhoney jhoney
• List of functions
  • From: sauro
• Re: thread awareness of the scheduler
  • From: Malita, Florin
• DMA zone
  • From: jhoney jhoney
• What is kernel ring buffer
  • From: Dinesh Ahuja
• Re: What is kernel ring buffer
  • From: aq
• Blocking in tty_operations?
  • From: Frank.A.Uepping
• Re: Blocking in tty_operations?
  • From: Greg KH
• Re: What is kernel ring buffer
  • From: Dinesh Ahuja
• Re: lspci -v
  • From: Luciano A. Stertz
• disabling/masking interrupts
  • From: Perfect Stranger
• Re: disabling/masking interrupts
  • From: Robert Love
• Re: disabling/masking interrupts
  • From: Jon Masters
• Re: What is kernel ring buffer
  • From: Jon Masters
• Re: kernel panic
  • From: Jon Masters
• RE: disabling/masking interrupts
  • From: Thekkedath, Gopakumar
• RE: DMA zone
  • From: Thekkedath, Gopakumar
• Re: disabling/masking interrupts
  • From: Perfect Stranger
• serio subsystem
  • From: Zeeshan Ali
• Re: where is __setup_start?
  • From: Anupam Kapoor
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• context of pci_driver::probe
  • From: Frank.A.Uepping
• hda lost interrupt
  • From: Cristina Rivera
• Re: ATA/133 Problems with multiple cards
  • From: Bartlomiej Zolnierkiewicz
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• CEH in Egypt
  • From: EC-Council
• International - Brazil
  • From: Pedro Henrique
• Dirty Buffers
  • From: Can Sar
• Re: disabling/masking interrupts
  • From: Jon Masters
• Re: hda lost interrupt
  • From: Jon Masters
• DMA
  • From: jhoney jhoney
• Re: DMA
  • From: Tyler
• Linux Without shell
  • From: Ketan Mukadam
• do_IRQ() when ??
  • From: Prashant Batra, Noida
• Re: Linux Without shell
  • From: Nir Tzachar
• Re: Linux Without shell
  • From: Bijoy Thomas
• backing in empty or ram subject.
  • From: Ribamar Santarosa de Sousa
• Driver allocating virtual memory region
  • From: Rajeev B
• Re: context of pci_driver::probe
  • From: Greg KH
• Re: Linux Without shell
  • From: Russell Miller
• Re: contributing to the kernel
  • From: Ed L Cashin
• Re:letter of introduction.
  • From: carol
• DMA
  • From: jhoney jhoney
• PCI window
  • From: jhoney jhoney
• how to find interface uptime?
  • From: RamaRao
• Re: changes required for making modular driver -> a buitl-in one
  • From: Anupam Kapoor
• memory map of Linux
  • From: jhoney jhoney
• Please help.....
  • From: Ashish Mishra
• Re: Linux Without shell
  • From: Jan Hudec
• PCI mapping
  • From: jhoney jhoney
• PCI
  • From: jhoney jhoney
• Identifying the PIC
  • From: suresh ds
• Re: memory map of Linux
  • From: Jon Masters
• Re: Driver allocating virtual memory region
  • From: Tyler
• low energy
  • From: sauro
• Re: low energy
  • From: Kiran Kumar Immidi
• Crashme !!!
  • From: Ashish Mishra
• Re: low energy
  • From: Kiran Kumar Immidi
• Booting LILO on CF - hung at "LI"
  • From: Choong KN
• Re: Re: memory map of Linux
  • From: jhoney jhoney
• Re: Booting LILO on CF - hung at "LI"
  • From: Ravi Kumar
• Broken link on home page
  • From: Yoni Rabkin
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• Re: Broken link on home page
  • From: Manish Malik
• Re: Crashme !!!
  • From: Julien Danjou
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• Problem in getting kernel vritual address
  • From: jhoney jhoney
• Kernel virtual address for physical address
  • From: jhoney jhoney
• threads & processes.
  • From: DigitalSecure
• Re: Kernel virtual address for physical address, Problem in getting kernel vritual address
  • From: Fawad Lateef
• Re: Problem in getting kernel vritual address
  • From: Om
• Re: threads & processes.
  • From: Jim Bauer
• About swapper_pg_dir
  • From: Bao zhao
• RE: Problem in getting kernel vritual address
  • From: Thekkedath, Gopakumar
• Re: Problem in getting kernel vritual address
  • From: Om
• Re: Problem in getting kernel vritual address
  • From: Om
• Re: About swapper_pg_dir
  • From: sar.kernel
• Re: Kernel virtual address for physical address
  • From: sar.kernel
• Re: RE: Problem in getting kernel vritual address
  • From: jhoney jhoney
• RE: RE: Problem in getting kernel vritual address
  • From: Thekkedath, Gopakumar
• Re: how to find interface uptime?
  • From: Jon Masters
• Re: RE: Problem in getting kernel vritual address
  • From: Jon Masters
• Re: threads & processes.
  • From: Jon Masters
• Adding a new network protocol layer
  • From: xin
• Re: Re: memory map of Linux
  • From: Jon Masters
• Changing kernel page size
  • From: sriram krishnamoorthy
• Re: Changing kernel page size
  • From: Jon Masters
• Re: Changing kernel page size
  • From: Jon Masters
• Accessing Processor Registers
  • From: jhoney jhoney
• Re: Changing kernel page size
  • From: sriram krishnamoorthy
• communication with serial port
  • From: Zeeshan Ali
• Re: communication with serial port
  • From: Greg KH
• Re: communication with serial port
  • From: Zeeshan Ali
• Re: Changing kernel page size
  • From: Jon Masters
• Re: Accessing Processor Registers
  • From: Om
• Address of Linux kernel in RAM
  • From: jhoney jhoney
• Re: ATA/133 Problems with multiple cards
  • From: Bartlomiej Zolnierkiewicz
• Re: Address of Linux kernel in RAM
  • From: Russell Miller
• Re: Address of Linux kernel in RAM
  • From: Jon Masters
• Re: ATA/133 Problems with multiple cards
  • From: Hans-Peter Jansen
• Re: ATA/133 Problems with multiple cards
  • From: James Stevenson
• maximum number of ticks
  • From: F. A.
• sys_open
  • From: Can Sar
• Re: sys_open
  • From: Jan Hudec
• Errors while insmod a USB function driver kernel module
  • From: Narendra Kulkarni
• Re: Errors while insmod a USB function driver kernel module
  • From: mohanlal jangir
• Re: Errors while insmod a USB function driver kernel module
  • From: Narendra Kulkarni
• Re: Errors while insmod a USB function driver kernel module
  • From: mohanlal jangir
• Re: sys_open
  • From: Arjan van de Ven
• Will kernel code be swapped out?
  • From: Lei Yang
• Re: Will kernel code be swapped out?
  • From: Bijoy Thomas
• Re: Will kernel code be swapped out?
  • From: Bernd Petrovitsch
• Unable to handle kernel paging request at virtual address 00100100
  • From: Mauricio Lin
• Re: Unable to handle kernel paging request at virtual address 00100100
  • From: Jim Bauer
• Re: sys_open
  • From: Can Sar
• Re: Errors while insmod a USB function driver kernel module
  • From: Jon Masters
• Re: sys_open
  • From: Sven Schuster
• How to include driver as a part of kernel
  • From: jhoney jhoney
• Re: Changing kernel page size
  • From: suthambhara nagaraj
• Re: Changing kernel page size
  • From: Jon Masters
• Re: How to include driver as a part of kernel
  • From: Jon Masters
• udev and char devices
  • From: Athul Acharya
• How to add teh device to /dev in linux
  • From: Rakesh Jagota
• getting hardware details - pls help
  • From: suresh ds
• Re: getting hardware details - pls help
  • From: suneesh
• Re: How to add teh device to /dev in linux
  • From: Zeeshan Ali
• Re: getting hardware details - pls help
  • From: Jon Masters
• Re: getting hardware details - pls help
  • From: Jon Masters
• list.h - how to remove all the entries from the list
  • From: Mauricio Lin
• RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: RedHat Security Team
• RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: RedHat Security Team
• Re: RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: Athul Acharya
• Re: RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: Manish Malik
• Re: RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: Bijoy Thomas
• Re: RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: Jon Masters
• Re: list.h - how to remove all the entries from the list
  • From: Gabor Fekete
• Re: RedHat: Buffer Overflow in "ls" and "mkdir"
  • From: Manish Malik
• Re: Re: communication with serial port
  • From: pradeep tr
• init/main.c question
  • From: Russell Miller
• Re: Re: communication with serial port
  • From: Zeeshan Ali
• Re: init/main.c question
  • From: Greg KH
• errors while insmoding usb-skeleton.o
  • From: Narendra Kulkarni
• Re: question in ldd.
  • From: Ribamar Santarosa de Sousa
• Re: init/main.c question
  • From: Russell Miller
• Re: question in ldd.
  • From: Ribamar Santarosa de Sousa
• Re: getting hardware details - pls help
  • From: suresh ds
• Re: low energy
  • From: Stephane List
• Re: Booting LILO on CF - hung at "LI"
  • From: Stephane List
• Use Cramfs as root
  • From: 林建安
• kernel panic - not syncing: VFS
  • From: Mauricio Lin
• Re: kernel panic - not syncing: VFS
  • From: Nish Aravamudan
• Re: kernel panic - not syncing: VFS
  • From: Manu Garg
• intercepting memory access
  • From: Simone Vellei
• Re: intercepting memory access
  • From: Momchil Velikov
• Re: low energy
  • From: sauro
• Re: Errors while insmod a USB function driver kernel module
  • From: Anupam Kapoor
• Re: Errors while insmod a USB function driver kernel module
  • From: Jon Masters
• Re: intercepting memory access
  • From: Jon Masters
• EXPORT_SYMBOL and Makefile
  • From: Mauricio Lin
• Re: Errors while insmod a USB function driver kernel module
  • From: Anupam Kapoor
• set blksize of block device
  • From: Lei Yang
• loopback on block device
  • From: Lei Yang
• What is this function doing
  • From: F. A.
• Re: intercepting memory access
  • From: Momchil Velikov
• Setting block sizes beyond 4K
  • From: sai narasimhamurthy
• Re: Setting block sizes beyond 4K
  • From: sai narasimhamurthy
• Re: Setting block sizes beyond 4K
  • From: Ribamar Santarosa de Sousa
• data buffer and scatter-gather
  • From: Tommaso Moroni
• Re: data buffer and scatter-gather
  • From: Jon Masters
• Re: data buffer and scatter-gather
  • From: Tommaso Moroni
• Re: data buffer and scatter-gather
  • From: sai narasimhamurthy
• Re: Setting block sizes beyond 4K
  • From: sai narasimhamurthy
• inode to destination address
  • From: Thorsten Holz
• Re: Setting block sizes beyond 4K
  • From: sai narasimhamurthy
• Re: set blksize of block device
  • From: Lei Yang
• 未承諾広告※5000円で開業してみませんか
  • From: hayabusa
• Re: set blksize of block device
  • From: Lei Yang
• Re: set blksize of block device
  • From: Bijoy Thomas
• Re: set blksize of block device
  • From: Lei Yang
• Re: set blksize of block device
  • From: Denis Vlasenko
• RE: set blksize of block device
  • From: gopu.bhaskar
• Re: set blksize of block device
  • From: Denis Vlasenko
• Requirement for Set Top Box professionals on STMicro or other platforms
  • From: GEORGE JOSEPH
• Re: set blksize of block device
  • From: Shesha B.
• Re: set blksize of block device
  • From: Lei Yang
• Re: set blksize of block device
  • From: Lei Yang
• Re: set blksize of block device
  • From: Todd Poynor
• Upgrading problem with my /proc/pid/smaps
  • From: Mauricio Lin
• Re: Upgrading problem with my /proc/pid/smaps
  • From: Mauricio Lin
• Re: inode to destination address
  • From: suthambhara nagaraj
• How to Add socket interface to char devices
  • From: Vanitha Ramaswami
• Re: How to Add socket interface to char devices
  • From: prasanna wakhare
• Re: Upgrading problem with my /proc/pid/smaps
  • From: Mauricio Lin
• in_atomic() and DMA
  • From: Michal Ludvig
• Re: in_atomic() and DMA
  • From: Robert Love
• Re: in_atomic() and DMA
  • From: Michal Ludvig
• zlib compress buffer in kernel
  • From: Lei Yang
• RE: What is this function doing
  • From: Brandon Niemczyk
• kernel BUG at slab.c 1130
  • From: bunty
• LDT in linux?
  • From: aq