From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andreas Henriksson <andreas@fjortis.info>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OOPS in read_cd... what to do?
Date: 28 Jan 2003 18:48:31 +0000 [thread overview]
Message-ID: <1043779710.24849.8.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030128125119.GA31590@foo>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
> 1. load module.
> #modprobe e2100
> e2100.c: Presently autoprobing (not recommended) for a single card.
> e2100.c:v1.01 7/21/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> 00 00 1D 0A 72 AB, IRQ 15, secandary media, memory @ 0xd0000
> (I can supply io=0x380 to get rid of the warning message, but there will
> be no real difference. I'm not really sure this is the correct value,
> but last time I tried this I did look at the jumpers and used the right
> value, thats when I noticed the oops. A weird thing btw. It didn't
> happen when there also was a ne2000-compatible isa-card used at the same
> time, then it just refused to send any traffic.)
>
> 2. configure and up the interface, then send traffic using the
> interface.
> (ping some.remote.ip ... pinging myself works fine, but I guess it's
> because the driver isn't involved there)
Try this
[-- Attachment #2: a1 --]
[-- Type: text/plain, Size: 1587 bytes --]
--- drivers/net/e2100.c~ 2003-01-28 18:38:21.000000000 +0000
+++ drivers/net/e2100.c 2003-01-28 18:38:21.000000000 +0000
@@ -77,7 +77,7 @@
{
/* This is a little weird: set the shared memory window by doing a
read. The low address bits specify the starting page. */
- readb(mem_base+start_page);
+ isa_readb(mem_base+start_page);
inb(port + E21_MEM_ENABLE);
outb(E21_MEM_ON, port + E21_MEM_ENABLE + E21_MEM_ON);
}
@@ -306,9 +306,9 @@
#ifdef notdef
/* Officially this is what we are doing, but the readl() is faster */
- memcpy_fromio(hdr, shared_mem, sizeof(struct e8390_pkt_hdr));
+ isa_memcpy_fromio(hdr, shared_mem, sizeof(struct e8390_pkt_hdr));
#else
- ((unsigned int*)hdr)[0] = readl(shared_mem);
+ ((unsigned int*)hdr)[0] = isa_readl(shared_mem);
#endif
/* Turn off memory access: we would need to reprogram the window anyway. */
@@ -328,7 +328,7 @@
mem_on(ioaddr, shared_mem, (ring_offset>>8));
/* Packet is always in one chunk -- we can copy + cksum. */
- eth_io_copy_and_sum(skb, dev->mem_start + (ring_offset & 0xff), count, 0);
+ isa_eth_io_copy_and_sum(skb, dev->mem_start + (ring_offset & 0xff), count, 0);
mem_off(ioaddr);
}
@@ -342,10 +342,10 @@
/* Set the shared memory window start by doing a read, with the low address
bits specifying the starting page. */
- readb(shared_mem + start_page);
+ isa_readb(shared_mem + start_page);
mem_on(ioaddr, shared_mem, start_page);
- memcpy_toio(shared_mem, buf, count);
+ isa_memcpy_toio(shared_mem, buf, count);
mem_off(ioaddr);
}
next prev parent reply other threads:[~2003-01-28 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 14:43 Mauricio Martinez
2003-01-27 16:23 ` Brian Gerst
2003-01-28 12:51 ` Andreas Henriksson
2003-01-28 18:48 ` Alan Cox [this message]
2003-01-28 19:52 ` Andreas Henriksson
2003-01-29 4:07 ` Cabletron E2100 (e2100.c) Oops Andreas Henriksson
2003-01-29 21:25 ` OOPS in read_cd... what to do? Faik Uygur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1043779710.24849.8.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andreas@fjortis.info \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®