Linux-Development-Sys Digest #690
Linux-Development-Sys Digest #690, Volume #8 Fri, 4 May 01 11:13:18 EDT Contents: serial port autodetection (Javier Loureiro Varela) Re: Is linux kernel preemptive?? (Neal Tucker) losing bottom halves (Barry Smyth) Re: Interprocess Communication...help (Nick Lockyer) Re: Is there a limit of the number of kernel modules? (Nick Lockyer) Re: malloc Bug? (Wolfram Gloger) Re: serial port autodetection (Roberto Nibali) Re: Kernel 2.4.4 Problems (Fruitbat) Re: losing bottom halves (Arne Driescher) floppy problem with kernel 2.4.2 (jerome corre) simple processus termination (Karim Atiki) Re: serial port autodetection (Grant Edwards) Help: Kernel module doesn't compile after kernel upgrade. (Stefan) Re: Help: Kernel module doesn't compile after kernel upgrade. (Peter T. Breuer) Re: simple processus termination (Chris) Re: Is linux kernel preemptive?? (Greg Copeland) Re: simple processus termination (Steve Connet) Re: IO system throughput (Greg Copeland) Re: STLport 4.0 g++ 2.96 (Steve Connet) Re: Need your recommendation for a full-featured text editor (Keith Lomax) Large file support on Linux? (Dragan Cvetkovic) From: [EMAIL PROTECTED] (Javier Loureiro Varela) Subject: serial port autodetection Date: Fri, 04 May 2001 09:04:27 GMT hI! I'd like to autodetect some params from a serial port attached to my serial port (like modems do). I was searching for it, but I dont know where to start on. any keyword will be apreciated!! -- signed, Javier Loureiro Varela Class One System Research Leader -- From: [EMAIL PROTECTED] (Neal Tucker) Subject: Re: Is linux kernel preemptive?? Date: 4 May 2001 02:09:45 -0700 Greg Copeland says: The use of system call is a very ambiguous term which I feel people often assign specific attributes that does not really exist. I like to avoid all of that and think of system calls as just that. A function residing within the system. In this case, I think of system as being the kernel. This is where we differ. As I was taught in my Operating Systems classes back in school, a system call is a function in the kernel which a user level program calls to use the OS functionality. The system calls are the interface to the OS from the applications. At any rate, the whole disagreement in this thread is based on you guys not agreeing on the terminology. It doesn't matter how you define system call, as long as the participants agree on how to define it. You don't, so your discussion is going in circles. -Neal Tucker -- From: Barry Smyth [EMAIL PROTECTED] Subject: losing bottom halves Date: Fri, 4 May 2001 10:11:07 +0100 Hi, I am writing a driver for a PCI card using interrupts. I have a main interrupt service routine and inside this I schedule a bottom half to the immediate task queue. Most of the time when running the program everything works fine, however occasionally all the interrupts occur and the isr gets run but the bottom half does not occur for every interrupt. I have replaced the scheduling of the bottom half with a direct call to the bottom half from the interrupt service routine and the program works every time. Could anyone explain why skipping of bottom halves could be occuring when using scheduling? Is it because the code in the bottom half takes too long to run? If it is then why does calling the bottom half directly fix the problem? I am using kernel 2.2.17. Thanks -- From: Nick Lockyer [EMAIL PROTECTED] Crossposted-To: comp.os.linux.development.apps Subject: Re: Interprocess Communication...help Date: Fri, 4 May 2001 10:44:57 +0100 Another really good book which clearly shows this with nice pretty picture (which even I could follow) is the Beginning Linux Programming, ISBN 1861002971 (see www.amazon.co.uk/www.amazon.com). Karim Atiki [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Hi all, I have to implement a way to communicate between tow applications. For some reasons, I've chosen the pipe() function . Basically, her's what I want to do: 1) I've an application, qt based,named APP1. this application gets some parameters from Gfx Widgets. Then , user pushes a run button in order to launch another application (APP2) I launch it by using fork() and execle() 2) So the next step is: to communicate between the 2 application. I want APP1 gives orders to APP2 such like RUN, PAUSE, RESUME. For each of these commands, I want APP2 to notifiy APP1 that commands have been correctly handled. So, I'm not very experienced with Interprocess-Communication under Unix/Linux. I would like to know how should my applications structured in order to manage such an IPC. How should I use the fork() and pipe() calls ? Please let me know if you have an idea
Linux-Development-Sys Digest #690
Linux-Development-Sys Digest #690, Volume #7 Mon, 20 Mar 00 12:13:14 EST
Contents:
moderm card! ("sang")
Re: ramdisk: releasing memory (Thomas Eschenbacher)
SIMD and PIII (Pascal Junod)
Re: sharing DMAable memory (Mathias Waack)
Kernelmeldung ... und was bedeutet sie?! (Daniel Schulze)
kernelmessage ... and now? (Daniel Schulze)
Re: Bootdisks, rdev, and root filesystems...aargh! (Ron Gibson)
Re: mmap PCI I/O registers (Alan Donovan)
Re: underscores (Alan Donovan)
Re: File System Development (Alan Donovan)
Re: BHs in 2.3.X Kernels (Martin Gruber)
Re: ramdisk: releasing memory (Villy Kruse)
Re: Rubini's device driver example (nilesh patel)
Shared memory and kernel module (MidiShare)
Re: Shared memory and kernel module (mlw)
Problem with sendmsg () (Bernd Draxler)
Re: mmap PCI I/O registers ([EMAIL PROTECTED])
How to insert a intermediate filtering driver between ethernet and TCP/IP stack
([EMAIL PROTECTED])
gcc: how to read/write a block ([EMAIL PROTECTED])
Re: sharing DMAable memory (Grant Edwards)
From: "sang" [EMAIL PROTECTED]
Subject: moderm card!
Date: Mon, 20 Mar 2000 15:33:40 +0800
I have a moderm card inside computer. How do I setup it in linux?
Because it does not connect with com1 or com2.
--
From: Thomas Eschenbacher [EMAIL PROTECTED]
Subject: Re: ramdisk: releasing memory
Date: Mon, 20 Mar 2000 09:20:51 +0100
Peter Pointner schrieb:
[...]
Is there any way to _really_ get rid of the memory used in the ramdisk?
[...]
I thought the utility "freeramdisk" should do that?
how amusing :-)
Two days ago I took a look in the kernel source and wrote a little
program with the same name that calls ioctl(BLKFLSBUF) and takes the
device name as first cmdline parameter.
But this doesn't work either.
Now I solved my problem in another way and just don't make use of a
temporary ramdisk for packing/unpacking files: I pipe them through a
filter that reads the original file into memory, removes it and writes
the output to stdout where I can filter it through "gzip" or "gzip -d".
Thanks nevertheless,
Thomas.
--
Thomas Eschenbacher [EMAIL PROTECTED]
--
Date: Mon, 20 Mar 2000 09:30:35 +0100
From: Pascal Junod [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Subject: SIMD and PIII
I can write assembly routines which uses SIMD extensions of the PIII
using nasm, but :
Does the kernel support the new registers (context switch while
scheduling, and so ?)
I have found very few information about this topic.
Thanks for your help
Pascal
--
~
* Pascal Junod, [EMAIL PROTECTED]*
* Laboratoire de Sécurité et de Cryptographie, EPFL *
* ++ 41 (0) 21 693 7617 Lausanne (Switzerland) *
* Route d'Yverdon 25, CH-1028 Préverenges *
~
--
From: Mathias Waack [EMAIL PROTECTED]
Subject: Re: sharing DMAable memory
Date: Mon, 20 Mar 2000 10:37:22 +0100
Hi,
Mirko Saam wrote:
the driver should allocate a dma-able piece of
memory (via ioctl) and return a pointer to the
caller. The caller must be able to read and write
this memory. The old code segment looks like:
pAdr = (unsigned long) kmalloc (size, GFP_DMA | GFP_BUFFER);
uAdr = do_mmap (file, 0, (size+~PAGE_MASK) PAGE_MASK,
PROT_READ | PROT_WRITE, MAP_SHARED,
pAdr PAGE_MASK);
return(uAdr);
This only produces a SEGV if the caller tries
to access the pointer (read or write). What's
the right way to this with 2.2.x kernels?
I've read Rubini's book and was not able to find
a working solution.
Read the book again, especially chapter 13: Mmap and DMA.
Rubini describes a driver called "scullp" doing nearly the
same work as your driver should do.
Or short anwser: implement you own mmap method instead of
calling do_mmap.
HTH
Mathias
--
Mathias Waack | [EMAIL PROTECTED]
Tel.: +49 621 181 2717 Fax.: +49 621 181 2713
--
From: Daniel Schulze [EMAIL PROTECTED]
Subject: Kernelmeldung ... und was bedeutet sie?!
Date: Mon, 20 Mar 2000 10:46:49 +0100
Hallo Leute
Folgendes Problem:
Ich steckte mal eben noch 64MB Speicher rein und dann...
Ziemlich früh während des Hochfahrens bricht der Kern (SuSE 2.2.13) mit
folgender Meldung ab:
Memory: 127680k/131072k (1240k kernel, 412k reserved, 1676k data, 64k
init, 0k big)
kmem-alloc: Bad slab magic (corrupt) name=kmem_cache
canot create uid taskcount SLAB cache
Was will er mir sagen?!
Übrigens mit der mem-Option = 64M funktioniert es wie gehabt und das
BIOS meint wirklich 128MB zur Ver
Linux-Development-Sys Digest #690
Linux-Development-Sys Digest #690, Volume #6 Sat, 8 May 99 14:14:16 EDT
Contents:
Re: Y2K bug in strptime ? (libc5) ("Robert H. de Vries")
Re: Get client machine's IP-address (Horst von Brand)
Failed building glibc-2.1.1pre2, please help ([EMAIL PROTECTED])
Re: Failed building glibc-2.1.1pre2, please help (Andreas Jaeger)
Re: Failed building glibc-2.1.1pre2, please help (Paul Kimoto)
Re: Glibc rant (Greg White)
Re: Need help. My kernel won't compile on my new system. (Captain Panic)
Re: glibc-2.1 and incompatible apps (Sid Boyce)
Re: tulip driver woes (was Re: Reliable (!) nic for 2.2 kernel?) (bryan)
tulip driver woes (was Re: Reliable (!) nic for 2.2 kernel?) (Paul Kimoto)
Re: glibc-2.1 and incompatible apps (Juergen Heinzl)
creative webcam I - I got the specs... (Matthias Wientapper)
Re: Reliable (!) nic for 2.2 kernel? ("Doug Pitek")
porting Linux to other processors (Joseph Virzi)
PCI Hot Plug Support (Joseph Virzi)
Sound card driver help? ("Luke A. Guest")
Re: Reliable (!) nic for 2.2 kernel? (bryan)
Re: Reliable (!) nic for 2.2 kernel? (Richard Torkar)
From: "Robert H. de Vries" [EMAIL PROTECTED]
Subject: Re: Y2K bug in strptime ? (libc5)
Date: Sat, 08 May 1999 09:16:11 +0200
Peter Verthez wrote:
I found the following peculiar behaviour in strptime.
Compile and run the following program:
-
#include stdio.h
#include time.h
int main()
{
struct tm tmdate;
char* date = "01/04/2000";
strptime(date, "%d/%m/%Y", tmdate);
printf ("The parsed year is: %d\n", tmdate.tm_year);
return 0;
}
-
The result will be:
The parsed year is: 0.
Isn't tm_year supposed to be the number of years since
1900 ?
Yes. The correct answer would be 100.
At least, that is what I found in "Advanced
Programming in the UNIX Environment", but the manpage
of strptime only says that tm_year is a "year".
Details of my system:
- linux 2.0.26
- libc 5.4.23
The new C library glibc fixes this.
I now run RedHat 6.0 with glibc 2.1.1.
Robert
--
Robert de Vries
[EMAIL PROTECTED]
--
From: [EMAIL PROTECTED] (Horst von Brand)
Crossposted-To:
it.comp.linux.development,comp.os.linux.networking,comp.os.linux.development.apps,comp.programming,comp.protocols.tcp-ip,comp.protocols.tcp-ip.domains,comp.unix.programmer,comp.unix.sco.programmer
Subject: Re: Get client machine's IP-address
Date: 8 May 1999 09:17:11 GMT
On Wed, 05 May 1999 16:56:17 +0200, Iond Research Srl [EMAIL PROTECTED] wrote:
Does anybody know how can I get in a stand-alone C/C++ program, running on
a server machine but started during a telnet/rlogin session, the IP-address
of the client machine that launched the telnet session ?
Impossible to know, as there is nothing that points back in this case.
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Viña del Mar, Chile +56 32 672616
--
From: [EMAIL PROTECTED]
Subject: Failed building glibc-2.1.1pre2, please help
Date: Sat, 08 May 1999 08:07:46 GMT
Hello,
I was trying to build glibc but got undefined reference to "__printf_fphex".
I am using:
slackware 3.6 with 2.2.7 kernel,
gcc version pgcs-2.91.66 19990314 (egcs-1.1.2) release,
make 3.77,
binutils 2.9.1.0.24
Glibc was configured using CFLAGS="-mpentiumpro -march=pentiumpro"
../configure --enable-omitfp --enable-add-ons=crypt,linuxthreads
Error message I got:
make -C db2 others make[2]: Entering directory
`/usr/src/glibc-2.1.1pre2/db2' gcc -nostdlib -nostartfiles -o
/usr/src/glibc-2.1.1pre2/obj/db2/makedb -Wl,-dyn
amic-linker=/usr/local/lib/ld-linux.so.2
/usr/src/glibc-2.1.1pre2/obj/csu/crt1 .o
/usr/src/glibc-2.1.1pre2/obj/csu/crti.o `gcc --print-file-name=crtbegin.o` /u
sr/src/glibc-2.1.1pre2/obj/db2/makedb.o
/usr/src/glibc-2.1.1pre2/obj/db2/libdb.s o.3
-Wl,-rpath-link=/usr/src/glibc-2.1.1pre2/obj:/usr/src/glibc-2.1.1pre2/obj/m
ath:/usr/src/glibc-2.1.1pre2/obj/elf:/usr/src/glibc-2.1.1pre2/obj/nss:/usr/sr
c/g
libc-2.1.1pre2/obj/nis:/usr/src/glibc-2.1.1pre2/obj/db2:/usr/src/glibc-2.1.1p
re2
/obj/rt:/usr/src/glibc-2.1.1pre2/obj/resolv:/usr/src/glibc-2.1.1pre2/obj/linu
xth reads /usr/src/glibc-2.1.1pre2/obj/libc.so.6
/usr/src/glibc-2.1.1pre2/obj/libc_n onshared.a -lgcc `gcc
--print-file-name=crtend.o` /usr/src/glibc-2.1.1pre2/obj/c su/crtn.o
/usr/src/glibc-2.1.1pre2/obj/libc.so.6: undefined reference to
`__printf_fphex' collect2: ld returned 1 exit status make[2]: ***
[/usr/src/glibc-2.1.1pre2/obj/db2/makedb] Error 1 make[2]: Leaving directory
`/usr/src/glibc-2.1.1pre2/db2' make[1]: *** [db2/others] Error 2 make[1]:
Leaving directory `/usr/src/glibc-2
