From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Tulip driver
Date: Sun, 6 Feb 2000 02:46:51 +0100 [thread overview]
Message-ID: <20000206024651.B3143@alpha.franken.de> (raw)
Hi,
I've checked in a new tulip driver, which works for me on the onbard tulip
of the A180. I've tried to use Donald's latest driver (0.91x), but this
driver needs some pci infrastructure, which isn't available in our 2.3 tree,
yet. So I ported the 2.2.14 driver and added cache flushes. Before
that I've added the cache flushes to tulip 0.91x, so whenever we update
our tree, I should have an updated tulip very quick.
The 2.2.14 tulip didn't like the SROM provided by the onboard tulip,
because it didn't provide information about the attached phy (and the
default media is in the wrong endian, but that isn't a big problem).
I fixed that by just not allocating a media table, which works in
my case. It's possible that this may break later. The SROMs of the
tulips behind the card mode dino are looking stranger, they seem
to be from a time before Digital released a sane SROM documentation
and might confuse the driver as well. But since the machine hangs,
when the driver tries to probe the second tulip on the card, this
isn't an issue, yet.
I'm now looking into getting nfs root working.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next reply other threads:[~2000-02-06 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-06 1:46 Thomas Bogendoerfer [this message]
2000-02-06 16:54 ` [parisc-linux] Tulip driver Grant Grundler
2000-02-07 0:32 ` Thomas Bogendoerfer
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 23:06 [parisc-linux] tulip driver Sonny Cook
2001-12-13 0:36 ` Grant Grundler
2001-12-13 7:22 ` Sonny Cook
2001-12-13 7:47 ` Matthew Wilcox
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=20000206024651.B3143@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox