Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Alex deVries <adevries@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] ethernet driver...
Date: Mon, 04 Oct 1999 02:24:08 -0400	[thread overview]
Message-ID: <37F84808.D8E48C4C@thepuffingroup.com> (raw)


I've cleaned up dino.c sufficiently that tulips are detected, although
somewhat broken still:

  The PCI BIOS has not enabled this device!  Updating PCI command
1011->1015.   
tulip.c:v0.89H 5/23/98
becker@cesdis.gsfc.nasa.gov                              
eth0: Digital DS21140 Tulip at 0x82223800, EEPROM not present, 00 4c 69
6e 75 7.
eth0: Old style EEPROM -- no media selection
information.                       
  PCI latency timer (CFLT) is unreasonably low at 0.  Setting to 64
clocks.     
  The PCI BIOS has not enabled this device!  Updating PCI command
1011->1015.   
eth1: Digital DS21142/3 Tulip at 0xff00, EEPROM not present, 00 4c 69 6e
75 7a,.
eth1: Old style EEPROM -- no media selection
information.                       
  PCI latency timer (CFLT) is unreasonably low at 0.  Setting to 64
clocks.     

Two things to note here:
- I'm not running pcibios_fixup (or whatever) yet, haven't figured out
what this is supposed to do
- in tulip.c, there's really only one addition having to do with EEPROM
detection, and I think I've messed that up.  The MACs shown are
incorrect.

We're getting to the point where most PCI devices will start to be
detected.

- Alex
-- 
Alex deVries
Vice President of Engineering
The Puffin Group

             reply	other threads:[~1999-10-04  6:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04  6:24 Alex deVries [this message]
1999-10-04 11:37 ` [parisc-linux] ethernet driver Alan Cox

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=37F84808.D8E48C4C@thepuffingroup.com \
    --to=adevries@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox