Mail Index

• Thread Index

• Re: Kernel Panic at boot
  • From: Stephen Roberts
• Re: the fb_prepare_logo(./drivers/video/fbmem.c) no longer export as symbol at 2.6.27 Kernel
  • From: Peter Teoh
• Re: the fb_prepare_logo(./drivers/video/fbmem.c) no longer export as symbol at 2.6.27 Kernel
  • From: Peter Teoh
• Re: Kernel Panic at boot
  • From: Mulyadi Santosa
• Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Manish Katiyar
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Manish Katiyar
• Re: Kernel Panic at boot
  • From: Durga Prasad
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Durga Prasad
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Sandeep K Sinha
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Manish Katiyar
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Sandeep K Sinha
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Manish Katiyar
• configuring AirLink101 Wireless PCI network adapter - AWLH3028- RHEL5.3 or 5.0
  • From: ridgetwo
• Re: configuring AirLink101 Wireless PCI network adapter - AWLH3028- RHEL5.3 or 5.0
  • From: microbit
• Re: Kernel Panic at boot
  • From: Stephen Roberts
• unity mapping in kernel area?
  • From: NAHieu
• Re: unity mapping in kernel area?
  • From: NAHieu
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Sandeep K Sinha
• Re: Kernel Panic at boot
  • From: Durga Prasad
• Re: Checking of NULL with __GFP_NOFAIL in kzalloc()
  • From: Manish Katiyar
• Re: the fb_prepare_logo(./drivers/video/fbmem.c) no longer export as symbol at 2.6.27 Kernel
  • From: Peter Chen
• sock_create vs socket_create_kern
  • From: Daniel Baluta
• hot to distinquish between 2 USB devices with same vendor and product id
  • From: Belisko Marek
• Re: unity mapping in kernel area?
  • From: Mulyadi Santosa
• Re: sock_create vs socket_create_kern
  • From: Alan Menegotto
• Re: sock_create vs socket_create_kern
  • From: Michael Blizek
• Re: sock_create vs socket_create_kern
  • From: Daniel Baluta
• Re: Where is obj parameters comes from?
  • From: Pei Lin
• Re: Where is obj parameters comes from?
  • From: Pei Lin
• Re: Kernel Panic at boot
  • From: Stephen Roberts
• Re: unity mapping in kernel area?
  • From: Peter Teoh
• Re: unity mapping in kernel area?
  • From: NAHieu
• creative modem in lenny
  • From: Joe Neel
• Re: unity mapping in kernel area?
  • From: Peter Teoh
• Re: unity mapping in kernel area?
  • From: NAHieu
• Re: unity mapping in kernel area?
  • From: Pei Lin
• Re: hot to distinquish between 2 USB devices with same vendor and product id
  • From: Greg KH
• Re: unity mapping in kernel area?
  • From: NAHieu
• Re: unity mapping in kernel area?
  • From: Peter Teoh
• Re: unity mapping in kernel area?
  • From: Peter Teoh
• Re: creative modem in lenny
  • From: Daniel Baluta
• What is the difference between loopback device and ramdisk device
  • From: loody
• 'hlist' structures
  • From: Chetan Nanda
• Re: hot to distinquish between 2 USB devices with same vendor and product id
  • From: Belisko Marek
• Re: hot to distinquish between 2 USB devices with same vendor and product id
  • From: Greg KH
• Porting 32bit IOCTL on 64bit Architecture
  • From: tejas khatiwala
• Re: unity mapping in kernel area?
  • From: NAHieu
• Re: Kernel Panic at boot
  • From: Stephen Roberts
• Hang at memory address while booting
  • From: Tina S.
• Linux rb-tree doubt: two entries with same key values
  • From: Sukanto Ghosh
• Re: hot to distinquish between 2 USB devices with same vendor and product id
  • From: Belisko Marek
• Re: Deciphering Call Trace details
  • From: yogeshwar sonawane
• Re: Kernel Panic at boot
  • From: Stephen Roberts
• Re: Deciphering Call Trace details
  • From: Manish Katiyar
• Re: What is the difference between loopback device and ramdisk device
  • From: Peter Teoh
• Linux option for network
  • From: Bizhan Gholikhamseh (bgholikh)
• Re: Linux option for network
  • From: Bob Beers
• Re: Deciphering Call Trace details
  • From: Durga Prasad
• Wait for two clock ticks
  • From: Asim
• How to DMA on PCI devices
  • From: Fernand LONE SANG
• Re: What is the difference between loopback device and ramdisk device
  • From: Minchan Kim
• About Kernel preemption and kernel mode stack
  • From: sahlot arvind
• Re: About Kernel preemption and kernel mode stack
  • From: Michael Blizek
• Re: Wait for two clock ticks
  • From: Mulyadi Santosa
• Re: Wait for two clock ticks
  • From: Sandeep K Sinha
• Question about C Programming.
  • From: Ravi Sankar
• Re: Question about C Programming.
  • From: Manish Katiyar
• Re: Question about C Programming.
  • From: Anuz Pratap Singh Tomar
• Re: About Kernel preemption and kernel mode stack
  • From: Pranav Peshwe
• on crypto
  • From: chaitanya
• Re: Question about C Programming.
  • From: Sandeep K Sinha
• Re: Question about C Programming.
  • From: Srdjan Todorovic
• Char device driver. Illegal seek.
  • From: Denis Borisevich
• Re: How to DMA on PCI devices
  • From: Peter Teoh
• Re: Question about C Programming.
  • From: mukti jain
• Re: How to DMA on PCI devices
  • From: Fernand LONE SANG
• Re: Char device driver. Illegal seek.
  • From: microbit
• Re: Question about C Programming.
  • From: Bernd Petrovitsch
• need help in understanding basics of block device driver
  • From: nidhi mittal
• Re: Question about C Programming.
  • From: Ravi Sankar
• Re: Char device driver. Illegal seek.
  • From: microbit
• Re: need help in understanding basics of block device driver
  • From: Rohit Sharma
• Challenges Faced by an Amateur Linux Programmer
  • From: Mohit Varma
• Re: About Kernel preemption and kernel mode stack
  • From: Michael Blizek
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: Frederic Weisbecker
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: Greg Freemyer
• Re: About Kernel preemption and kernel mode stack
  • From: sahlot arvind
• Re: Wait for two clock ticks
  • From: Asim
• Re: About Kernel preemption and kernel mode stack
  • From: microbit
• Re: Wait for two clock ticks
  • From: microbit
• Re: About Kernel preemption and kernel mode stack
  • From: Shinu
• Re: About Kernel preemption and kernel mode stack
  • From: Michael Blizek
• Re: About Kernel preemption and kernel mode stack
  • From: Michael Blizek
• Re: Char device driver. Illegal seek.
  • From: Peter Teoh
• page address from user buffer
  • From: Vishal Thanki
• Re: need help in understanding basics of block device driver
  • From: nidhi mittal
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: nidhi mittal
• jprobes for 'enqueue_entity' and 'dequeue_entity' causes kernel hang on spinlock
  • From: Sukanto Ghosh
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: ArunKumar Nagarajan
• Re: jprobes for 'enqueue_entity' and 'dequeue_entity' causes kernel hang on spinlock
  • From: Mulyadi Santosa
• Re: Wait for two clock ticks
  • From: Henrik Austad
• Re: Wait for two clock ticks
  • From: Asim
• Re: Wait for two clock ticks
  • From: Greg Freemyer
• Re: need help in understanding basics of block device driver
  • From: Rohit Sharma
• Re: Wait for two clock ticks
  • From: Raz
• question on tun/tap and network-stack
  • From: matthias
• Re: Wait for two clock ticks
  • From: Asim
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: Greg KH
• Re: Wait for two clock ticks
  • From: Raz
• Re: question on tun/tap and network-stack
  • From: matthias
• File System Project
  • From: Shyam Burkule
• Re: File System Project
  • From: Greg Freemyer
• Re: File System Project
  • From: Shyam Burkule
• Re: File System Project
  • From: sahlot arvind
• Re: File System Project
  • From: sahlot arvind
• Re: Wait for two clock ticks
  • From: Greg Freemyer
• Re: File System Project
  • From: Greg Freemyer
• Re: page address from user buffer
  • From: Chauhan
• Re: File System Project
  • From: Manish Katiyar
• Re: File System Project
  • From: Greg KH
• Re: Wait for two clock ticks
  • From: Greg KH
• Re: on crypto
  • From: Pei Lin
• Re: on crypto
  • From: Pei Lin
• Re: File System Project
  • From: Sandeep K Sinha
• Lost fedora Installation
  • From: Rishi Bhushan Agrawal
• HIGHMEM4G & PAE possible?
  • From: NAHieu
• Re: HIGHMEM4G & PAE possible?
  • From: Mulyadi Santosa
• Re: need help in understanding basics of block device driver
  • From: Rohit Sharma
• Re: Lost fedora Installation
  • From: Manish Katiyar
• Re: Lost fedora Installation
  • From: Matthias Kaehlcke
• Re: Question about C Programming.
  • From: Stephen Roberts
• RE: reverse-engineering a usb device
  • From: Microbit_P43000
• Re: HIGHMEM4G & PAE possible?
  • From: Rik van Riel
• Re: File System Project
  • From: "Stanisław T. Findeisen"
• Solar flares effect in Fedora Core 10
  • From: Peter Teoh
• RE: About Kernel preemption and kernel mode stack
  • From: Microbit_P43000
• Re: File System Project
  • From: Manish Katiyar
• Re: File System Project
  • From: Peter Teoh
• Re: What is the difference between loopback device and ramdisk device
  • From: loody
• array declaration inside init function causing kernel panic
  • From: yogeshwar sonawane
• Re: array declaration inside init function causing kernel panic
  • From: Daniel Baluta
• Re: array declaration inside init function causing kernel panic
  • From: yogeshwar sonawane
• Re: array declaration inside init function causing kernel panic
  • From: Denis Kirjanov
• Re: array declaration inside init function causing kernel panic
  • From: Daniel Baluta
• Re: Lost fedora Installation
  • From: Rishi Bhushan Agrawal
• Question about return value of do_mount_root
  • From: loody
• "make TAGS" according to ".config" file
  • From: Pawel K
• Re: Wait for two clock ticks
  • From: Asim
• Re: Wait for two clock ticks
  • From: Raz
• Re: Solar flares effect in Fedora Core 10
  • From: Stuart Jansen
• Re: Wait for two clock ticks
  • From: Greg KH
• how large is a atomic_t
  • From: Mike Christie
• Re: HIGHMEM4G & PAE possible?
  • From: NAHieu
• any NX memory areas?
  • From: NAHieu
• Re: array declaration inside init function causing kernel panic
  • From: yogeshwar sonawane
• RE: array declaration inside init function causing kernel panic
  • From: Microbit_P43000
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: nidhi mittal
• Re: array declaration inside init function causing kernel panic
  • From: Durga Prasad
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: Challenges Faced by an Amateur Linux Programmer
  • From: Greg KH
• Re: how large is a atomic_t
  • From: Mulyadi Santosa
• What is mem_cgroup?
  • From: Chauhan
• SOC Board development
  • From: Ole Loots
• BUG_ON with sizeof and bit operations
  • From: Stoyan Gaydarov
• Re: SOC Board development
  • From: Thomas Rega
• Re: BUG_ON with sizeof and bit operations
  • From: Nelson Castillo
• Re: SOC Board development
  • From: Ole Loots
• RE: What is mem_cgroup?
  • From: Microbit_P43000
• RE: BUG_ON with sizeof and bit operations
  • From: Microbit_P43000
• Re: What is mem_cgroup?
  • From: Li Zefan
• Re: any NX memory areas?
  • From: NAHieu
• load/store uops
  • From: Shinu
• Include path for module compilation
  • From: Harsha
• Re: Include path for module compilation
  • From: Harsha
• RE: load/store uops
  • From: Microbit_P43000
• Re: Include path for module compilation
  • From: Vishal Thanki
• Re: Include path for module compilation
  • From: Vishal Thanki
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: inode block address
  • From: Manish Katiyar
• Re: load/store uops
  • From: Shinu
• Re: inode block address
  • From: Sandeep K Sinha
• Re: inode block address
  • From: Peter Teoh
• Re: any NX memory areas?
  • From: NAHieu
• Re: any NX memory areas?
  • From: NAHieu
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: any NX memory areas?
  • From: Pei Lin
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: any NX memory areas?
  • From: Peter Teoh
• Re: any NX memory areas?
  • From: NAHieu
• Re: any NX memory areas?
  • From: NAHieu
• Re: Include path for module compilation
  • From: Harsha
• Creating /proc/net/dev
  • From: Bizhan Gholikhamseh (bgholikh)
• Re: hot to distinquish between 2 USB devices with same vendor and product id
  • From: Brandon Philips
• Re: Creating /proc/net/dev
  • From: ArunKumar Nagarajan
• structure definition in a .c file rather than .h file
  • From: Sukanto Ghosh
• Re: structure definition in a .c file rather than .h file
  • From: Nelson Castillo
• Re: structure definition in a .c file rather than .h file
  • From: Pei Lin
• Re: structure definition in a .c file rather than .h file
  • From: Sukanto Ghosh
• asynchronous handling of request in block device driver
  • From: nidhi mittal
• Drivers need for usb file system
  • From: vichy
• Re: Drivers need for usb file system
  • From: Greg KH
• [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Manish Katiyar
• Re: Drivers need for usb file system
  • From: Alan Stern
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: Creating /proc/net/dev
  • From: Irimia Bogdan
• Re: structure definition in a .c file rather than .h file
  • From: Durga Prasad
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• request structure --
  • From: nidhi mittal
• School Project
  • From: matt mooney
• elf working
  • From: krushnaal pai
• Re: elf working
  • From: Adam Jiang
• Re: structure definition in a .c file rather than .h file
  • From: Sukanto Ghosh
• Re: structure definition in a .c file rather than .h file
  • From: Pei Lin
• Re: structure definition in a .c file rather than .h file
  • From: Sukanto Ghosh
• RE: elf working
  • From: Vivek Kumar Gupta
• request structure related confusions--
  • From: nidhi mittal
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Vineet Agarwal
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Manish Katiyar
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• how to change the cpu time limit of a running process
  • From: Santosh Pradhan
• Testing the networking / storage stuff !
  • From: Onkar
• Re: Testing the networking / storage stuff !
  • From: Michael Blizek
• filesystem info
  • From: krushnaal pai
• linux switch_to function
  • From: Gaurav Tewari
• Re: filesystem info
  • From: arshad hussain
• where is macro SetPageDirty located
  • From: Belisko Marek
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Vineet Agarwal
• Re: where is macro SetPageDirty located
  • From: Shyam Burkule
• Re: where is macro SetPageDirty located
  • From: Belisko Marek
• Re: where is macro SetPageDirty located
  • From: Daniel Baluta
• Re: where is macro SetPageDirty located
  • From: Daniel Baluta
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Vineet Agarwal
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Manish Katiyar
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Vineet Agarwal
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: any NX memory areas?
  • From: lech
• Re: any NX memory areas?
  • From: lech
• Converting logical address to physical address
  • From: Pravin
• linux switch_to
  • From: Gaurav Tewari
• timeout of 10 usecs
  • From: Denis Borisevich
• Re: timeout of 10 usecs
  • From: Razvan Deaconescu
• Re: Converting logical address to physical address
  • From: Mulyadi Santosa
• Re: any NX memory areas?
  • From: Mulyadi Santosa
• Re: elf working
  • From: Mulyadi Santosa
• Re: linux switch_to function
  • From: Mulyadi Santosa
• Re: linux switch_to function
  • From: Manish Katiyar
• Re: filesystem info
  • From: Wahengbam
• Re: filesystem info
  • From: Manish Katiyar
• Re: linux switch_to function
  • From: Mulyadi Santosa
• Re: filesystem info
  • From: Matthias Kaehlcke
• Re: timeout of 10 usecs
  • From: Denis Borisevich
• Re: timeout of 10 usecs
  • From: Matthias Kaehlcke
• Re: timeout of 10 usecs
  • From: Denis Borisevich
• Re: filesystem info
  • From: Leandro Dorileo
• Re: timeout of 10 usecs
  • From: Raz
• how much updating of "scripts/" directory from 2.6.21 to now?
  • From: Robert P. J. Day
• Re: how much updating of "scripts/" directory from 2.6.21 to now?
  • From: Robert P. J. Day
• How to convert a port number (_be16) to a string
  • From: Cliffe
• Re: How to convert a port number (_be16) to a string
  • From: Matthias Kaehlcke
• Fwd: Re: any NX memory areas?
  • From: lech
• Re: linux switch_to function
  • From: Peter Teoh
• How to get node property in the /sys device model
  • From: Ahmed A
• Re: How to convert a port number (_be16) to a string
  • From: Cliffe
• TCP kernel server
  • From: Mark Ryden
• Re: TCP kernel server
  • From: Razvan Deaconescu
• Re: How to convert a port number (_be16) to a string
  • From: Shaz
• Zero-copy for large amounts of streaming data
  • From: Priya Suryanarayanan
• hrtimers API and description
  • From: Denis Borisevich
• The Linux Staging tree, what it is and is not.
  • From: Greg KH
• Re: Zero-copy for large amounts of streaming data
  • From: Shawn Bohrer
• Re: The Linux Staging tree, what it is and is not.
  • From: Greg KH
• Re: The Linux Staging tree, what it is and is not.
  • From: Mariusz Kozlowski
• Re: The Linux Staging tree, what it is and is not.
  • From: Mariusz Kozlowski
• Re: Zero-copy for large amounts of streaming data
  • From: Shawn Bohrer
• Info about a node in the /sys device file system
  • From: Ahmed A
• Re: Info about a node in the /sys device file system
  • From: Greg KH
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• RE: Zero-copy for large amounts of streaming data
  • From: Priya Suryanarayanan
• Vlan Driver 8021q
  • From: Mohammed Mustaq
• Re: request structure --
  • From: Yogesh Sobale
• kernel timer problem
  • From: Saransh Mittal
• Re: kernel timer problem
  • From: rahul p
• Re: kernel timer problem
  • From: Nelson Castillo
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• Re: kernel timer problem
  • From: Chetan Nanda
• Re: kernel timer problem
  • From: Durga Prasad
• Ftrace
  • From: Paolo
• Re: Zero-copy for large amounts of streaming data
  • From: Shawn Bohrer
• Re: Ftrace
  • From: Frederic Weisbecker
• Re: Ftrace
  • From: microbit
• __GFP_RECLAIMABLE in case of GFP_DMA, GFP_KERNEL etc.
  • From: Jagadeesh Bhaskar P
• Re: __GFP_RECLAIMABLE in case of GFP_DMA, GFP_KERNEL etc.
  • From: Mulyadi Santosa
• "physmap flash device: 200000 at 60000000" do i need that?
  • From: Robert P. J. Day
• semaphore ownership
  • From: Shyam Burkule
• Re: semaphore ownership
  • From: Daniel Baluta
• Re: semaphore ownership
  • From: Matthias Kaehlcke
• Re: semaphore ownership
  • From: Durga Prasad
• Re: semaphore ownership
  • From: Shyam Burkule
• Kernel Audinting and debugfs
  • From: Shaz
• Re: Kernel Audinting and debugfs
  • From: Greg KH
• "no initial console" error on ARM embedded system
  • From: Robert P. J. Day
• Understanding the Linux Kernel book?
  • From: Joe Ryan
• Re: semaphore ownership
  • From: Manish Katiyar
• combining two usb devices into one?
  • From: Alex Tsui
• Re: combining two usb devices into one?
  • From: Sandeep K Sinha
• Re: Understanding the Linux Kernel book?
  • From: Henrik Austad
• Re: Understanding the Linux Kernel book?
  • From: rahul p
• Re: Understanding the Linux Kernel book?
  • From: Henrik Austad
• CONFIG_* symbols status
  • From: Pawel K
• Re: CONFIG_* symbols status
  • From: Manish Katiyar
• Re: "no initial console" error on ARM embedded system
  • From: Belisko Marek
• Will code kernel for food ;-)
  • From: Frank Seidel
• Re: Will code kernel for food ;-)
  • From: Gabor Kuti
• Re: "no initial console" error on ARM embedded system
  • From: Robert P. J. Day
• Re: Will code kernel for food ;-)
  • From: Paul Charles Leddy
• Re: Will code kernel for food ;-)
  • From: Georgy Berdyshev
• Re: Will code kernel for food ;-)
  • From: Shentino
• Re: TCP kernel server
  • From: Raz
• Query: Real time process
  • From: Chetan Nanda
• Re: Query: Real time process
  • From: Sandeep K Sinha
• Re: Query: Real time process
  • From: Chetan Nanda
• Re: Query: Real time process
  • From: Sandeep K Sinha
• CONFIG_SMP for single-core CPU
  • From: Peter Chen
• Re: Query: Real time process
  • From: Denis Borisevich
• Two questions about scheduler
  • From: Peter Chen
• Re: CONFIG_SMP for single-core CPU
  • From: Mircea Gherzan
• Re: Two questions about scheduler
  • From: Henrik Austad
• Re: Query: Real time process
  • From: Henrik Austad
• Re: CONFIG_SMP for single-core CPU
  • From: Peter Chen
• Re: Two questions about scheduler
  • From: Peter Chen
• Re: Two questions about scheduler
  • From: Henrik Austad
• Testing Networking code !
  • From: Onkar
• Re: semaphore ownership
  • From: pradeep singh
• Re: Testing Networking code !
  • From: pradeep singh
• Questions about FSG, pls help me(platform:s3c2440 and linux2.6.26)
  • From: snoppy1314
• Re: Questions about FSG, pls help me(platform:s3c2440 and linux2.6.26)
  • From: Kalpesh Rathod
• Re: question about SCSI commands
  • From: loody
• Re: question about SCSI commands
  • From: Sandeep K Sinha
• Re: Re: Questions about FSG, pls help me(platform:s3c2440 andlinux2.6.26)
  • From: snoppy1314
• Netlink sockets
  • From: luca ellero
• Re: Netlink sockets
  • From: Mauricio Mauad Menegaz Filho
• Re: question about SCSI commands
  • From: Mark Brown
• some questions about porting pcmcia driver?
  • From: loody
• printk not printing to kernel log
  • From: Sukanto Ghosh
• Re: printk not printing to kernel log
  • From: Henrik Austad
• filesystem project idea
  • From: Onkar
• Re: filesystem project idea
  • From: Manish Katiyar
• Re: filesystem project idea
  • From: Sandeep K Sinha
• Re: Cannot open from user space a misc device - why ?
  • From: Jeffrey Cao
• Re: Netlink sockets
  • From: luca ellero
• Re: kernel timer problem
  • From: Jeffrey Cao
• doubts about I2C driver.....
  • From: Akshay Pujari
• Fwd: doubts about I2C driver.....
  • From: Akshay Pujari
• A Seguranca no Internet Banking CAIXA.
  • From: Caixa Economica Federal .
• Sending Signal to a user thread from kernel
  • From: Devesh Sharma
• Re: Sending Signal to a user thread from kernel
  • From: Rizvan
• question about mapping RAM into user space.
  • From: yihect
• Re: question about mapping RAM into user space.
  • From: yihect
• understanding the linux code
  • From: krushnaal pai
• Re: understanding the linux code
  • From: debian developer
• Re: question about mapping RAM into user space.
  • From: Peter Chen
• Re: Sending Signal to a user thread from kernel
  • From: Devesh Sharma
• Re: understanding the linux code
  • From: Leandro Dorileo
• vfree with remaps current?
  • From: Andrew Malton
• device driver debugging
  • From: nidhi mittal
• Re: device driver debugging
  • From: Sandeep K Sinha
• Re: device driver debugging
  • From: Denis Borisevich
• Re: device driver debugging
  • From: nidhi mittal
• Re: device driver debugging
  • From: Srdjan Todorovic
• Re: device driver debugging
  • From: Vishal Thanki
• Re: device driver debugging
  • From: Anuz Pratap Singh Tomar
• Re: device driver debugging
  • From: Rishi Bhushan Agrawal
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• module compile error -- but suprising
  • From: nidhi mittal
• Re: module compile error -- but suprising
  • From: Sandeep K Sinha
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Sandeep K Sinha
• multiboot
  • From: Onkar
• Re: [ext2/ext3] Re-allocation of blocks for an inode
  • From: Greg Freemyer
• Why no trylock for read/write_bh?
  • From: Kristian Evensen
• /proc/stat iowait?, io_schedule()
  • From: David Neiss
• Projects on Linux core networking
  • From: Onkar
• can anyone tell me the differences between "struct sock" and "struct socket" that are data structures of network protocol stack ?
  • From: Irfan Ahmed
• Re: can anyone tell me the differences between "struct sock" and "struct socket" that are data structures of network protocol stack ?
  • From: Vishal Thanki
• Re: /proc/stat iowait?, io_schedule()
  • From: Mulyadi Santosa
• Re: understanding the linux code
  • From: Mulyadi Santosa
• timer function
  • From: nidhi mittal
• Re: module compile error -- but suprising
  • From: nidhi mittal
• Re: module compile error -- but suprising
  • From: Erik Mouw
• Re: module compile error -- but suprising
  • From: nidhi mittal
• Re: module compile error -- but suprising
  • From: nidhi mittal
• Re: timer function
  • From: Henrik Austad
• Re: module compile error -- but suprising
  • From: Sandeep K Sinha
• Re: module compile error -- but suprising
  • From: Sandeep K Sinha
• The biggest continual physical memory we can get during the kernel running?
  • From: Peter Chen
• Re: The biggest continual physical memory we can get during the kernel running?
  • From: microbit
• Re: multiboot
  • From: Pei Lin
• Re: The biggest continual physical memory we can get during the kernel running?
  • From: Peter Teoh
• Re: device driver debugging
  • From: Vishal Thanki
• Re: /proc/stat iowait?, io_schedule()
  • From: David Neiss
• Video Subsystem
  • From: m
• Re: Why no trylock for read/write_bh?
  • From: Peter Teoh
• Re: The biggest continual physical memory we can get during the kernel running?
  • From: Peter Chen
• Re: /proc/stat iowait?, io_schedule()
  • From: Mulyadi Santosa
• Re: The biggest continual physical memory we can get during the kernel running?
  • From: Peter Teoh
• D_LOOKUP in REAL_LOOKUP?
  • From: krushnaal pai
• Re: Video Subsystem
  • From: Peter Teoh
• Re: D_LOOKUP in REAL_LOOKUP?
  • From: Sandeep K Sinha
• Choosing Driver Model
  • From: Ole Loots
• Re: Why no trylock for read/write_bh?
  • From: kristrev
• asynchronous request procesisng in ram based block dev driver
  • From: nidhi mittal
• Re: Why no trylock for read/write_bh?
  • From: Peter Teoh
• Re: Why no trylock for read/write_bh?
  • From: Peter Teoh
• Re: module compile error -- but suprising
  • From: Erik Mouw
• d_lookup in real-lookup?
  • From: krushnaal pai
• d_lookup in real-lookup?
  • From: krushnaal pai
• d_lookup in real_lookup
  • From: krushnaal pai
• Re: question about SCSI commands
  • From: loody
• Re: Video Subsystem
  • From: m
• Re: understanding the linux code
  • From: Rakesh Radhakrishnan
• Re: understanding the linux code
  • From: Bob Beers