Linux-Development-Sys Digest #161, Volume #8 Wed, 20 Sep 00 13:13:11 EDT
Contents:
Re: new windowing system ("Fr�d�ric G. MARAND")
Re: new windowing system (Alexander Viro)
Re: new windowing system (Derek M. Flynn)
Re: new windowing system ("Fr�d�ric G. MARAND")
Re: How to allocate non cachable driver space? (Bruno Ascenso)
USB & IEEE 1394 support in Kernel 2.2.16 and 2.2.17 (Patrick malloy)
Re: Memprof -- lack of behavior. (Art Haas)
help about ei_* functions and ei_open variables ("Anil Prasad")
Re: Help: Kernel hang/coredump analysis ("Andy Jeffries")
Re: 64M buffer passed from user to kernel (lsnover)
Re: USB & IEEE 1394 support in Kernel 2.2.16 and 2.2.17 ("peter.katzmann")
Re: Multiple c source files for a kernel module? (Tasos Kotaras)
Re: new windowing system (John Reiser)
Infos about Brooktree BT86X (Joachim Rosskopf)
Re: Help: Kernel hang/coredump analysis (Michel Talon)
is there a tutorial on modprobe and kin?? ("A derelict Engineer")
Re: 64M buffer passed from user to kernel (Mario Klebsch)
Re: Help: Kernel hang/coredump analysis (Andreas K�h�ri)
----------------------------------------------------------------------------
From: "Fr�d�ric G. MARAND" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.windows.x
Subject: Re: new windowing system
Date: Wed, 20 Sep 2000 15:16:15 +0200
Well...
dadidguy doesn't use X at all - neither Xlib nor protocol
kivinen uses XLib
cmills uses XLib
tvr uses XLib
jonth uses XLib
So which one were you referring to ?
Alexander Viro <[EMAIL PROTECTED]> a �crit dans le message :
8qaam0$[EMAIL PROTECTED]
> In article <8qa8ab$jh5$[EMAIL PROTECTED]>,
> Fr�d�ric G. MARAND <[EMAIL PROTECTED]> wrote:
> >Did you ever see an application using the X protocol directly without
going
> >through the X library ? I'd be interested in any information about that.
>
> Yes.
> <chuckle> As a starting point, check one that was on IOCCC. Probably one
> of the shortest examples...
>
> --
> "You're one of those condescending Unix computer users!"
> "Here's a nickel, kid. Get yourself a better computer" - Dilbert.
------------------------------
From: [EMAIL PROTECTED] (Alexander Viro)
Crossposted-To: comp.os.linux.x,comp.windows.x
Subject: Re: new windowing system
Date: 20 Sep 2000 09:07:36 -0400
In article <8qa9qi$gtp$[EMAIL PROTECTED]>,
Casper H.S. Dik - Network Security Engineer <[EMAIL PROTECTED]> wrote:
>[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]
>
>[EMAIL PROTECTED] (Alexander Viro) writes:
>
>>In article <8qa4u4$f0m$[EMAIL PROTECTED]>,
>>Casper H.S. Dik - Network Security Engineer <[EMAIL PROTECTED]> wrote:
>
>>>But loadable or not, it doesn't really matter on a paging based
>>>system. Unused code is simply paged out and shouldn't bother
>>>your application.
>
>><sarcasm target=Solaris>
>>Especially when swap competes with /tmp for space, right?
>></sarcasm>
>
>Which OS requires swap to back program text?
It was a long time since I've looked at the memory use of Xsun, but
IIRC it had a bloody lot of data structures initialized upon the startup
(dynamically, that is).
And yes, I realize that cost of running CDE et.al. outweights that -
which is a great reason for not touching them with a 10 feet pole...
--
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert.
------------------------------
From: [EMAIL PROTECTED] (Derek M. Flynn)
Crossposted-To: comp.os.linux.x,comp.windows.x
Subject: Re: new windowing system
Date: Wed, 20 Sep 2000 13:30:21 GMT
Fr�d�ric G. MARAND wrote:
> Did you ever see an application using the X protocol directly without going
> through the X library ? I'd be interested in any information about that.
Xlib is just the C bindings to the X protocol. There are/were many alternate
bindings. I believe the common lisp ones were the most popular of the
alternatives. But that was some time ago; most everyone uses C for X
programming, now.
------------------------------
From: "Fr�d�ric G. MARAND" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.windows.x
Subject: Re: new windowing system
Date: Wed, 20 Sep 2000 15:37:56 +0200
Quite so. Which is why I asked in the first place. But I didn't think of
alternate languages: you're perfectly on point.
Derek M. Flynn <[EMAIL PROTECTED]> a �crit dans le message :
[EMAIL PROTECTED]
> Fr�d�ric G. MARAND wrote:
>
> > Did you ever see an application using the X protocol directly without
going
> > through the X library ? I'd be interested in any information about that.
>
> Xlib is just the C bindings to the X protocol. There are/were many
alternate
> bindings. I believe the common lisp ones were the most popular of the
> alternatives. But that was some time ago; most everyone uses C for X
> programming, now.
>
------------------------------
From: Bruno Ascenso <[EMAIL PROTECTED]>
Subject: Re: How to allocate non cachable driver space?
Date: Wed, 20 Sep 2000 14:40:09 +0100
"F. Heitkamp" wrote:
> I want to allocate space for a driver.
> Not a PCI/ISA card. In fact not on PC architecture.
> How do I allocate non cachable space for the I/O.
> This will be memory mapped I/O.
>
> Fred
When mapping, use 'ioremap_nocache()'
--Bruno
____________________________________________________________________________
WATM2000:
ATM sem fios em placas DSSS 802.11
E-mail: [EMAIL PROTECTED]
URL: http://feldspato.ist.utl.pt/~watm2000
Autores:
Bruno Ascenso: [EMAIL PROTECTED]
Bruno Santos : [EMAIL PROTECTED]
------------------------------
From: Patrick malloy <[EMAIL PROTECTED]>
Subject: USB & IEEE 1394 support in Kernel 2.2.16 and 2.2.17
Date: Wed, 20 Sep 2000 09:43:51 -0400
Hi all,
I recently upgraded my kernel from 2.2.14 to 2.2.16. I downloaded the
*apparently full* tarball. When I ran xconfig there wasn't any USB or
IEEE 1394 support listed. I poked around in the header files and didn't
find the ones that were in the 2.2.14 tarball.
So, I went back and found the new 2.2.17 tarball and gave that a try to
no avail. The other support that wasn't included was for the reiser
filesystem.
Can anyone tell me if this suppor was left out on purpose or am I
getting bad tarballs?
Thanks for any help with this.
Pat
------------------------------
From: Art Haas <[EMAIL PROTECTED]>
Subject: Re: Memprof -- lack of behavior.
Date: 20 Sep 2000 08:44:31 -0500
Szabolcs Csetey <[EMAIL PROTECTED]> writes:
> Art Haas <[EMAIL PROTECTED]> wrote:
> > I didn't think it would catch new() leaks, but I wasn't sure.
>
> new() uses malloc internally so all mem debug tool catches those leaks
> as well.
>
> > Purify catches these problems, but if you want an open-source type
> > tool, it won't do. I've seen it in action, though, and it does a great
> > job at finding these problems. There is the GNU Checker program, which
> > does similar things, but it doesn't seem to be maintained. Perhaps
>
> There are quite a lot of tools, a quick search should give you back tons
> of them. My favourits are yamd and mpatrol (both are free), of course
> they caught both leaks.
>
> [ ... snip ... ]
Thanks for the info on these two programs. They'll be extremely handy.
--
###############################
# Art Haas
# (713) 689-2417
###############################
------------------------------
From: "Anil Prasad" <[EMAIL PROTECTED]>
Subject: help about ei_* functions and ei_open variables
Date: 20 Sep 2000 13:54:09 GMT
hi!!
in source code of some pci cards i found out variables and function names
starting with ei_ (Like ei_open, ei_close and ei_status structure) but i
couldn't find any declaration of these variables and functions . can
anybody tell what are these??
------------------------------
From: "Andy Jeffries" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.apps
Subject: Re: Help: Kernel hang/coredump analysis
Date: Wed, 20 Sep 2000 14:58:27 +0000
In article <[EMAIL PROTECTED]>, Andreas K�h�ri
<[EMAIL PROTECTED]> wrote:
> In article
> <[EMAIL PROTECTED]>, Liaw Yong
> Shyang <[EMAIL PROTECTED]> wrote:
>>Hi,
>>
>>I have midified and recompiled the Linux kernel for my project. I can
>>reboot from my new kernel image successfully, and it works happily.
>>However, the system will hang from time to time. How can I debug, as I
>>could not repeat the bug at my will?? Is it any tool that I can use to
>>analyse coredump? Any book or article I can read more about coredump
>>analysis?
>>
>>I really appreciate if you can help. Thank in advance.
>>
>
> Core dumps may be analyzed using e.g. the 'gdb' debugger.
>
>
> $ gdb -c ./core
>
> This will start 'gdb' and tell you what executable created the core file
> (I hope! It does with a small example I'm playing with). From
> 'gdb' type "file a.out" (where 'a.out' is the name of the executable
> that 'gdb' said generated the core file) and then type "where".
>
> /A
>
Just for people's interest the "file" utility will also tell you which binary
generated a core dump. Very cool little utility that file command.
--
Andy Jeffries
Lead-developer of Scramdisk for Linux
Developer of original Scramdisk Delphi Component
------------------------------
From: lsnover <[EMAIL PROTECTED]>
Subject: Re: 64M buffer passed from user to kernel
Date: Wed, 20 Sep 2000 14:21:09 GMT
In article <[EMAIL PROTECTED]>,
Mathias Waack <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Pete Zaitcev) writes:
> > Don't be stupid, Lisa. In what respect bigphisarea is "dirtier" than
> > using "mem="? Mathias advocates to pull the subtle work of picking
at
> > mem_start/memory_end inside your driver.
>
> I answered a posting saying you _must_ use bigphysarea just to show
> other solutions. I didn't say you _must_ use the mem switch.
>
> > If you do that, you have to
> > deal with any bugs, have intricate understanding how the memory is
> > allocated, and support multiply kernel revisions. Certainly a well
> > defined interface of bigphisarea, tested by numerous developers,
> > provides you a better option.
>
> Fine, thats the drawback of the mem switch and the advantages of
> the bigphysarea patch. It isn't really serious. Please remember
> you can't (eventually) patch already patched kernels, you need a
> patch for your exact kernel version and you depend on the
> goodwill of the developers. The mem switch is a well documented
feature
> of the kernel. That's just the opposite point of view. Please don't
tell
> someone how to do something. Tell her all possibilities and let her
> decide. That's the way. I think we agree on that?
>
> Mathias
>
Thanks for all the suggestions, eventhough some of them could have been
presented a little friendlier. I certainly prefer to get several
solutions so I can pick the best for my situation. My requirements in
the embedded world may not be the same for those working in the desktop
world.
I am using lilo on a 2.2.12 kernel. I will probably end up using the
boot parameter solution for short term and then go to the bigphysarea
patch in the near future. (I need a quick and dirtly for prototype
demo.)
Lisa
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "peter.katzmann" <[EMAIL PROTECTED]>
Subject: Re: USB & IEEE 1394 support in Kernel 2.2.16 and 2.2.17
Date: Wed, 20 Sep 2000 16:11:50 +0200
Reply-To: [EMAIL PROTECTED]
Patrick malloy wrote:
>
> So, I went back and found the new 2.2.17 tarball and gave that a try to
> no avail. The other support that wasn't included was for the reiser
> filesystem.
>
> Can anyone tell me if this suppor was left out on purpose or am I
> getting bad tarballs?
You should give the 2.2.18 pre a chance, there will be backports from
the 2.4.x tree and contributions from distributors which also include
our requested features.
peter
------------------------------
From: Tasos Kotaras <[EMAIL PROTECTED]>
Subject: Re: Multiple c source files for a kernel module?
Date: Wed, 20 Sep 2000 10:06:17 +0300
Ed Hudson wrote:
> Is it possible to create a kernel module from more than one source
> file? If so, how would you go about compiling it?
>
> Thanks,
>
> Ed
At first, get a makefile like this:
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
TARGET = foo
SRC = foo1.c foo2.c . . .
CC = gcc
LD = ld -r
CFLAGS = -D__KERNEL__ -DMODULE -O2 -Wall
### RULES:
all: $(TARGET).o
$(TARGET).o: $(SRC:.c=.o)
$(LD) $^ -o $@ <------------ HERE'S THE TRICK
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
The only problem might be in the case where you include <linux/module.h>
in more than one file: The linker will complain for the multiple
declaration
of the variable kernel_version, which is declared in the above header
file.
To circumvent this problem, define __NO_VERSION__ to prevent
<linux/module.h> from declaring this variable, and instead, do it
yourself
(just once), like this:
char kernel_version[] = UTS_RELEASE;
If you ever get A. Rubini's "Linux Device Drivers" in your hands,
check page 21.
`\|||/
(@@)
_ooO_(_)_Ooo________________________________
______|_____|_____|_____|_____|_____|_____|_____|
_____|__________|_____|_____|____|_____|____|_____
|________Tasos Kotaras___|_____|____|_____|_____|
___|___|__Telecom Software Engineer_____|____|____
_____|_____Access Net & Wireless Comm Dept
|_______|___INTRACOM___|_____|______|______|____
__|___|______Peania 19002, Greece_|_____|____
___e-mail: [EMAIL PROTECTED]|____|____|____|
|_____Phone: +30 1 6690185_______|_____|______
------------------------------
From: John Reiser <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.windows.x
Subject: Re: new windowing system
Date: Wed, 20 Sep 2000 08:03:20 -0700
"Fr�d�ric G. MARAND" wrote:
>
> Did you ever see an application using the X protocol directly without going
> through the X library ? I'd be interested in any information about that.
Applications such as 'xscope' and 'xmon', which analyze and print
X11 protocol, also do not go through the X11 library, at least not
in the usual way. It's not uncommon to discover that some redraws
or other stylized use of X11 protocol (by either "application" or
"widget") could reduce traffic by 30% to 50%, in both bytes and roundtrips.
--
John Reiser, [EMAIL PROTECTED]
------------------------------
From: Joachim Rosskopf <[EMAIL PROTECTED]>
Subject: Infos about Brooktree BT86X
Date: Wed, 20 Sep 2000 19:52:09 GMT
Hello,
I search some futher information about the brooktree BT86X chipset=20
series. I try to develope some piece of code to run the TV Output on=20
several Graphic Cards. I think the bt chipset and the vga out are on a=20
I=B2C bus so the technologie is quite similar to the to tv tuner cards=20
which are already integrated into the kernel.=20
Thank you for help in advantage
Joachim
------------------------------
From: Michel Talon <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.apps
Subject: Re: Help: Kernel hang/coredump analysis
Date: Wed, 20 Sep 2000 18:32:41 +0200
In comp.os.linux.development.system Andy Jeffries <[EMAIL PROTECTED]> wrote:
>>>I have midified and recompiled the Linux kernel for my project. I can
>>>reboot from my new kernel image successfully, and it works happily.
>>>However, the system will hang from time to time. How can I debug, as I
>>>could not repeat the bug at my will?? Is it any tool that I can use to
>>>analyse coredump? Any book or article I can read more about coredump
>>>analysis?
>>>
>>
>> $ gdb -c ./core
>>
> Just for people's interest the "file" utility will also tell you which binary
> generated a core dump. Very cool little utility that file command.
Yes fine, but how do you capture a coredump of the kernel? I did not know such
a possibility existed in Linux. Is it new? For reference this functionnality
exists in *BSD. On panic a coredump is written to the swap area, and can be
examined by gdb after reboot with a working kernel.
--
Michel Talon
------------------------------
From: "A derelict Engineer" <[EMAIL PROTECTED]>
Subject: is there a tutorial on modprobe and kin??
Date: Wed, 20 Sep 2000 09:57:10 -0700
I'm still having problems getting modprobe to work properly. I had
previously installed Redhat 6.1 on a system with no problems, but after I
rebuilt the kernel, I got tons of "module not found" errors on boot.
Someone told me to run "make modules modules_install" to solve this problem,
and it mostly worked (though one non-existent module remained unfound).
However, when I go and look in the /lib/modules/2... directory, most of the
subdirectories have many many .o files in them, yet modprobe does NOT try to
load them all... where is the reference list which tells modprobe which
modules to try to load??
For example, after I did the modules_install step mentioned above, the
system still tried to load scsi/megaraid.o ... I don't have any scsi
devices, so naturally that failed... however, the /lib/modules/2.../scsi
directory has some 20 object files in it; none of the others tried to load,
or they'd have failed also. I looked in /etc, /etc/rc.d, /etc/rc.d/init.d,
and no file in *any* of those directories contained a "modprobe megaraid.o"
line...
Where is the master reference list???
... and is there a tutorial anywhere about this process, that will make me
an expert on it?? The man page certainly wasn't sufficient!!
Can anyone tell me what package this utility came with, in the event that
I'm reduced to reading the sources for information??
Thank you all for your assistance!!
------------------------------
From: [EMAIL PROTECTED] (Mario Klebsch)
Subject: Re: 64M buffer passed from user to kernel
Date: Wed, 20 Sep 2000 18:20:49 +0200
Mathias Waack <[EMAIL PROTECTED]> writes:
>The kernel will work (eventually). But the driver doesn't. Passing
>parameters to the kernel is a well documented feature of Linux, which
>can and should be used. There is only one other solution: patching the
>kernel. What kind of solution would you prefer? If you think that
>kernel parameters are ugly, what do think about kernel patches?
What about patching the parameters into the kernel. I can imagine
having a kind of default command line, which is used, when no
parameters are specified. If any driver requires some parameter on the
command line, they could be added to this default command line during
the build process.
73, Mario
--
Mario Klebsch [EMAIL PROTECTED]
PGP-Key available at http://www.klebsch.de/public.key
Fingerprint DSS: EE7C DBCC D9C8 5DC1 D4DB 1483 30CE 9FB2 A047 9CE0
Diffie-Hellman: D447 4ED6 8A10 2C65 C5E5 8B98 9464 53FF 9382 F518
------------------------------
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.apps
Subject: Re: Help: Kernel hang/coredump analysis
From: Andreas K�h�ri <[EMAIL PROTECTED]>
Date: 20 Sep 2000 19:06:53 +0100
In article <[EMAIL PROTECTED]>,
Michel Talon <[EMAIL PROTECTED]> wrote:
>In comp.os.linux.development.system Andy Jeffries <[EMAIL PROTECTED]> wrote:
>>>>I have midified and recompiled the Linux kernel for my project. I can
>>>>reboot from my new kernel image successfully, and it works happily.
>>>>However, the system will hang from time to time. How can I debug, as I
>>>>could not repeat the bug at my will?? Is it any tool that I can use to
>>>>analyse coredump? Any book or article I can read more about coredump
>>>>analysis?
>>>>
>>>
>>> $ gdb -c ./core
>>>
>
>> Just for people's interest the "file" utility will also tell you which binary
>> generated a core dump. Very cool little utility that file command.
>
>Yes fine, but how do you capture a coredump of the kernel? I did not know such
>a possibility existed in Linux. Is it new? For reference this functionnality
>exists in *BSD. On panic a coredump is written to the swap area, and can be
>examined by gdb after reboot with a working kernel.
>
>--
>Michel Talon
I was under the impression that the OP *had* a kernel core dump... My
answer was quite general and concerned debugging core dumps in
general. One might have to do "special things" to debug GNU/Linux
kernel core dumps, I don't know...
/A
--
Andreas K�h�ri, <URL:http://hello.to/andkaha/>. Junk mail, no.
========================================================================
Put a part of GNU in every box: <URL:http://www.gnu.org/>
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
