From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] test6 merge
Date: Fri, 18 Aug 2000 12:49:44 +0100 [thread overview]
Message-ID: <20000818124944.A13870@linuxcare.com> (raw)
In-Reply-To: <20000815160510.C7757@vodka.thepuffingroup.com>; from matthew@wil.cx on Tue, Aug 15, 2000 at 04:05:10PM -0400
Hi,
The tulip driver doesn't initialise with the 2.4.0-test6 kernel
(for me, anyway).
The problem is that pci_resource_start (pdev, 0) in tulip_core.c
line 1046, returns 0x0001ff00, where it should (I think) return
0x0000ff00. I added a printk in drivers/pci/pci.c to show the
start/end values as it filled in the pci_dev->resource table,
and that showed start 0x0000ff00 end 0x0000ff7e. Don't know
where bit 16 gets added to start..
I just commented out the 'goto err_out_free_netdev' in tulip_core.c
and it now claims to mount nfs root, but cannot find init.
I had to comment out the unregistering of pdc console to
see that.
In 2.3.99pre8 tulip announced that the chip was at 0x1ff00 also,
but it didn't matter because the request_region call was different.
My 53c720 driver doesn't work any more either :-(
Richard
next prev parent reply other threads:[~2000-08-18 11:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 20:05 [parisc-linux] test6 merge Matthew Wilcox
2000-08-18 11:49 ` Richard Hirst [this message]
2000-08-18 12:08 ` Richard Hirst
2000-08-18 12:37 ` Matthew Wilcox
2000-08-18 13:45 ` Richard Hirst
2000-08-18 18:13 ` Matthew Wilcox
2000-08-18 22:07 ` Grant Grundler
2000-08-19 2:04 ` Matthew Wilcox
2000-08-19 15:24 ` Richard Hirst
2000-08-19 23:13 ` Matthew Wilcox
2000-08-20 18:20 ` Richard Hirst
2000-08-19 17:22 ` Richard Hirst
2000-08-21 17:01 ` David Huggins-Daines
2000-08-21 18:16 ` Richard Hirst
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=20000818124944.A13870@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.