Linux-Development-Sys Digest #192, Volume #8 Thu, 5 Oct 00 03:13:09 EDT
Contents:
Re: Linux partition question? ("E-mu")
hello,I want to begin with linux kernal programming?? (hushui)
include file for printk() (Zhihui Zhang)
vmlinuz (Bo - Sun)
upgrade (Bo - Sun)
Re: vmlinuz ("Steve Schefter")
Re: cscope (Bruce Stephens)
Re: How SMP works in Linux (Karl Heyes)
Re: hello,I want to begin with linux kernal programming?? (Lac Hao Viet)
HELP -- understanding ([EMAIL PROTECTED])
Re: upgrade (Karl Heyes)
Re: How SMP works in Linux ("???")
Re: How SMP works in Linux (=?ks_c_5601-1987?B?wMzBvrHH?=)
Re: Sony Memory Stick ("E-mu")
Red Hat 7.0 and Kernel 2.4.0-test9 question? ("E-mu")
Re: Sony Memory Stick (Reinald Kirchner)
Re: mmap problem in pci driver ("Edward A. Hildum")
Re: PCI Documentation (Mark McDougall)
----------------------------------------------------------------------------
From: "E-mu" <[EMAIL PROTECTED]>
Subject: Re: Linux partition question?
Date: 04 Oct 2000 20:19:26 GMT
Thanks much :)
"James T. Dennis" <[EMAIL PROTECTED]> wrote in message
news:8rer40$bn3$[EMAIL PROTECTED]...
> E-mu <[EMAIL PROTECTED]> wrote:
>
> > Sorry, here are prinouts generated from cfdisk and fdisk respectivley.
Note
> > that CFDISK does not make note of /dev/hda3. Why does Linux FDISK see
this
> > as a 'Win95 Ext'd (LBA)' ? Partition Magic just sees it as just an
> > Extended Primary Partition. I was told that the ID should be '5' and
not
> > 'f' and that I would not be able to install or run linux the way I have
my
> > partitions set up right now? Well I am running both linux and windows
98SE
> > just fine under a dual boot system :)
>
> > CFDISK
>
> Basically useless. Use fdisk or sfdisk.
>
>
> > Name Flags Part Type FS Type [Label]
> > Size(MB)
>
> > -------------------------------------------------------------------
> > hda1 Primary Linux ext2 [/boot] 23.23
> > hda2 Boot Primary Win95 FAT32(LBA) 14004.27
> > hda5 Logical Win95 FAT32 526.42
> > hda6 Logical Linux swap 270.96
> > hda7 Logical Linux ext2 [/] 5179.03
>
>
> > FDISK
>
> > Device Boot Start End Blocks Id System
> > /dev/hda1 1 3 22648+ 83 Linux
> > /dev/hda2 * 4 1812 13676040 c Win95
FAT32
> > (LBA)
> > /dev/hda3 1813 2584 5836320 f Win95 Ext'd
> > (LBA) <<<<<<< This is suppose to be ID 5, Linux Exten. Prim.
>
> Actually /dev/hda3 can be any sort of extended partition as
> far as Linux is concerned.
>
> > /dev/hda5 1813 1880 514048+ b Win95 FAT32
> > /dev/hda6 1881 1915 264568+ 82 Linux swap
> > /dev/hda7 1916 2584 5057608+ 83 Linux
>
> As I suspected. This is a perfectly normal partition table with
> a minor quirk: the extended partition is marked as type f (Win'95
> extended) rather than type 5 (normal/DOS extended) or 85 (Linux
> extended). That quirk is of no operational consequence to Linux.
>
>
------------------------------
From: hushui <[EMAIL PROTECTED]>
Subject: hello,I want to begin with linux kernal programming??
Date: Wed, 04 Oct 2000 17:20:28 -0400
Reply-To: hushui
This is a multi-part message in MIME format.
==============EC3FC2481B9E9F31E70D9120
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I want to know how to know how to start??
can anybody help me??
just send a simple souce to me ??
thank you
==============EC3FC2481B9E9F31E70D9120
Content-Type: text/x-vcard; charset=us-ascii;
name="hushui.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for hushui
Content-Disposition: attachment;
filename="hushui.vcf"
begin:vcard
n:;hushui
x-mozilla-html:FALSE
org:http://hushui.yeah.net
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:I am a linux fan
note:My page is Chinese gb
x-mozilla-cpt:;0
fn:hushui
end:vcard
==============EC3FC2481B9E9F31E70D9120==
------------------------------
Date: Wed, 4 Oct 2000 16:45:33 -0400
From: Zhihui Zhang <[EMAIL PROTECTED]>
Subject: include file for printk()
When I compile a kernel module, it says:
warning: implicit declaration of function 'printk_R1b7d4074"
I guess I need to include some header file for this or what? Thanks for
your help.
-Zhihui
------------------------------
From: Bo - Sun <[EMAIL PROTECTED]>
Subject: vmlinuz
Date: Wed, 4 Oct 2000 16:13:08 -0500
hi, there:
Can some one tell me what is the difference between the 2 files
vmLinux-2.2.14.5.0 and vmLinuz-2.2.14.5.0
I am trying to upgrade my kernel, but after compiling the kernel(make
bzImage), I don't know how to modify /etc/lilo.conf.
thanks,
Bo
------------------------------
From: Bo - Sun <[EMAIL PROTECTED]>
Subject: upgrade
Date: Wed, 4 Oct 2000 16:28:46 -0500
hi, there:
I am trying to upgrade my kernel from 2.2.14 to 2.4, and I use make
bzImage, when I modify the lilo.conf file as:
image = /boot/vmlinux
and run lilo
I get the following error messages:
vmlinux is too large.
Can someone give me some suggestions?
thanks,
Bo
------------------------------
From: "Steve Schefter" <[EMAIL PROTECTED]>
Subject: Re: vmlinuz
Date: Wed, 04 Oct 2000 21:47:44 GMT
Bo - Sun wrote in message ...
>hi, there:
>
>Can some one tell me what is the difference between the 2 files
>vmLinux-2.2.14.5.0 and vmLinuz-2.2.14.5.0
>
>I am trying to upgrade my kernel, but after compiling the kernel(make
>bzImage), I don't know how to modify /etc/lilo.conf.
>
vmlinuz files are compressed kernels while vmlinux files are the raw ones.
In lilo.conf, you want to specify the compressed kernel for the image.
Steve
------------------------------
From: Bruce Stephens <[EMAIL PROTECTED]>
Subject: Re: cscope
Date: 04 Oct 2000 23:27:36 +0100
"St. Otto" <[EMAIL PROTECTED]> writes:
> Is there anywhere a tool like "cscope" (->Solaris)
> under linux (Suse) available ?
Well, there's cscope: <URL:http://cscope.sourceforge.net/>. Also SDS
(which is a bit different, but still relevant):
<URL:http://sds.sourceforge.net/>. cxref:
<URL:http://www.gedanken.demon.co.uk/cxref/>. OO-Browser (for XEmacs,
and probably Emacs)
<URL:http://www.beopen.com/products/oobrowser/oobrowser_overview.html>.
And Source Navigator, <URL:http://sources.redhat.com/sourcenav/>.
If you know you want cscope, then that's available. Otherwise, get
Source Navigator.
------------------------------
From: Karl Heyes <[EMAIL PROTECTED]>
Subject: Re: How SMP works in Linux
Date: Wed, 04 Oct 2000 23:43:20 +0000
In article <8rfa9a$rac$[EMAIL PROTECTED]>,
"???" <[EMAIL PROTECTED]> wrote:
> Isn't there any FAQ?
>
> my question is:
> Q1: What happens when one of two cpu dies in SMP kernel ?
>
Does the hardwars support hot swap/recoverable CPUs?. Linux tries to
provide what the majority require. This isn't a big issue for the majority
of linux installations out there, and support for it will appear in some
form.
> Q2: When one CPU is processing kernel code, can the other CPU process
> application code ?
>
That was supported in 2.0. The scaleability issues that keep being mentioned
are when two processors are executing kernel code. 2.0 had a big kernel lock
for everything kernel related. 2.2 increased scability by providing spinlocks
enabling some kernel functions/facilities that are un-related to exucute at the
same time. 2.4 improves this further.
The network stack in 2.4 is now SMP, I think the VFS is a 2.4 SMP thing as well
> Q3: TUX, a web server which runs in kernel mode, can be accelarated by
> multi-CPU ?
>
If its threaded/cloned, I don't know that much about the TUX implementation,
but I think it is.
karl.
------------------------------
From: Lac Hao Viet <[EMAIL PROTECTED]>
Subject: Re: hello,I want to begin with linux kernal programming??
Date: Wed, 04 Oct 2000 22:36:39 GMT
download source from http://www.kernel.org and look for what you're
interested in and ..start ;)
In article <[EMAIL PROTECTED]>,
hushui wrote:
> This is a multi-part message in MIME format.
> --------------EC3FC2481B9E9F31E70D9120
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> I want to know how to know how to start??
> can anybody help me??
> just send a simple souce to me ??
> thank you
>
> --------------EC3FC2481B9E9F31E70D9120
> Content-Type: text/x-vcard; charset=us-ascii;
> name="hushui.vcf"
> Content-Transfer-Encoding: 7bit
> Content-Description: Card for hushui
> Content-Disposition: attachment;
> filename="hushui.vcf"
>
> begin:vcard
> n:;hushui
> x-mozilla-html:FALSE
> org:http://hushui.yeah.net
> adr:;;;;;;
> version:2.1
> email;internet:[EMAIL PROTECTED]
> title:I am a linux fan
> note:My page is Chinese gb
> x-mozilla-cpt:;0
> fn:hushui
> end:vcard
>
> --------------EC3FC2481B9E9F31E70D9120--
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: HELP -- understanding
Date: Thu, 05 Oct 2000 00:34:47 GMT
Reply-To: [EMAIL PROTECTED]
Hi,
I apologize in advance for the length of this posting.
I'm trying to learn systems/kernel/linux programming and I'm writing to
get confirmation and correction of my understanding of various
driver/system programming concepts. I've listed some assertions below,
and I'm hoping that some knowledgable readers can tell me if they are
correct or incorrect, and if incorrect, why. Any help and pointers will
be GREATLY appreciated as I've spent a fairly large amount of time
trying to figure this stuff out. If you don't have answers to all the
questions, please don't hesitate to comment on the others. Feel free to
be as detailed and brutal as possible (steep learning curve I guess) :)
1)The address space of a machine, as seen by the Linux kernel, can be
divided into three logical sections:
a) "normal/real" memory,
b) I/O address section (a.k.a. I/O ports),
c) I/O memory section
2)The address space of a machine is the range of addresses that can be
specified using all address buses on that machine.
3)A machine may have a number of address "subspaces", depending on
how many busses are used to connect the CPU with main memory and
peripherals. Each bus used for one of these connections defines one
subspace. If one bus is used to establish all necessary conections,
then the three logical sections described in 1) are said to share the
same address space.
4)In the case of an x86 processor, the three logical sections described
in 1) all share the same space. On a non-x86 architecture, these
sections may not share the same space.
-- Does the above imply that there is only one bus interconnecting
the CPU, main memory, and set of peripherals on the x86?
5) It is atypical compared to other architectures that the I/O memory
section and the other sections share the same address space on the
x86 architecture.
6)On a non-x86 architecture that uses a different bus to refer to
main memory than it does to refer to the I/O devices, the logical
I/O port section and "normal/real" section do not share the same
address space.
6a) In the situation specified by 6), the CPU and device controllers
use different addresses to refer to the same physical memory
address.
7)inb/outb operations are used to access the I/O port section in Linux
8)On an x86 machine, the inb/outb operations translate to I/O specific
assembly instructions (in/out) that do not use memory-mapped I/O to
accomplish communication with the specified device.
9)On an x86 machine, the arguments passed to inb/outb operations (I/O
ports -- e.g. 0x03f6, 0x02f8) are used to identify device/register
combinations by passing them onto an address bus.
10)On an x86 machine, the existence of an I/O port identified by 0x03f6
does NOT preclude the existence of any other entity (main memory)
identified by address 0x03f6.
??? I'm really not sure of this one, but I've presented reasons that
it seems to be able to go either way.
10a)The reason it DOES NOT is that the CPU "understands" that the
I/O port 0x03f6 is a part of the I/O port section. It is able to
understand this because the port is accessed only through certain
I/O assembly instructions.
10b)The reason it DOES preclude the existence of another entity
identified by 0x03f6 is because all three sections sharing
the same "address space" means that each address can only be
used to identify one entity.
11)The readb/writeb routines are used access the I/O memory section
described in 1).
12)Accessing the I/O memory section described in 1) is what is meant
by the term "memory-mapped I/O".
Thanks,
Josh Willey
[EMAIL PROTECTED]
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Karl Heyes <[EMAIL PROTECTED]>
Subject: Re: upgrade
Date: Thu, 05 Oct 2000 02:35:56 +0000
In article <Pine.SOL.4.10.10010041627020.15239-100000@robert>, Bo - Sun
<[EMAIL PROTECTED]> wrote:
> hi, there:
>
> I am trying to upgrade my kernel from 2.2.14 to 2.4, and I use make bzImage,
> when I modify the lilo.conf file as: image = /boot/vmlinux and run lilo I get
> the following error messages: vmlinux is too large.
>
> Can someone give me some suggestions?
>
I suspect you have copied the wrong file. do
file vmlinux
if you get ELF then its wrong,
try copying the arch/i386/boot/bzImage file instead.
karl
------------------------------
From: "???" <[EMAIL PROTECTED]>
Subject: Re: How SMP works in Linux
Date: Thu, 5 Oct 2000 10:56:28 +0900
"Johan Kullstam" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> "???" <[EMAIL PROTECTED]> writes:
>
> > Isn't there any FAQ?
> >
> > my question is:
> > Q1: What happens when one of two cpu dies in SMP kernel ?
>
> i would expect the machine to fall on its face. however, not having
> any CPUs die on me yet, i really have no idea. do you anticipate
> having your CPUs fail often?
No. I just wondered whether multi-CPU systems will be more stable or not
than single CPU systems.
>
> > Q2: When one CPU is processing kernel code, can the other CPU process
> > application code ?
>
> yes, of course.
>
> > Q3: TUX, a web server which runs in kernel mode, can be accelarated by
> > multi-CPU ?
>
> i don't know. what are you doing? why do you think you need this?
To acclerate the speed of my system. ^^
>
> --
> J o h a n K u l l s t a m
> [[EMAIL PROTECTED]]
> sysengr
------------------------------
From: =?ks_c_5601-1987?B?wMzBvrHH?= <[EMAIL PROTECTED]>
Subject: Re: How SMP works in Linux
Date: Thu, 5 Oct 2000 11:12:40 +0900
"Karl Heyes" <[EMAIL PROTECTED]> wrote in message
news:8rgbq6$rk3$[EMAIL PROTECTED]...
> In article <8rfa9a$rac$[EMAIL PROTECTED]>,
> "???" <[EMAIL PROTECTED]> wrote:
> > Isn't there any FAQ?
> >
> > my question is:
> > Q1: What happens when one of two cpu dies in SMP kernel ?
> >
>
> Does the hardwars support hot swap/recoverable CPUs?. Linux tries to
> provide what the majority require. This isn't a big issue for the
majority
> of linux installations out there, and support for it will appear in some
> form.
>
> > Q2: When one CPU is processing kernel code, can the other CPU process
> > application code ?
> >
>
> That was supported in 2.0. The scaleability issues that keep being
mentioned
> are when two processors are executing kernel code. 2.0 had a big kernel
lock
> for everything kernel related. 2.2 increased scability by providing
spinlocks
> enabling some kernel functions/facilities that are un-related to exucute
at the
> same time. 2.4 improves this further.
>
> The network stack in 2.4 is now SMP, I think the VFS is a 2.4 SMP thing as
well
wonderful! But what do you mean that network stack is SMP ?
Is it also possible that while one CPU is processing network I/O, another
CPU
processes DISK I/O ?
How about two CPUs share network job? (can I expect a linux router performs
much with multi-CPU?)
>
> > Q3: TUX, a web server which runs in kernel mode, can be accelarated by
> > multi-CPU ?
> >
>
> If its threaded/cloned, I don't know that much about the TUX
implementation,
> but I think it is.
Someone above said that it showed linear improvement.
I think it was possible that TUX does not only consist of kernel mode
modules
but also has application mode modules.
>
> karl.
>
>
>
------------------------------
From: "E-mu" <[EMAIL PROTECTED]>
Subject: Re: Sony Memory Stick
Date: 05 Oct 2000 05:16:26 GMT
I installed kernel 2.4.0-test7 as monolithic, and all my USB devices
including the sony memory stick were recogonized after mounting them. I
think my memory stick was assigned /dev/sdc3 don't remember that part?
"Reinald Kirchner" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi all,
> I'm using a Sony Z600 Notebook and a Sony DSC505V Digicam. The camera
> uses the socalled "Memory-Stick" as
> Flashcard, a convenient little chip. The Notebook has a Slot for reading
> that chip. Of course there are only WinX-drivers supplied. So what I'd
> like to know is:
>
> Is anybody hacking a driver for that device?
>
> If yes, I'd like to help/support a development like that, if not I would
> appreciate any advice where to start
> with, the only information available seems to be the PCI-Identification
> and I/O Adresses,
> that the WinX System-Info supplies
>
>
> Reinald
> --
> [EMAIL PROTECTED]
> fon +49 (0)241 503023
> fax +49 (0)241 503024
> www http://www.qbcl.de (not up yet...)
------------------------------
From: "E-mu" <[EMAIL PROTECTED]>
Subject: Red Hat 7.0 and Kernel 2.4.0-test9 question?
Date: 05 Oct 2000 05:23:42 GMT
Has anyone installed this kernel on Red hat version 7.0 yet? Any problems?
I had a problem with test8, I couldn't get the PASSWORD script after the
LOGIN script.
Finally is anyone having problems getting the graphical mode during the
install of red hat 7.0. I have a Dell Laptop Inspirion 7500, and had no
problems with Red Hat version 6.2 but with Red Hat 7.0, it will only
install in TEXT mode :(
Thanks
------------------------------
Date: Thu, 05 Oct 2000 08:44:58 +0200
From: Reinald Kirchner <[EMAIL PROTECTED]>
Subject: Re: Sony Memory Stick
Hi,
E-mu wrote:
>
> I installed kernel 2.4.0-test7 as monolithic, and all my USB devices
> including the sony memory stick were recogonized after mounting them. I
> think my memory stick was assigned /dev/sdc3 don't remember that part?
>
what kind of USB-Device you were using, an external
USB-Memory-Stick-reader or a Sony Camera
direct?
Reinald
--
[EMAIL PROTECTED]
fon +49 (0)241 503023
fax +49 (0)241 503024
www http://www.qbcl.de (not up yet...)
------------------------------
From: "Edward A. Hildum" <[EMAIL PROTECTED]>
Subject: Re: mmap problem in pci driver
Date: Thu, 05 Oct 2000 06:48:21 GMT
Gunnar Proppe wrote:
> I'm working on a linux device driver for the pci controller card for a
> haptic interface called the Phantom. Things were going along quite
Check out the demo device driver at
ftp://ftp.visi.com/users/grante/stuff/demomm.tar.gz
Grant Edwards pointed me to this code when I was working on a similar problem,
and it was quite helpful.
Also, if you probe the size of the PCI address space by writing 0xFFFFFFFF to the
base address register(s), be sure to put the original contents back, or you will
change the bus address at which your board is mapped.
HTH
Ted Hildum
------------------------------
From: Mark McDougall <[EMAIL PROTECTED]>
Subject: Re: PCI Documentation
Date: Thu, 05 Oct 2000 17:56:29 +1100
Arne Driescher wrote:
> For most drivers you are right. PCI is really painless.
> However, there is hardly any documentation for bus master devices.
> What exactly is the PCI-latency register usefull for? Am I free to
> set it to any value if can think of? What happens
> if a DMA transfer is interrupted by bus arbitration of an other devices.
> I haven't found any documentation about this problems.
> So, if anybody knows a good source for this .....
Your best source of info for these questions would be the PCI
specification (available from pcisig). Failing that, try any of the PCI
books available (Shanley or Solari spring to mind).
Your questions are also, in some cases, device-specific. These problems
are handled by the PCI chipset on your target hardware - and in most
cases will *not* be an issue to the driver developer. For that, you need
to read the databook of your PCI chipset.
Regards,
--
| Mark McDougall |
| Engineer |
| Virtual Logic Pty Ltd |
| http://www.vl.com.au |
------------------------------
** 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
******************************
