Linux-Development-Sys Digest #297, Volume #6 Sun, 17 Jan 99 23:13:55 EST
Contents:
Re: What does this traceroute output mean? (James Youngman)
Re: mmap problem (James Youngman)
Re: - deprecated - why? (Matthew Hannigan)
Re: Parallel C for Linux (Guido D)
Parallel C for Linux (Vitor Pedro Bonucci Pias)
Re: The new interface in Java - IS VERY IMPORTANT! (Matthew Hannigan)
Re: virtualizing i386-linux (Glen Turner)
Re: disheartened gnome developer (Per Bothner)
Adaptec or SCSI driver error recovery sucks (Phil Howard)
Re: SysV vs. BSD ps Re: - deprecated - why? (Matthew Hannigan)
Re: How to run Windows Applications on Linux ([EMAIL PROTECTED])
CTI Libraries ("Daniel Curry")
mounting filesystem on a char device ? ("Bjorn Wesen")
es1370: dma timed out? message from 2.2.0pre-7 ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Subject: Re: What does this traceroute output mean?
Date: 17 Jan 1999 20:49:27 +0000
[EMAIL PROTECTED] () writes:
> Hi,
> I have a very bad network performance between my Alpha and a Pentium.
> It basically works, but the 10Mbps link yields about 300KB/s from
> the Alpha to the Pentium but only 45KB/s vice versa.
> That could i have gotten by plip, too...
Doesn't sound too good. Something is -- you guessed it -- wrong.
> The only strange thing i observed besides the slow link is this:
> When i do a traceroute from alpha to pentium:
> traceroute to 192.168.1.2, 30 hops max, 40 byte packets
> 1 * * *
> 2 * * *
> this continues.
>From the manual page for traceroute:-
This program attempts to trace the route an IP packet would
follow to some internet host by launching UDP probe packets
with a small ttl (time to live) then listening for an ICMP
"time exceeded" reply from a gateway. We start our probes with
a ttl of one and increase by one until we get an ICMP "port
unreachable" (which means we got to "host") or hit a max (which
defaults to 30 hops & can be changed with the -m flag). Three
probes (change with -q flag) are sent at each ttl setting and a
line is printed showing the ttl, address of the gateway and
round trip time of each probe. If the probe answers come from
dif- ferent gateways, the address of each responding system
will be printed. If there is no response within a 5 sec.
timeout interval (changed with the -w flag), a "*" is printed
for that probe.
In other words, increasing the TTL is not helping get the packet to
its destination. In general if two hosts are on the same subnet,
traceroute is the wrong tool for the job.
> Can anybody please give me a hint, what i could check
> to repair this slow link?
See if you can spot the problem (from either end) using tcpdump. IMHO
running tcpdump on the Alpha end is more likely to be illuminating.
> Some more data:
> On pentium:
> eth0 Link encap:10Mbps Ethernet HWaddr 00:00:E8:58:33:3A
> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4853 errors:1 dropped:0 overruns:0
> TX packets:4897 errors:0 dropped:0 overruns:0
> Interrupt:10 Base address:0xf200
> This seems correct to me - doesn't it?
> The Pentium card is a 4Lan PCI (Realtek 8139 driver)
> The system is Linux 2.0.35
>
> On Alpha i have a DEC onboard net (Samsung UX2 board)
> and Linux 2.0.36
And what does ifconfig say on the Alpha?
Do you have a headware problem (e.g. 10baseT with cards configured for
duplex but only a non-duplex hub)?
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Subject: Re: mmap problem
Date: 17 Jan 1999 20:52:56 +0000
Marcin Szyllo <[EMAIL PROTECTED]> writes:
> I'm battling to understand why mmap (as in the attached example) does not
> allow me to mmap a block device - a partition... Why NOT?
[...]
> mmap: Operation not supported by device
Yep. That is indeed the reason.
$ grep mmap /usr/src/linux/drivers/block/*.c
/usr/src/linux/drivers/block/acsi.c: NULL, /* mmap */
/usr/src/linux/drivers/block/acsi_slm.c: NULL, /* mmap */
/usr/src/linux/drivers/block/amiflop.c: NULL, /* mmap */
/usr/src/linux/drivers/block/ataflop.c: NULL, /* mmap */
/usr/src/linux/drivers/block/floppy.c: NULL, /* mmap */
/usr/src/linux/drivers/block/hd.c: NULL, /* mmap */
/usr/src/linux/drivers/block/ide-tape.c: NULL, /* mmap */
/usr/src/linux/drivers/block/ide.c: NULL, /* mmap */
/usr/src/linux/drivers/block/loop.c: NULL, /* mmap */
/usr/src/linux/drivers/block/nbd.c: NULL, /* mmap */
/usr/src/linux/drivers/block/ps2esdi.c: NULL, /* mmap */
/usr/src/linux/drivers/block/rd.c: NULL, /* mmap */
/usr/src/linux/drivers/block/rd.c: NULL, /* mmap */
/usr/src/linux/drivers/block/swim3.c: NULL, /* mmap */
/usr/src/linux/drivers/block/xd.c: NULL, /* mmap */
/usr/src/linux/drivers/block/z2ram.c: NULL, /* mmap */
Does the light begin to dawn? :-)
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: [EMAIL PROTECTED] (Matthew Hannigan)
Subject: Re: - deprecated - why?
Date: 18 Jan 1999 01:48:46 GMT
In article <[EMAIL PROTECTED]>,
Tristan Wibberley <[EMAIL PROTECTED]> wrote:
>That's insane! All the options should have '-' prefixed.
Tell that to the authors of tar and BSD ps.
As it is, it gives us a very nice way to have compatibility.
--
-Matt
------------------------------
From: Guido D <[EMAIL PROTECTED]>
Subject: Re: Parallel C for Linux
Date: Mon, 18 Jan 1999 02:46:29 +0000
Vitor Pedro Bonucci Pias wrote:
> and i would like to know if there is a Parallel C
> compiler for Linux to explore the Parallelisme.
What parallelism do you mean? AFAIK, a task is connected
under SMP to one cpu at a time. Hence, you don't
get parallelism on code-level anyway which you would
need a compiler for. The rest is done with threading
and synchronization techniques - that's what the programmer
has to watch out for himself.
ciao
-- guido
------------------------------
From: Vitor Pedro Bonucci Pias <[EMAIL PROTECTED]>
Subject: Parallel C for Linux
Date: Mon, 18 Jan 1999 01:23:08 +0000
I have my system running Dual pentium II 450.
The system runing fine with kernel-2.2.0-pre7,
and i would like to know if there is a Parallel C
compiler for Linux to explore the Parallelisme.
Thanks
Pedro Pias
------------------------------
From: [EMAIL PROTECTED] (Matthew Hannigan)
Subject: Re: The new interface in Java - IS VERY IMPORTANT!
Date: 18 Jan 1999 02:07:07 GMT
On Sun, 17 Jan 1999 13:36:59 -0200, Marinho Brandão <[EMAIL PROTECTED]>
posted:
>************* READ THIS BECAUSE MOST IMPORTANT ********************
Are you tired from that horrible interface of X-Windows? Iam also. And
>have a big idea as solution!
>
>Before, I likely that know if is possible to work in graphic mode at
>Java. I not, send for me a message informing this. This is only a
>project.
> [ ... ]
Sounds like someone (you? :-) should implement Java's Swing directly
on top of svgalib or ggi.
This article might have got more response in the Java newsgroups,
cold.system is for kernel stuff mostly. (*)
--
-Matt
* yeah i know
------------------------------
Date: Mon, 18 Jan 1999 10:29:30 +1030
From: Glen Turner <[EMAIL PROTECTED]>
Subject: Re: virtualizing i386-linux
M Sweger wrote:
> But since Intel processors don't contain these special priveleged instructions,
> multiple versions of Linux or Linux/Windows combinations is probably
> impossible.
Actually they do. You don't need an instruction, you just need
the ability to trap on a priviledged instruction and to fake
the status registers showing the priviledge mode. With this,
a control program can present a number of fake CPUs.
I/O is more problematical. The IBM 3070 I/O model is that you download
a
channel program, which is then executed by the I/O device. This makes
it simple to write CPU code that emulates I/O devices. Similarly,
screen I/O is done through VTAM, an API that gives adequate opportunity
for fakery.
The microprocessor model is that I/O is done through special registers
in an address space -- this is more difficult to emulate without a
lot of overhead. It is probably simpler to have a "virtual disk"
device driver than bother with hardware emulation. Emulating
screen I/O is a total pain: in the worst case you can have a
processor trap per pixel update. Again, the best option is to
install a special device driver.
Having Linux run on a virtual 586 CPU would be pretty straight
forward. This would allow test and production version of
Linux to run concurently -- which could be useful for 2.2
testers :-)
What is wouldn't allow is Linux and Win95 to run concurrently.
There is a fair chance that you could get Linux and NT to
run concurrently at a respectable speed because there is more
opportunity to replace the NT device drivers and still have
a functioning OS. Because NT is a "real" OS, the OS authors
have to be more disciplined about accessing the hardware
than the 95 authors.
------------------------------
From: [EMAIL PROTECTED] (Per Bothner)
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.development.apps,comp.os.linux.x
Subject: Re: disheartened gnome developer
Date: 17 Jan 1999 18:57:30 -0800
In article <77omcl$f12$[EMAIL PROTECTED]>,
Nathan Myers <[EMAIL PROTECTED]> wrote:
>No, there's a fourth choice. Accept only contributions with copyrights
>assigned to you. Aladdin does this with Ghostscript, Cygnus with Egcs,
>and FSF with all its projects.
This is misleading. The *Egcs project* (not Cygnus) only accepts
contributions to Egcs/Gcc that as assigned to the *FSF*, not Cygnus.
(While Egcs is hosted at Cygnus, it is not owned by Cygnus.)
Some code that may be considered part of Egcs, but which is not
part of the compiler proper, may be as you describe. (I believe
Cygnus will keep the copyright the libstdc++, the C++ run-time
library, as well as the Java run-time library.)
--
--Per Bothner
Cygnus Solutions [EMAIL PROTECTED] http://www.cygnus.com/~bothner
------------------------------
From: [EMAIL PROTECTED] (Phil Howard)
Subject: Adaptec or SCSI driver error recovery sucks
Date: Mon, 18 Jan 1999 03:28:52 GMT
I've had this with both the drivers for 1542 and 2940. When there are
errors due to a device not responding the driver keeps trying to do some
kind of reset, over and over and over and over.
Here are the bad points about it:
1. It never gives up. I've let this run it's course for over 10 hours
once and when I came back, it was still trying to do the resets.
2. It locks up the whole machine during each period of trying to do
several resets. This lockup is for about 15 to 25 seconds at a
time. It's locked pretty hard as even a virtual console switch
won't happen. It would be worse in X as it would all be frozen
with no way to even see that it was frozen because of this.
3. The resets are totally ineffective, yet once I manage to do a soft
reboot (with "shutdown -r now") the steps taken by the BIOS seem to
recover things just fine (until the next time the device on the
SCSI bus decides to play dead).
Here are the questions:
1. How can I tell the driver "enough is enough ... give up ... I don't
care about the I/O request that is pending ... unblock the process
that requested it so it will die (I've already killed it)".
2. Why do these cycles of resets lock up the whole machine? Is the
driver code doing spin loops to time the resets? Why can't it just
use clock timed events and let other things keep on running?
3. Is this specific to Adaptec or would other SCSI controllers likely
have the same problem? Would a DPT controller work any better,
for example?
4. Is this fixed in 2.1.X and the coming 2.2?
The error occurs with this CDROM drive when certain bad CDs are in it.
It gets errors and apparently does bad things like losing interrupts.
But I've had tis occur on other devices prone to errors, too, such as
the Jaz drive.
Here's a sample of output from "dmesg":
--<CUT HERE>----<CUT HERE>----<CUT HERE>----<CUT HERE>----<CUT HERE>--
Memory: sized by int13 0e801h
Console: 8 point font, 400 scans
Console: colour VGA+ 80x50, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0x000faf50
pcibios_init : BIOS32 Service Directory entry at 0xfb3f0
pcibios_init : PCI BIOS revision 2.10 entry at 0xfb420
Probing PCI hardware.
Calibrating delay loop.. ok - 53.04 BogoMIPS
Memory: 127516k/131072k available (912k kernel code, 384k reserved, 2260k data)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: ICMP, UDP, TCP
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Intel Pentium with F0 0F bug - workaround enabled.
alias mapping IDT readonly ... ... done
Linux version 2.0.36 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Sat Jan 16
11:49:15 CST 1999
Starting kswapd v 1.4.2.2
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
lp1 at 0x0378, (polling)
PS/2 auxiliary pointing device detected -- driver installed.
Ramdisk driver initialized : 16 ramdisks of 4096K size
loop: registered device at major 7
ide: i82371 PIIX (Triton) on PCI bus 0 function 57
ide0: BM-DMA at 0x9000-0x9007
ide1: BM-DMA at 0x9008-0x900f
hda: WDC AC31600H, 1549MB w/128kB Cache, CHS=3148/16/63, DMA
hdb: WDC AC32500H, 2441MB w/128kB Cache, CHS=4960/16/63, DMA
hdc: WDC AC31000H, 1033MB w/128kB Cache, CHS=2100/16/63
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8
linear personality registered
raid0 personality registered
Configuring Adaptec (SCSI-ID 7) at IO:330, IRQ 10, DMA priority 5
ppa: Version 1.42
ppa: Probing port 03bc
ppa: Probing port 0278
scsi0 : Adaptec 1542
scsi : 1 host.
Vendor: IOMEGA Model: ZIP 100 Rev: J.03
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Vendor: PHILIPS Model: CDD2600 Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0
Vendor: SONY Model: SDT-9000 Rev: 0400
Type: Sequential-Access ANSI SCSI revision: 02
Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0
scsi : detected 1 SCSI tape 1 SCSI cdrom 1 SCSI disk total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 196608 [96 MB] [0.1 GB]
sda: Write Protect is off
tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED]
eth0: Digital DS21140 Tulip at 0x6000, 00 40 05 41 7a cc, IRQ 11.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
eth0: MII transceiver found at MDIO address 0, config 1000 status 782d.
eth0: Advertising 01e1 on PHY 0, previously advertising 01e1.
Partition check:
sda: sda4
hda: hda1 hda4 < hda5 hda6 hda7 hda8 >
hdb: hdb1
hdc: hdc1
JAVA Binary support v1.01 for Linux 1.3.98 (C)1996 Brian A. Lantz
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 128988k swap-space (priority -1)
eth0: Advertising 01e1 on PHY 0 (0).
Disc change detected.
VFS: Disk change detected on device 0b:00
Max size:249506 Log zone size:2048
First datazone:23 Root inode number 47104
ISO9660 Extensions: RRIP_1991A
scsi : aborting command due to timeout : pid 40, scsi0, channel 0, id 2, lun 0 Read
(6) 00 00 1f 01 00
scsi : aborting command due to timeout : pid 40, scsi0, channel 0, id 2, lun 0 Read
(6) 00 00 1f 01 00
SCSI host 0 abort (pid 40) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
Sent BUS DEVICE RESET to target 2
Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): scsi : aborting command due to timeout : pid 40, scsi0, channel
0, id 2, lun 0 Read (6) 00 00 1f 01 00
SCSI host 0 abort (pid 40) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
aha1542_out failed(2): Sent BUS DEVICE RESET to target 2
Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): scsi : aborting command due to timeout : pid 40, scsi0, channel
0, id 2, lun 0 Read (6) 00 00 1f 01 00
SCSI host 0 abort (pid 40) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
aha1542_out failed(2): Sent BUS DEVICE RESET to target 2
Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): scsi : aborting command due to timeout : pid 40, scsi0, channel
0, id 2, lun 0 Read (6) 00 00 1f 01 00
SCSI host 0 abort (pid 40) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
aha1542_out failed(2): Sent BUS DEVICE RESET to target 2
Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): scsi : aborting command due to timeout : pid 40, scsi0, channel
0, id 2, lun 0 Read (6) 00 00 1f 01 00
SCSI host 0 abort (pid 40) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
aha1542_out failed(2): Sent BUS DEVICE RESET to target 2
Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2): Sending DID_RESET for target 2
aha1542_out failed(2):
--<CUT HERE>----<CUT HERE>----<CUT HERE>----<CUT HERE>----<CUT HERE>--
--
-- *-----------------------------* Phil Howard KA9WGN * --
-- | Inturnet, Inc. | Director of Internet Services | --
-- | Business Internet Solutions | eng at intur.net | --
-- *-----------------------------* philh at intur.net * --
------------------------------
From: [EMAIL PROTECTED] (Matthew Hannigan)
Subject: Re: SysV vs. BSD ps Re: - deprecated - why?
Date: 18 Jan 1999 01:58:00 GMT
In article <77ljr0$5sm$[EMAIL PROTECTED]>, Marc Slemko <[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Timothy J. Lee)
>writes:
>
>>On Solaris, use /usr/ucb/ps to get BSD ps behavior.
>
>...and the sad part is, that /usr/ucb/ps is the _only_ way to do certain
>things on Solaris, ie. /usr/bin/ps can't do them.
Can you be more precise? What exactly can't you get?
>>AIX ps without the - takes BSD options; with the - takes SysV
>>options. The man page on Linux ps seems to imply that Linux
>>ps will take that approach in the future.
>
>That is such a stupid solution that I was completely dumbfounded the
>first time I read that bit of the man page. Talk about confusing people
>who have committed the sin of ever using any other Unix.
Eh? It's a nice solution. We should be happy its possible.
I mean you typed 'ps aux' when you listed processes under BSDish
Unixes didnt you? Surely you didn't waste precious time and bits
typing the redundant '-'? (I know how important lack of bloat
is to some people :-P )
>Even worse, Linux ps isn't even internally consistent about what is what:
I'm sure your patches and suggestions would be gratefully
received by the maintainer of procps.
--
-Matt
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
comp.os.linux.advocacy,comp.os.linux.development,comp.os.linux.development.apps
Subject: Re: How to run Windows Applications on Linux
Date: Mon, 18 Jan 1999 02:14:12 GMT
On 15 Jan 1999 02:17:24 GMT, [EMAIL PROTECTED] (Jim Richardson)
wrote:
>I for one have been unsuccessful in getting wine to do anything, I am sure
>that there is something, somewhere, I am doing wrong. I can't
>even get it to play tictactoe... Getting wine up to play the few games I
>use in windows, would enable me to delete windows entirely from the disk.
> (back to to the docs...)
Believe it or not i'm posting this reply from FreeAgent 32 running
under Linux :) With the last couple of wine releases I couldn't get
much of anything to run, not even calc.exe. With the latest release
I've even gotten Unreal to run with sound (albiet a little staticy)!
Check out the latest release, its beginning to shape up nicely!
Matt
------------------------------
From: "Daniel Curry" <[EMAIL PROTECTED]>
Subject: CTI Libraries
Date: Sun, 17 Jan 1999 21:44:45 -0600
My company is taking on a large CTI project to be developed. We are
currently looking for CTI related development tools and API's. Any relative
replies would be greatly appreciated
[EMAIL PROTECTED]
------------------------------
From: "Bjorn Wesen" <[EMAIL PROTECTED]>
Subject: mounting filesystem on a char device ?
Date: Mon, 18 Jan 1999 04:20:01 +0100
Is there a sane way to design a filesystem in Linux which can be mounted on
a char device ?
The major difference seems to be that a normal filesystem uses bread etc to
schedule block read/writes from the block device it's mounted on. bread in
turn uses ll_rw_block to perform the device I/O and the block device itself
processes its block requests.
A char device doesn't hook into the block read/write buffers, but rely on
normal inode + struct file communications with a process. This becomes a
problem for the filesystem, since it doesn't have a struct file with which
to perform access on the char device with.
The only workaround I can see is to combine the filesystem code with the
char device code itself (very unclean). But there must be some other way I
think.
The char device I want to mount on is a Flash memory device, and I want to
mount a flash file system we've made on it. I don't want it to be a block
device, because it's pointless to have pages and buffers in RAM mirroring
the memory-mapped flash - I just want the filesystem to read/write directly
into flash memory adresses. But I don't like the idea of putting the flash
I/O into the filesystem directly because I like the idea of a /dev/flash0 to
mount on.
Thank you for any suggestions,
/Bjorn
--
Please mail me at bjorn at sparta.lu.se and dont use the reply-to adress
since I've scrambled it to avoid junk mails.
------------------------------
From: [EMAIL PROTECTED]
Subject: es1370: dma timed out? message from 2.2.0pre-7
Date: Mon, 18 Jan 1999 03:46:48 GMT
Hi - I'm using Kernel 2.2.0pre-7 compiled under Debian Linux 2.0 on an Asus
P5A motherboard with an ALI Aladdin chipset and an AMD K6-2 300. I have the
following hardware installed:
Symbios 53c815 SCSI card.
ATI Xpert98 PCI card
Intel Etherpro 10/100 card at 10 megabit
SIIG SoundWave Pro PCI card with Ensonic AudioPCI 1370 chipset.
I've compiled the kernel support for this chipset. It seems to work fine, the
sox "play" command plays .au's and .wav's just fine. However, dmesg shows a
large number of "es1370: dma timed out?" messages in the log. Is there a
problem there?
Jeff McWilliams
[EMAIL PROTECTED]
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
** 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
******************************
