Linux-Development-Sys Digest #758, Volume #7     Tue, 11 Apr 00 23:14:40 EDT

Contents:
  =?iso-8859-1?Q?R=E9cuperation?= d'1 PID en C (Julien Curto)
  =?iso-8859-1?Q?R=E9cuperation?= d'1 PID en C (Julien Curto)
  readline() (Philip)
  Re: Color faxing s/w? (Grant Edwards)
  Re: Random system hangs on Compaq P166/2.2.14 (Nix)
  Re: syscall during shrinking? (Bernd Strieder)
  Re: Color faxing s/w? ("Spehro Pefhany")
  Idea !!! ("Akbar Avliyaev")
  Re: Color faxing s/w? (M Sweger)
  Re: syscall during shrinking? (Mark Wooding)
  Re: Idea !!! (Alexander Viro)
  Re: Getting IP address of self in C? ("Akbar Avliyaev")
  Re: To core or not to core - You tell me (Dave Vandervies)
  Flash disk driver for Linux beginning programmer ("Long")
  Re: Multiple kernel versions on same system (Michael Kelly)
  Linux c programming with inline assembly ("Long")
  Re: Q: Serial Port Programming (Charles Blackburn)
  NCR53C8XX problems (Darin Smith)
  Re: A driver for Read/Writeable cdrom (TEAC CD-W54E) ? (bill davidsen)
  Kernel development ("Ivan  Van den Bossche")
  Re: To core or not to core - You tell me (Floyd Davidson)
  Spinlock trouble ("Rui Prior")
  Re: Linux c programming with inline assembly ("Arthur H. Gold")

----------------------------------------------------------------------------

From: Julien Curto <[EMAIL PROTECTED]>
Crossposted-To: 
fr.comp.lang.c,fr.comp.developpement,alt.comp.lang.learn.c-c++,comp.os.linux.development.apps
Subject: =?iso-8859-1?Q?R=E9cuperation?= d'1 PID en C
Date: Tue, 11 Apr 2000 17:20:12 -0700
Reply-To: [EMAIL PROTECTED]

Salut,

2 Questions :


* Comment est-ce que peut-on r�cuperer un PID en C.

* Comment peut-on savoir si un programme est d�j� activer en C. (ex. :
par recherche du PID)

D'avance merci

Merci de r�pondre � l'adresse indiqu�e.

M�ll#99

------------------------------

From: Julien Curto <[EMAIL PROTECTED]>
Crossposted-To: 
fr.comp.lang.c,fr.comp.developpement,alt.comp.lang.learn.c-c++,comp.os.linux.development.apps
Subject: =?iso-8859-1?Q?R=E9cuperation?= d'1 PID en C
Date: Tue, 11 Apr 2000 17:21:51 -0700
Reply-To: [EMAIL PROTECTED]

Salut,

2 Questions :


* Comment  peut-on r�cuperer un PID en C.

* Comment peut-on savoir si un programme est d�j� actif [=en cours
d'utilisation] en C. (ex. :
par recherche du PID)

D'avance merci

Merci de r�pondre � l'adresse indiqu�e.

M�ll#99

------------------------------

From: Philip <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: readline()
Date: Tue, 11 Apr 2000 16:37:23 GMT

pre information:
OS: linux
Compiler: gcc

I need a function that reads a defined amount of characters from the
keyboard (stdin?). When the user presses to much characters it should
stop reading these (do a beep or..). the function should also allow the
user to use the arrowkeys , delete key and backspace key (so like
reading something in textboxes like in windows/X/<form><input
type=text>/.. but then in the console -text mode-). I would like an ANSI
C method so I dislike using curses and/or readline in linux (using these
it would be possible with the standard functions in these libs).

So the function declaration would look like this

char *read_from_keyboard(int max_lenght)
{

 // My user can use the arrowkeys (<- and ->) to correct his string
 // My user can use the <del> and <backspace> keys to correct his 
 // string
 // My user can only enter "maxlength" characters
 // When echo-ing the chars my user typed I will not modify the 
 // ansi  draw where I am reading. (only the chars on the 
 // positions "0".."max_length" may be modified (ps. readline() does
 // this wrong afther the user used the arrow keys).
 //
}

Has somebody already made something like this (for linux) ? Or can
somebody point me the right direction ... before I will start writing
this myself I would like to know if there is maybe already something
like this...


-- 
Philip van Hoof                  _/_/_/                                 
aka freax @ undernet.org        _/_/  _/ _/_/   _/_/_/    _/_/   _/   _/
http://users.pandora.be/skatan _/_/     _/ _/  _/       _/  _/   _/  _/ 
mailto:[EMAIL PROTECTED]     _/_/_/_/   _/  _/ _/_/    _/_/_/_/   _/_/   
Linux: Because a PC is a     _/_/     _/     _/      _/    _/  _/  _/   
terrible thing to waste.    _/_/     _/      _/_/_/ _/    _/ _/     _/

------------------------------

From: grant@nowhere. (Grant Edwards)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Color faxing s/w?
Date: Tue, 11 Apr 2000 16:37:44 GMT

In article <8cve3a$3sk$[EMAIL PROTECTED]>, M Sweger wrote:

>   I'm wondering if it is possible to send "color" faxes to machines that
>act as fax machines/color printers and whether Linux can receive a color
>fax and display it as a color document? Perhaps using hylafax or something
>similar!

Last time I looked at the CCITT books (about 10 years ago), the
encoding used by Group 4 fax machines only supported black and
white (one bit per pixel).  Unless things have changed since
then, there is no way to represent color or grayscale info in a
fax data stream.

>Another question, is how does one send a Msoft Word, Postscript, and pdf
>document and when it is received after faxing, to convert it back to
>the format selected such as Msfot Word  ....etc.

One doesn't.

One e-mails the file to the recipient.  Faxes transmit
bitmapped images (B/W AFAIK).  Nothing more.  It is not a
file-transfer mechanism.

-- 
Grant Edwards                   grante             Yow!  Hey, LOOK!! A pair of
                                  at               SIZE 9 CAPRI PANTS!! They
                               visi.com            probably belong to SAMMY
                                                   DAVIS, JR.!!

------------------------------

From: Nix <$}xinix{[email protected]>
Crossposted-To: uk.comp.os.linux
Subject: Re: Random system hangs on Compaq P166/2.2.14
Date: 11 Apr 2000 13:20:27 +0100

Bill Hayles <[EMAIL PROTECTED]> writes:

> I'm running the same model (but with 32Mb and no ISDN card) as my server
> here using SuSE 6.3 and it's been up for weeks.  I doubt it's
> overheating - that's the way Compaq built the things, and there's a good
> air flow around the processor.  As an off-the-wall diagnosis, I'd
> suspect an iffy 64Mb RAM chip.

What I'm wondering is which component is at fault in one of the boxes
here.

It crashes every so often, and a memtest86 soon reveals the problem; if
you write 0xFFFFFFF8 to a RAM chip, you should get that back, not
0xFFFFFFFF. Every single-flipped-bit surrounded by 1-bits or 0-bits
flipped state.

What is mystifying is that this happens in *all* the banks from the
bottom of memory up to 0xA0000, and it happens even if I flip the chips,
or replace them with all-new chips --- but those chips in other boxes
are error-free.

So it's not the chips. Is it the cache? is there any way I can *tell* if
it's the processor-internal cache on this aging 586, or the L2 cache on
the motherboard? (If it's the latter, it'll probably mean replacing the
entire mobo to fix; if it's the former, I just need to find a P90
somewhere.)

Agh. I hate RAM faults.

-- 
`ndbm on Linux is an emulation, not the original. It comes in several
 flavours; `slightly broken', `moderately broken', and `totally and
 utterly broken'.' --- Nick Kew

------------------------------

From: Bernd Strieder <[EMAIL PROTECTED]>
Subject: Re: syscall during shrinking?
Date: Tue, 11 Apr 2000 19:25:54 +0200

Hi

Weiguang Shi wrote:
> 
> Thanks for your response.
> 
> It seems to me that "ed" will "truncate" a file to zero before writing the
> modified file (in memory?) to it.
> 

That's the probably the best way you can do it, without further
investigation, what has been changed indeed. If a file has changed in
the middle, then all past this position has to be moved accordingly,
this operation expectedly touches about half of the file. This means in
other words, that at most half of the file is reusable, without touching
it. If there are more changes, the reusable part will decrease. After
all the reasonable way of doing it, is not trying to be too clever. Just
kill the old file. But this would be too much, we just need a file with
the same name, so we don't kill it and create it again immediately after
that, but we throw all of its contents away, i.e., we truncate the file
to length zero.

So what you see is just the most efficient way of doing the job, or at
least a very good compromise in terms of code simplicity anf efficiency.

If you want to know the syscalls done in between use "strace". It has a
manpage... I'm sure you will see almost all of the existing apps doing
it the way we talk about.

Bernd.

------------------------------

From: "Spehro Pefhany" <[EMAIL PROTECTED]>
Subject: Re: Color faxing s/w?
Crossposted-To: comp.os.linux.development.apps
Date: Tue, 11 Apr 2000 17:37:30 GMT

In comp.os.linux.development.system Grant Edwards <grant@nowhere.> wrote:

> One e-mails the file to the recipient.  Faxes transmit
> bitmapped images (B/W AFAIK).  Nothing more.  It is not a
> file-transfer mechanism.

The Japanese have had color faxes for some time, and I'm vaguely aware of
an extension to the fax standard that allows Postscript faxes to be sent
in the native format, provided both ends agree on the feasibility after
the connection is made, but I think mailing the file as an attachment is
the best way these days (or just put it on an ftp site for the recipient
to pull it down from). 

Best regards, 

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Spehro Pefhany --"it's the network..."            "The Journey is the reward"
[EMAIL PROTECTED]             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com
Contributions invited->The AVR-gcc FAQ is at: http://www.BlueCollarLinux.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

------------------------------

From: "Akbar Avliyaev" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Idea !!!
Date: Tue, 11 Apr 2000 12:44:32 -0500

The main problem of Linux is hardware support.
On the other hand Windows supports most of hardware,
most vendors ship products with drivers for windows.
I'm thinking about making a way to use windows drivers in Linux.
Have anyone thought about it?
Is it reasonable/possible?




------------------------------

From: [EMAIL PROTECTED] (M Sweger)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Color faxing s/w?
Date: 11 Apr 2000 17:49:28 GMT
Reply-To: [EMAIL PROTECTED]


I just searched www.google.com for "color fax" and came up
with http://www.blackice.com   which says it has color fax s/w.
I guess I should have checked here first. :(
Moreover, HP makes a color fax/printer device HPOJ700.
There is supposed to be an HP T series color printer/fax out there too!

My guess is that one could send a bit mapped image for each color plane
in succession, then send a bit mapped image of color saturation and
color hue or brightness. Then when each of these distinct bit-mapped
images is received, they are put back together to represent the image
in color!

I assume that this is how they are doing it. As far as gif, jpeg etc.
one just saves the file off using standard utilities on the receiving
host.

Here is a color fax news article
http://www.internetnews.com/intl-news/print/0,1089,6_38831,00.html

The ITU-T30e is the international standard for sending and receiving
color fax.

Grant Edwards (grant@nowhere.) wrote:
: In article <8cve3a$3sk$[EMAIL PROTECTED]>, M Sweger wrote:

: >   I'm wondering if it is possible to send "color" faxes to machines that
: >act as fax machines/color printers and whether Linux can receive a color
: >fax and display it as a color document? Perhaps using hylafax or something
: >similar!

: Last time I looked at the CCITT books (about 10 years ago), the
: encoding used by Group 4 fax machines only supported black and
: white (one bit per pixel).  Unless things have changed since
: then, there is no way to represent color or grayscale info in a
: fax data stream.

: >Another question, is how does one send a Msoft Word, Postscript, and pdf
: >document and when it is received after faxing, to convert it back to
: >the format selected such as Msfot Word  ....etc.

: One doesn't.

: One e-mails the file to the recipient.  Faxes transmit
: bitmapped images (B/W AFAIK).  Nothing more.  It is not a
: file-transfer mechanism.

: -- 
: Grant Edwards                   grante             Yow!  Hey, LOOK!! A pair of
:                                   at               SIZE 9 CAPRI PANTS!! They
:                                visi.com            probably belong to SAMMY
:                                                    DAVIS, JR.!!

--
        Mike,
        [EMAIL PROTECTED]


------------------------------

From: [EMAIL PROTECTED] (Mark Wooding)
Subject: Re: syscall during shrinking?
Date: 11 Apr 2000 17:50:55 GMT

Weiguang Shi <[EMAIL PROTECTED]> wrote:

> It seems to me that "ed" will "truncate" a file to zero before writing the
> modified file (in memory?) to it.

It does that with the O_TRUNC option to `open'.

-- [mdw]

------------------------------

From: [EMAIL PROTECTED] (Alexander Viro)
Crossposted-To: comp.os.linux.hardware
Subject: Re: Idea !!!
Date: 11 Apr 2000 14:03:16 -0400

In article <8cvoar$svq$[EMAIL PROTECTED]>,
Akbar Avliyaev <[EMAIL PROTECTED]> wrote:
>The main problem of Linux is hardware support.
>On the other hand Windows supports most of hardware,
>most vendors ship products with drivers for windows.
>I'm thinking about making a way to use windows drivers in Linux.
        What an original idea. It's certainly impossible that DN would
keep a dozen of archived flamew^Wthreads exactly about that, isn't it?

>Have anyone thought about it?
        Have you thought about checking?

>Is it reasonable/possible?
        Definitely takes more efforts than a search on Dejanews.

-- 
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid.  Get yourself a better computer" - Dilbert.

------------------------------

From: "Akbar Avliyaev" <[EMAIL PROTECTED]>
Subject: Re: Getting IP address of self in C?
Date: Tue, 11 Apr 2000 13:16:59 -0500

create a socket, and read ip from socket structure

[EMAIL PROTECTED] wrote in message ...
>[EMAIL PROTECTED] (Pete Cavender) writes:
>
>Hi
>>
>> How can I get my IP address from C?  I used to use gethostid() but with
>> newer kernels that doesn't seem to work...I can run ifconfig and dig
>> through the text and look for it, bu there has to be a C way...  Thanks!
>
>may be http://ivs.cs.uni-magdeburg.de/~elkner/tilo/if2ip.c helps ...
>
>Have fun,
>jens.
>--
>+---[ Jens
Elkner ]--------------------------------------------------------+
>| Walther-Rathenau-Str. 58                 [EMAIL PROTECTED]
|
>| 39104 Magdeburg   GERMANY              http://www.linofee.org/
|
>+--------------------------------------------------------------------------
+



------------------------------

From: [EMAIL PROTECTED] (Dave Vandervies)
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: 11 Apr 2000 17:54:49 GMT

In article <[EMAIL PROTECTED]>, Dima Volodin  <[EMAIL PROTECTED]> wrote:
>Floyd Davidson wrote:
>
>> The macro NULL must be a null pointer constant, which is either
>> an integral constant expression of value 0 or such an expression
>> cast to a void*.  (In other words, it has an all 0 bit pattern.)
>
>There's no requirement that ((void*)0) produced all 0 bit pattern.

That's irrelevant until run time, though; it _is_ required that (void *)0
(or any pointer to which it has been assigned) compares equal to 0, so
what it produces at run time is irrelevant to the programmer.

-- 
Dave Vandervies
[EMAIL PROTECTED]

I have no mouth, and I must scream.

------------------------------

From: "Long" <[EMAIL PROTECTED]>
Subject: Flash disk driver for Linux beginning programmer
Date: Tue, 11 Apr 2000 11:22:13 -0700

Anyone, please helllllllp:

I got an error trying to run "insmod flashfx.o" after rebuilding the driver:
FLASHFX: Cout not get major 31
./flashfx.o: init_module: Device or resource busy

I had to reboot linux in order to load the driver again.  Is there any I can
do to load the new rebuilt driver w/o having to reboot the machine
everytime?

flashfx.o is the name of the driver whose major number is 31.

Long



------------------------------

From: [EMAIL PROTECTED] (Michael Kelly)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Multiple kernel versions on same system
Date: 11 Apr 2000 18:30:50 GMT

In article <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED] (William Burrow) writes:
> On 7 Apr 2000 00:19:33 -0500,
> Paul Kimoto <[EMAIL PROTECTED]> wrote:

[snip]
 
> I have not seen it to date, but I keep multiple kernels and system maps
> in /boot, and have a boot script set the correct system map file for the
> currently running kernel.  This is all fairly easy to implement:
> 
> ln -sf /boot/System.map-`uname --release` /boot/System.map
> ln -sf /usr/src/linux-`uname --release` /usr/src/linux
> 
> 

Hi Paul.  That's useful info.  I was wondering also if you know
what governs the creation of module-info files.  It's probably
not all that important but I am booting multiple kernels and
it would be nice and neat if I could get all the symbols to
map to the correct versions.  I'll use the ln script you suggest
above for the System.map file but when I compiled modules for
the 2.3.4 kernel I got no module-info symbols.  Is there a
define I can pass to the Makefile or is it really irrelevant?

TIA

-- 

Mike
--
"I don't want to belong to any club that would have *me* as a member!"
             -- Groucho Marx


------------------------------

From: "Long" <[EMAIL PROTECTED]>
Subject: Linux c programming with inline assembly
Date: Tue, 11 Apr 2000 11:49:57 -0700

Hello,

Does anyone know how (syntax) to define c-macros (#define MACRO(par1,
par2,...) (function(par1, par2)) that can contains inline assembly code.
Please show the links or books I could find.  Thanks in advance.

Long



------------------------------

From: [EMAIL PROTECTED] (Charles Blackburn)
Subject: Re: Q: Serial Port Programming
Date: Tue, 11 Apr 2000 19:25:19 +0100
Reply-To: [EMAIL PROTECTED]

On Mon, 10 Apr 2000 13:39:36 -0400, Ron wrote:
>The PC UART hardware is not capable of receiving this type of
>synchronous serial data.  The manufacturer of your device probably has
>an interface for it.  Otherwise you'd need to make your own interface in
>hardware.  It is possible (if the baud rate is not too fast) to develop
>your own interface in software.  You would need to develop an
>interrupt-driven device driver using the parallel port to handle each
>bit as it comes in.  It can be done--but it is quite involved!

agreed, but he could also go for a sync <-> async converter.
-- 
Charles Blackburn -=- Remove NOSPAM to email a reply.
Summerfield Technology Limited - SuSE Linux Reseller & Birmingham L.U.G sponsor
[EMAIL PROTECTED] 
[EMAIL PROTECTED]
  7:22pm  up 2 days, 33 min,  1 user,  load average: 0.00, 0.00, 0.00

------------------------------

From: Darin Smith <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.bsd.freebsd,comp.unix.bsd.netbsd
Subject: NCR53C8XX problems
Date: Tue, 11 Apr 2000 14:28:11 -0500

Howdy everybody,

Sorry to cross-post & risk starting some kind of holy war here, but I'm
stuck.

I'm running into a lot of difficulties getting an NCR53C825A (SCSI
controller) to work with Linux kernel 2.2.14 on a custom PowerPC (750)
based board.  The driver originates from 386bsd and FreeBSD and is
ported to NetBSD and Linux...thus the choice of groups to xpost to,
hoping someone can shed some light on the matter.

We currently have it running nicely on a Linux 2.0.30 based system,
using version 1.18h of the driver.  Sometime between Linux 2.0.27 and
2.0.38 the driver changed enough that it wouldn't work for us.  I don't
know the specifics because I wasn't here at the time.
Now, we are in an effort to get to the 2.2.x series of kernels (for
various reasons).

At any rate, as I understand it, the messages they were seeing back then
(going from 2.0.29 or 30 to 2.0.38) were the same as I'm seeing now:

ncr53c8xx: at PCI bus 0, device 12, function 0
ncr53c8xx: PCI_CACHE_LINE_SIZE not set, features based on CACHE LINE
SIZE not us
ed.
ncr53c8xx: 53c825a detected 
ncr53c825a-0: rev=0x14, base=0x1ffeb00, io_port=0x1000000, irq=11
ncr53c825a-0: ID 7, Fast-10, Parity Checking
ncr53c825a-0: on-chip RAM at 0x1fff000
CACHE TEST FAILED: ncr wrote 2, host read 0.
CACHE TEST FAILED: ncr wrote 2, read back 0.
CACHE INCORRECTLY CONFIGURED.
ncr53c825a-0: detaching...
scsi : 0 hosts.
scsi : detected total.


Using 2.0.30 with v1.18h of the driver, we get this output:
ncr53c8xx:
setup=disc:y,specf:y,ultra:y,tags:0,sync:255,burst:7,wide:y,diff:0
ncr53c8xx:
setup=mpar:y,spar:y,fsn=n,verb:1,debug:0x0,led:n,settle:2,irqm:0
ncr53c8xx: at PCI bus 0, device 12, function 0
IRQ from table (900ffbc8) - dev: 12, val: 1
SCSI: Mapped base moved from 3AFFEB00 to 01ffeb00
ncr53c8xx: unit=0 chip=825 rev=0x0 base=0x1ffeb00, io_port=0x1000000,
irq=11
Rewrite script 904de824..904df6e8 - 90b150c0
Rewrite script 904df6e8..904e0570 - 90b15f84
ncr53c825-0: requesting shared irq 11 (dev_id=0x90b14080)
ncr53c825-0: resetting, command processing suspended for 2 seconds
ncr53c825-0: restart (scsi reset).
ncr53c825-0: initial value of dmode/dcntl/ctest3/4/5 = (hex)
c0/00/00/00/00
ncr53c825-0: final value of dmode/dcntl/ctest3/4/5 = (hex)
ca/00/00/00/00
scsi0 : ncr53c8xx - revision 1.18h
scsi : 1 host.
Started kswapd v 1.4.2.2 
ncr53c825-0: command processing resumed
  Vendor: WDIGTL    Model: WDE4550           Rev: 1.50
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi : detected 1 SCSI disk total.
ncr53c825-0-<0,0>: WIDE SCSI (16 bit) enabled.
ncr53c825-0-<0,0>: asynchronous.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8891602 [4341 MB] [4.3
GB]


**********************

One option is to play with the arguments (maybe use safe:y)...but I
unfortunately don't have the keyboard to play with at boot right now,
and I'm doing a network boot.  In any case, it would be nice to know
what is causing this...

So, after spending some time going through the sources I think that:
1) It is not an endianness issue, as only 2 of the cache tests failed
and the endianness code from Cort looks fine.
2) The SCRIPTS (tm) code changed significantly between these versions of
the driver.
3) Might be an io-mapping issue (this is using NCR_IOMAPPED), but it
finds the proper address, so I kind of doubt that too.

It looks like the code goes and stores a 1 (host_wr) in np->ncr_cache,
writes a 2 (ncr_wr) to the NCR's nc_temp register, then runs some kind
of "snooptest" script.  Then it reads back the value in np->ncr_cache as
host_rd. It copies the value from the register nc_scratcha to ncr_rd and
copies the value from register nc_temp to ncr_bk.

Then it performs the following tests:
compare host_wr & ncr_rd...if !=, error.  (We get no error here)
compare host_rd & ncr_wr...if !=, error.  (We get an error here:
ncr_wr=2, host_rd=0)
compare ncr_bk & ncr_wr...if !=, error.  (We get an error here:
ncr_wr=2, ncr_bk=0)

So I must conclude that it is expected that the "snooptest" will store
the value from np->ncr_cache (host_wr) in the nc_scratcha register, and
will store the value from nc_temp in np->ncr_cache.  What happens to
nc_temp?  Obviously, it is getting slam-dunked by something...we wrote a
2, did the script thing, and read back a 0.

There is some strangeness here.  Also the complaint about
PCI_CACHE_LINE_SIZE not being set.  It seems that the old driver didn't
have that functionality.

Looks like this is coming from:
        /*
         * Fix up for recent chips that support CACHE LINE SIZE.
         * If PCI config space is not OK, remove features that shall not
be 
         * used by the chip. No need to trigger possible chip bugs.
         */

        if ((chip->features & FE_CLSE) && cache_line_size == 0) {
                chip->features &= ~FE_CACHE_SET;
                printk("ncr53c8xx: PCI_CACHE_LINE_SIZE not set, features
based o
n CACHE LINE SIZE not used.\n");
        }

I've just now undef'ed the SCSI_NCR_PCI_FIX_UP_SUPPORT in
sym53c8xx_defs.h to keep from even reaching that code but haven't gotten
the opportunity to try it out yet.  Has anyone else seen this & have any
tips on what it might be (and how to get around it)?

The hardware is mostly PReP compliant:  RTC moved to Watchdog timer
location because they are on the same chip, no keyboard controller, no
VGA, serial console only.  I've worked around most of these issues using
equivalent "creative programming" to what was done to get 2.0.x kernels
running.  Our ethernet driver seems to work, as well as a driver written
in-house, it finds the serial ports fine, and the PCI io-mappings seem
correct.  IRQ's look good too.

Any help is greatly appreciated!

--Darin

------------------------------

From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: A driver for Read/Writeable cdrom (TEAC CD-W54E) ?
Date: 11 Apr 2000 20:29:48 GMT


In article <[EMAIL PROTECTED]>, Darius Samani  <[EMAIL PROTECTED]> wrote:
| Would anyone know if there are any drivers for
| Teac Read/Writeable cdrom (model CD-W54E) ? If so,
| could you point me to where they're located ?

  Is this ATAPI or SCSI, and what happens when you use the appropriate
driver for the bus type? Most modern writers are either mmc or SCSI and
work fine with the existing standard kernel drivers.

  You will want to load the standard SCSI generic (sg) driver, and for
most CD burning software the ide-scsi driver if the drive is ATAPI.

  These drivers are part of the standard kernel source.

--
bill davidsen <[EMAIL PROTECTED]>  CTO, TMR Associates, Inc
  "Doing interesting things with little computers since 1979"(tm)
The hardest test of maturity is knowing the difference between
resisting temptation and missing a once-in-a-lifetime opportunity.

------------------------------

Reply-To: "Ivan  Van den Bossche" <[EMAIL PROTECTED]>
From: "Ivan  Van den Bossche" <[EMAIL PROTECTED]>
Subject: Kernel development
Date: Tue, 11 Apr 2000 20:47:54 GMT

Hello everybody,

Where can I find the right documentation on the WEB to get started with
Kernel development?  What do I need to know?

Thanks
Ivan

[EMAIL PROTECTED]




------------------------------

From: Floyd Davidson <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.c,comp.unix.solaris,comp.lang.c++,comp.unix.programmer
Subject: Re: To core or not to core - You tell me
Date: 11 Apr 2000 11:52:01 -0800

Dima Volodin <[EMAIL PROTECTED]> wrote:
>Floyd Davidson wrote:
>
>> The macro NULL must be a null pointer constant, which is either
>> an integral constant expression of value 0 or such an expression
>> cast to a void*.  (In other words, it has an all 0 bit pattern.)
>
>There's no requirement that ((void*)0) produced all 0 bit pattern.

Yes there is.  It is a *null pointer constant* with a value of 0,
and will not be _converted_ to a null pointer unless it is compared or
assigned to a pointer type.

The *null pointer* is what is not required to be an all 0 bit pattern.

-- 
Floyd L. Davidson                          [EMAIL PROTECTED]
Ukpeagvik (Barrow, Alaska)

------------------------------

From: "Rui Prior" <[EMAIL PROTECTED]>
Subject: Spinlock trouble
Date: Tue, 4 Apr 2000 11:48:44 +0100

Hello.

I'm changing an ATM device driver to make it SMP friendly, but spinlock
freezes are making me crazy. I can't really undestand what's going wrong.
I made the following experiments:

UP box with non-SMP kernel: Works just fine.
UP box with non-SMP kernel but with SPINLOCK_DEBUG set to 2: Works just
fine, never complains about anything.
UP box with SMP kernel: Freezes with no messages at all.
SMP box with SMP kernel: Freezes with no messages, except for the NMI
watchdog detecting a lockup.

I always use spin_lock_irqsave() to acquire the locks (three kinds of them,
always acquired in the same order - I hope...), and spin_unlock_irqrestore()
to release them.

Given these symptoms, can anyone give me a hint about the problem?
Any help would be greatly appreciated, as it may well save me from going to
the asylum :-)

Rui Prior




------------------------------

Date: Tue, 11 Apr 2000 16:41:45 -0500
From: "Arthur H. Gold" <[EMAIL PROTECTED]>
Subject: Re: Linux c programming with inline assembly

Long wrote:
> 
> Hello,
> 
> Does anyone know how (syntax) to define c-macros (#define MACRO(par1,
> par2,...) (function(par1, par2)) that can contains inline assembly code.
> Please show the links or books I could find.  Thanks in advance.
> 
> Long
The simplest thing would be to look through the glibc sources...and "do
what they do".

HTH,
--ag
-- 
Artie Gold, Austin, TX  (finger the cs.utexas.edu account for more info)
mailto:[EMAIL PROTECTED] or mailto:[EMAIL PROTECTED]
--
A: Look for a lawyer who speaks Aramaic...about trademark infringement.

------------------------------


** 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
******************************

Reply via email to