comp.os.linux.development.system

• Thread Index

---

• Re: Data sharing in POSIX thread?
  • From: David Schwartz
• fdisk and mkfs tools
  • From: Bilgehan . Balban
• Re: Data sharing in POSIX thread?
  • From: Jack
• Re: how to get physical memory address from virtual memory address
  • From: David Schwartz
• Re: how to get physical memory address from virtual memory address
  • From: Josef Moellers
• how to get physical memory address from virtual memory address
  • From: Hari
• how to get physical memory address from virtual memory address
  • From: Hari
• Re: source for math functions?
  • From: mast2as@xxxxxxxxx
• Re: kernel threads
  • From: Max Y
• source for math functions?
  • From: mast2as@xxxxxxxxx
• Re: kernel threads
  • From: gil_hamilton@xxxxxxxxxxx
• kernel threads
  • From: dayakarbabu
• Re: block size more than 4096 in ext2/3
  • From: dbansal
• block size more than 4096 in ext2/3
  • From: nag
• Re: Data sharing in POSIX thread?
  • From: David Schwartz
• Re: POSIX thread question
  • From: David Schwartz
• Data sharing in POSIX thread?
  • From: Jack
• Re: accessing files, devices, in kernel modules
  • From: Yellow
• Re: accessing files, devices, in kernel modules
  • From: Joe Beanfish
• Re: POSIX thread question
  • From: Mikko Rauhala
• Re: POSIX thread question
  • From: Jack
• Max Thread per process.
  • From: Amit Yadav
• Re: accessing files, devices, in kernel modules
  • From: Yellow
• Re: POSIX thread question
  • From: David Schwartz
• Re: POSIX thread question
  • From: David Schwartz
• Re: POSIX thread question
  • From: Jack
• Re: POSIX thread question
  • From: Michael Rasmussen
• Re: POSIX thread question
  • From: Mikko Rauhala
• POSIX thread question
  • From: Jack
• how to trap FPU
  • From: Scott J. McCaughrin
• Re: request_irq() changes from red hat to suse
  • From: Dave Carroll
• Re: accessing files, devices, in kernel modules
  • From: ask
• Re: accessing files, devices, in kernel modules
  • From: Yellow
• Re: accessing files, devices, in kernel modules
  • From: Yellow
• Re: How to trace functions in a driver??
  • From: hide1713@xxxxxxxxx
• Re: accessing files, devices, in kernel modules
  • From: miline
• Re: startup question
  • From: Josef Moellers
• Re: Empty linux/config.h
  • From: miline
• Re: Empty linux/config.h
  • From: miline
• Re: What's different between pending and blocking in signal concept?
  • From: Josef Moellers
• Re: How to trace functions in a driver??
  • From: miline
• Not able to mlock
  • From: Hari
• How to trace functions in a driver??
  • From: hide1713@xxxxxxxxx
• ERROR IN CHARACTER DRIVER PROGRAM
  • From: palli
• Empty linux/config.h
  • From: joseluismarchetti
• startup question
  • From: Eric
• Re: Overriding System Calls
  • From: David Schwartz
• Re: accessing files, devices, in kernel modules
  • From: samiruor
• Re: accessing files, devices, in kernel modules
  • From: gil_hamilton@xxxxxxxxxxx
• Re: PCI Driver - Read/Write to Base Address
  • From: gil_hamilton@xxxxxxxxxxx
• Re: PCI Driver - Read/Write to Base Address
  • From: elliotng . ee
• accessing files, devices, in kernel modules
  • From: Yellow
• What's different between pending and blocking in signal concept?
  • From: hurryon
• Re: Overriding System Calls
  • From: gil_hamilton@xxxxxxxxxxx
• Re: insight for multiple users
  • From: Ulrich Eckhardt
• Re: Where can i download linux sources?
  • From: Ulrich Eckhardt
• Re: Overriding System Calls
  • From: Prafulla T
• Where can i download linux sources?
  • From: John E
• Re: Overriding System Calls
  • From: gil_hamilton@xxxxxxxxxxx
• Overriding System Calls
  • From: Prafulla T
• insight for multiple users
  • From: barros . jos
• Re: inter_module_* routines deprecated in 2.6.16 kernel
  • From: David Schwartz
• Re: socket communication and DNS
  • From: giangiammy
• Re: PCI Driver - Read/Write to Base Address
  • From: David Schwartz
• Re: socket communication and DNS
  • From: David Schwartz
• Re: PCI Driver - Read/Write to Base Address
  • From: elliotng . ee
• Re: PCI Driver - Read/Write to Base Address
  • From: elliotng . ee
• Re: PCI Driver - Read/Write to Base Address
  • From: gil_hamilton@xxxxxxxxxxx
• booting 2.6.13 kernel on ixp425 machine
  • From: pc
• socket communication and DNS
  • From: giangiammy
• PCI Driver - Read/Write to Base Address
  • From: elliotng . ee
• PCI IRQ number reported by scanpci and lspci are different.
  • From: samiruor
• Re: Simple Hello World error
  • From: miline
• Re: What is the best tool for traceing the driver??
  • From: miline
• inter_module_* routines deprecated in 2.6.16 kernel
  • From: Martin Feeney
• help!!a question to trouble me a lot in reading the driver code
  • From: nick811125
• Re: Adding a new interrupt handler to the IDT
  • From: Tauno Voipio
• Re: Adding a new interrupt handler to the IDT
  • From: Martin Feeney
• Re: Adding a new interrupt handler to the IDT
  • From: Martin Feeney
• Re: Adding a new interrupt handler to the IDT
  • From: Tauno Voipio
• Adding a new interrupt handler to the IDT
  • From: Martin Feeney
• HELP!Error :NO child processes in LTTV (linux trace toolkit viewer)
  • From: hide1713@xxxxxxxxx
• Re: semaphore question
  • From: 42Bastian Schick
• Re: semaphore question
  • From: 42Bastian Schick
• Re: I2C support - 'built-in' VS modules
  • From: Bill Marcum
• Re: About serial communication
  • From: Floyd L. Davidson
• Re: About serial communication
  • From: Josef Moellers
• What is the best tool for traceing the driver??
  • From: hide1713@xxxxxxxxx
• Re: unwanted double reads in /proc routines
  • From: Bernhard Holzmayer
• About serial communication
  • From: Dharmendra
• Simple Hello World error
  • From: elliotng . ee
• I2C support - 'built-in' VS modules
  • From: drasko
• Re: Inject a shared library or DLL into a running process in Linux
  • From: David Schwartz
• Re: unwanted double reads in /proc routines
  • From: Slaytanic
• Re: unwanted double reads in /proc routines
  • From: Tauno Voipio
• Re: semaphore question
  • From: Jack
• Re: Inject a shared library or DLL into a running process in Linux
  • From: Bernd Strieder
• unwanted double reads in /proc routines
  • From: Bernhard Holzmayer
• Re: Inject a shared library or DLL into a running process in Linux
  • From: Robert Redelmeier
• Re: Inject a shared library or DLL into a running process in Linux
  • From: manu
• Re: semaphore question
  • From: Josef Moellers
• Re: semaphore question
  • From: David Schwartz
• Re: semaphore question
  • From: Josef Moellers
• Re: semaphore question
  • From: David Schwartz
• Re: Inject code where in device driver for checking on receive packets?
  • From: Azeem
• Re: semaphore question
  • From: Josef Moellers
• CONFIG_NET_FASTROUTE
  • From: Roman Mashak
• setting permission of usb device file in driver
  • From: Yue Zhou
• Re: Inject a shared library or DLL into a running process in Linux
  • From: David Schwartz
• Re: semaphore question
  • From: Jack
• Re: Inject code where in device driver for checking on receive packets?
  • From: Slaytanic
• Re: Inject a shared library or DLL into a running process in Linux
  • From: manu
• Inject code where in device driver for checking on receive packets?
  • From: Azeem
• Re: semaphore question
  • From: Josef Moellers
• Re: HowTo check whether PAE is enabled on IA32?
  • From: Josef Moellers
• Re: Inject a shared library or DLL into a running process in Linux
  • From: Paul Pluzhnikov
• Re: Inject a shared library or DLL into a running process in Linux
  • From: Chris McDonald
• Re: Inject a shared library or DLL into a running process in Linux
  • From: John Reiser
• Inject a shared library or DLL into a running process in Linux
  • From: manu
• Re: semaphore question
  • From: 42Bastian Schick
• Re: HowTo check whether PAE is enabled on IA32?
  • From: David W Noon
• semaphore question
  • From: Jack
• how to implement ext2/ext3 filesytem in linux
  • From: nag
• Re: HowTo check whether PAE is enabled on IA32?
  • From: Josef Moellers
• Re: modify the Virtual Address space of a process
  • From: John Reiser
• modify the Virtual Address space of a process
  • From: manu
• Re: kmalloc size limitation in kernel module init
  • From: Slaytanic
• Re: how to use jiffies in printk
  • From: Azeem
• Re: Calling dlsym()-ed function causes segfault
  • From: Paul Pluzhnikov
• Re: HowTo check whether PAE is enabled on IA32?
  • From: David W Noon
• kmalloc size limitation in kernel module init
  • From: Christoph Dwertmann
• Calling dlsym()-ed function causes segfault
  • From: nirnimesh
• LILO version 22.7.3 released
  • From: JohnInSD At san DOT rr dot COM
• Re: how to use jiffies in printk
  • From: Slaytanic
• how to use jiffies in printk
  • From: Azeem
• Stopping a kernel thread [hang-up problem]
  • From: Slaytanic
• Re: random numbers
  • From: Josef Moellers
• random numbers
  • From: Roman Mashak
• Re: HowTo check whether PAE is enabled on IA32?
  • From: David Lee
• Re: HowTo check whether PAE is enabled on IA32?
  • From: David W Noon
• Re: gcc optimization changes results
  • From: David Schwartz
• Re: gcc optimization changes results
  • From: David Schwartz
• Re: schedule_timeout() doubt [possible infinite sleep?]
  • From: Slaytanic
• Re: gcc optimization changes results
  • From: Perianayagam Somasundaram
• MMC driver in linux 2.6.7
  • From: nate_jenny
• Re: HowTo check whether PAE is enabled on IA32?
  • From: David Lee
• platform_device question
  • From: drasko
• bc635vme timesys/linux device driver; need direction please
  • From: cstahl3
• Re: HowTo check whether PAE is enabled on IA32?
  • From: Markus Grabner
• Re: schedule_timeout() doubt [possible infinite sleep?]
  • From: gil_hamilton@xxxxxxxxxxx
• Re: Fast USB Transfers
  • From: Uwe Bonnes
• Re: gcc optimization changes results
  • From: Robert Komar
• Re: Fast USB Transfers
  • From: Tim Roberts
• Re: Load balancing using SCHED_RR
  • From: David Schwartz
• Re: gcc optimization changes results
  • From: nirnimesh
• HowTo check whether PAE is enabled on IA32?
  • From: David Lee
• Creating new Drivers for CUPS
  • From: kcool
• ixp400 npe driver
  • From: pc
• Re: user-space hangs - followup
  • From: Dan Miller
• Re: gcc optimization changes results
  • From: Perianayagam Somasundaram
• Re: gcc optimization changes results
  • From: Joe Beanfish
• schedule_timeout() doubt [possible infinite sleep?]
  • From: Slaytanic
• Re: accessing internal h/w timers
  • From: Bob Hauck
• Re: user-space hangs - followup
  • From: gil_hamilton@xxxxxxxxxxx
• Re: accessing internal h/w timers
  • From: techietone
• Re: gcc optimization changes results
  • From: Spoons
• user-space hangs - followup
  • From: Dan Miller
• Re: gcc optimization changes results
  • From: Joe Beanfish
• Re: accessing internal h/w timers
  • From: Bob Hauck
• Re: gcc optimization changes results
  • From: nirnimesh
• Re: gcc optimization changes results
  • From: Spoons
• Load balancing using SCHED_RR
  • From: abhi147
• Re: gcc optimization changes results
  • From: sandy
• accessing internal h/w timers
  • From: techietone
• Re: gcc optimization changes results
  • From: Ulrich Eckhardt
• Re: gcc optimization changes results
  • From: Thomas Richter
• Re: gcc optimization changes results
  • From: Thomas Richter
• Re: Compilaytion Problem
  • From: Paul Pluzhnikov
• Re: Compilaytion Problem
  • From: Thomas Richter
• Compilaytion Problem
  • From: Prafulla T
• Re: gcc optimization changes results
  • From: nirnimesh
• Re: gcc optimization changes results
  • From: Tauno Voipio
• gcc optimization changes results
  • From: nirnimesh
• Re: large file access at different locations
  • From: David Schwartz
• Re: Newbie at Embedded Linux
  • From: Stephane M
• integrating driver with kernel tree (2.4.20)
  • From: Roman Mashak
• Re: Accessing Real Page 0
  • From: gil_hamilton
• Re: Newbie at Embedded Linux
  • From: Peter
• Accessing Real Page 0
  • From: Martin Feeney
• Re: large file access at different locations
  • From: Chris Friesen
• Re: Newbie at Embedded Linux
  • From: Stephane M
• Re: request_irq() changes from red hat to suse
  • From: dnewbold
• Re: request_irq() changes from red hat to suse
  • From: dnewbold
• Re: request_irq() changes from red hat to suse
  • From: gil_hamilton
• Re: request_irq() changes from red hat to suse
  • From: steve_schefter
• Re: request_irq() changes from red hat to suse
  • From: dnewbold
• Re: request_irq() changes from red hat to suse
  • From: Bill Waddington
• Re: How to draw a line in linux using GTK
  • From: Lars Rune Nøstdal
• Re: request_irq() changes from red hat to suse
  • From: dnewbold
• Re: Newbie at Embedded Linux
  • From: Bob Smith
• large file access at different locations
  • From: Ariovist Lowa
• request_irq() changes from red hat to suse
  • From: dnewbold
• Re: Determining the last physical memory address
  • From: gil_hamilton
• How to draw a line in linux using GTK
  • From: Prafulla T
• Re: Determining the last physical memory address
  • From: Martin Feeney
• Determining the last physical memory address
  • From: Martin Feeney
• Newbie at Embedded Linux
  • From: Stephane M
• Re: serial drive
  • From: Grant Edwards
• Re: serial drive
  • From: Ulrich Eckhardt
• serial drive
  • From: Dharmendra
• Native ipsec in 2.6 kernel and openS/WAN
  • From: guruteck
• Re: Help - how to check if an embbeded Linux uses Llittle-Endian or Big-Endian
  • From: Robert Newson
• Re: Compilation Problem
  • From: Michael Heiming
• Compilation Problem
  • From: Prafulla T
• Re: 2.6 USB Throughput Issues?
  • From: Tim Roberts
• Re: suse 10.1 - printk output going no where ...
  • From: dnewbold
• Re: wait_event_interruptible_timeout() occasionally returns -512
  • From: steve_schefter
• Re: 2.6 USB Throughput Issues?
  • From: John Reiser
• Re: how does sleep waiting on an event and triggering that event work in linux
  • From: gil_hamilton
• Re: 2.6 USB Throughput Issues?
  • From: John Reiser
• Re: Getting FILE* from a memory map
  • From: nirnimesh
• how does sleep waiting on an event and triggering that event work in linux
  • From: hari . rulz
• wait_event_interruptible_timeout() occasionally returns -512
  • From: dnewbold
• Re: suse 10.1 - printk output going no where ...
  • From: steve_schefter
• Re: 2.6 USB Throughput Issues?
  • From: John Reiser
• Re: suse 10.1 - printk output going no where ...
  • From: mirek
• 2.6 USB Throughput Issues?
  • From: Tim Roberts
• Re: USB External keyboard / mouse
  • From: Tim Roberts
• Re: 2.6 module makefile - official syntax for SUBDIRS argument
  • From: Bob Hauck
• Re: About Kernel
  • From: Slaytanic
• Re: Getting FILE* from a memory map
  • From: gil_hamilton
• Regarding writing data in registers
  • From: gnanam
• 2.6 module makefile - official syntax for SUBDIRS argument
  • From: dnewbold
• Re: Linux Customization
  • From: Todd Knarr
• Driver memory footprint estimation
  • From: Trastabuga
• suse 10.1 - printk output going no where ...
  • From: dnewbold
• Re: Sharing 4MB of kernel Space in user space
  • From: MK
• About Kernel
  • From: Rahul
• Re: Linux Customization
  • From: Josef Moellers
• Re: Linux Customization
  • From: Bill Marcum
• Sharing 4MB of kernel Space in user space
  • From: MK
• USB External keyboard / mouse
  • From: NAV
• Re: select() problem
  • From: Floyd L. Davidson
• Re: Getting FILE* from a memory map
  • From: gil_hamilton
• Linux Customization
  • From: Prafulla T
• Linux Customization
  • From: Prafulla T
• Re: infos on /dev/mem
  • From: gil_hamilton
• Re: select() problem
  • From: Bob Hauck
• Re: various standard about OS
  • From: Spoons
• Re: Fooling around /proc
  • From: Tim Roberts
• Re: infos on /dev/mem
  • From: Georg Acher
• Re: Linked Lists - Some doubts
  • From: Slaytanic
• Re: Suggestions about protecting data with spinlocks [NEED AN OPINION]
  • From: Slaytanic
• Re: select() problem
  • From: Phil Hobbs
• Re: Suggestions about protecting data with spinlocks [NEED AN OPINION]
  • From: Michael Rasmussen
• Re: Linked Lists - Some doubts
  • From: Michael Rasmussen
• Suggestions about protecting data with spinlocks [NEED AN OPINION]
  • From: Slaytanic
• Re: Linked Lists - Some doubts
  • From: Slaytanic
• Getting FILE* from a memory map
  • From: nirnimesh
• kernel module 64-bit specific #defines
  • From: dnewbold
• Re: Linked Lists - Some doubts
  • From: Michael Rasmussen
• Re: select() problem
  • From: Phil Hobbs
• Re: infos on /dev/mem
  • From: Georg Acher
• Linked Lists - Some doubts
  • From: Slaytanic
• Re: infos on /dev/mem
  • From: gil_hamilton
• Re: Does my processor have local APIC?
  • From: Alexander Krizhanovsky
• Re: how application know if I copy shared library into user defined directory instaed of /lib directory
  • From: Josef Moellers
• Fooling around /proc
  • From: serty2
• Re: Does my processor have local APIC?
  • From: John Reiser
• Does my processor have local APIC?
  • From: Alexander Krizhanovsky
• how application know if I copy shared library into user defined directory instaed of /lib directory
  • From: GS
• Re: how can i get a file descriptor not used?
  • From: Norm Dresner
• Re: strange user-space hangs
  • From: Binary
• Re: infos on /dev/mem
  • From: Georg Acher
• Re: infos on /dev/mem
  • From: gil_hamilton
• how can i get a file descriptor not used?
  • From: mars
• infos on /dev/mem
  • From: steve
• Re: strange user-space hangs
  • From: Dan Miller
• Re: strange user-space hangs
  • From: gil_hamilton
• strange user-space hangs
  • From: Dan Miller
• web100 problem
  • From: Alaa
• Re: SMP and Linux network protocol stack
  • From: cyril.li@xxxxxxxxx
• various standard about OS
  • From: Binary
• Re: How do Linux handle process priority inversion?
  • From: Robert Redelmeier
• Re: check what methods or macros deprecated like MODULE_PARM?
  • From: Jan Wagner

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint

linux.derkeiler.com  > Newsgroups  > comp.os.linux.development.system  > 2006-08