Linux-Development-Sys Digest #660, Volume #8 Sat, 21 Apr 01 08:13:12 EDT
Contents:
Re: 82559 Intel Network Chip Driver
2001 USENIX Annual Technical Conference (Becca Sibrack)
Re: type of hard disk ("Cameron Kerr")
lspcmcia
Thoughts on printing best practices?? recommendations?? (David Sims)
Re: Thoughts on printing best practices?? recommendations?? ("Cameron Kerr")
Re: Can Linux kernel ported on supercomputer (using 16 processor) ("Steven J.
Hathaway")
Re: howto properly access serial devices in Perl or C (Jonadab the Unsightly One)
Re: Can Linux kernel ported on supercomputer (using 16 processor) (Lew Pitcher)
Re: Can Linux kernel ported on supercomputer (using 16 processor) ([EMAIL PROTECTED])
Re: A Linux emulator for Linux, does this exist? (Jonadab the Unsightly One)
Re: lspcmcia (Trevor Hemsley)
Re: IO system throughput ([EMAIL PROTECTED])
Re: IO system throughput ([EMAIL PROTECTED])
Re: Can Linux kernel ported on supercomputer (using 16 processor)
([EMAIL PROTECTED])
Re: Can Linux kernel ported on supercomputer (using 16 processor)
([EMAIL PROTECTED])
Re: IO system throughput (Alexander Viro)
From: [EMAIL PROTECTED]
Subject: Re: 82559 Intel Network Chip Driver
Date: Fri, 20 Apr 2001 17:13:17 -0700
I'll add a little spice to the broth. I have a situation where eepro100.c
(the driver for the 82559) prints out a KERN_ALERT of "eepro100:
wait_for_cmd_done timeout!" and I go thru the source and find that
wait_for_cmd_timeout is waiting on the port it was called with, which is
always called with the argument ioaddr + SCBCmd where SMCCmd is 2 which
maps to the command register in the 82559. There is a status register in the
82559 (SBCStatus at 0), but it is *never* checked to see if the command unit
status is idle (meaning the command is executed). I further see that this
driver works *most* of the time and only fails when transferring a large
file across a 100baseT local LAN. This means, I think that the
non-functional wait_for_cmd_done is timing out (with its hard coded count
down from 1000) is loosing it with a fast processor and a fast network.
So..Gentlemen, my question is "Am I diagnosing the problem correctly with
the eepro100.c driver?".
--
From: Becca Sibrack [EMAIL PROTECTED]
Subject: 2001 USENIX Annual Technical Conference
Date: Fri, 20 Apr 2001 17:15:07 -0700
2001 USENIX Annual Technical Conference
June 25-30, 2001
Marriott Copley Place Hotel
Boston, Massachusetts, USA
http://www.usenix.org/events/usenix01/
==
REGISTER BY May 25, 2001 and Save up to $200!
==
The USENIX Annual Technical Conference has always been the gathering
place for like minds in the computer industry. USENIX ¹01 provides
tutorials that help master new and important skills and opportunities,
and is a place to meet peers and experts to share solutions to common
problems.
USENIX ¹01 offers professional-level tutorials, three technical tracks,
an AFS workshop, a GNOME developers conference, an information-laden
vendor exhibition, Birds-of-a-Feather Sessions, Work-in-Progress
Reports, parties and get-togethers for sys admins, programmers, systems
engineers and researchers.
DON¹T MISS OUT! Thirty tutorials in all, seventeen brand-new. Here¹s a
sampling:
-Network Programming with Perl
-Solaris Administration
-Building Linux Applications
-Large Heterogeneous Networks
-Practice Wireless IP Security
-Running Secure Web Servers
-Network Security
-Advanced Solaris Administration
-Unix Network Programming
-LDAP
Keynote address by Daniel D. Frye, Director of IBM Linux Technology
Center.
Invited Talks on WAP, IP Wireless Networking, Security Aspects of
Napster and Gnutella, Security For E-voting in Public Elections, Virtual
Machines, Online Privacy, Active Content and Secure DNS.
The USENIX Annual Technical Conference Exhibition features ~100
companies, products and services. For more information, please contact
Dana Geffner at [EMAIL PROTECTED]
=
--
From: "Cameron Kerr" [EMAIL PROTECTED]
Subject: Re: type of hard disk
Date: Sat, 21 Apr 2001 14:21:13 +1200
You know, its funny, in a lot of linux programs (in my
case libpcap, I think), a lot of this information is
found/set by reading/writing values in the /proc filesystem.
(fscanf is really useful for this, so is popen)
You will probably want to look in /proc/devices,
or check the existence of /proc/ide and /proc/scsi, but
beware that (on my system anyway) that /proc/scsi will
not exist until I load my zip drive module, even though I
have a CD-Writer, which uses the scsi-generic module.
(This may well be because the sg module is autoloading.)
--
Cameron Kerr