Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael Ang <mang@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] progress on tulip driver
Date: Tue, 25 Jan 2000 14:01:55 -0500	[thread overview]
Message-ID: <388DF323.7B9EF164@linuxcare.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

I just committed some changes to the tulip driver that should let you
read a MAC on the bultin tulip on the A180 -- please let me know if this
doesn't work on other machines.  You need to apply the attached patch
since check_region doesn't understand our fudged PCI I/O addresses.  You
can type "in la" from the boot menu to get the MAC of the builtin lan
adapter.

I suspect that the tulip code is still broken on pa20 boxen because of
the fudged addresses.

Thanks to Grant for fixing the Dino code that I was having problems
with.

	- Mike.

[-- Attachment #2: tulip.diff --]
[-- Type: text/plain, Size: 655 bytes --]

Index: tulip.c
===================================================================
RCS file: /home/cvs/parisc/linux-2.3/drivers/net/tulip.c,v
retrieving revision 1.3
diff -u -r1.3 tulip.c
--- tulip.c	2000/01/25 19:48:06	1.3
+++ tulip.c	2000/01/25 19:48:52
@@ -513,7 +513,10 @@
 
 		/* Avoid already found cards */
 		if (check_region(pci_ioaddr, tulip_tbl[chip_idx].io_size))
-			continue;
+/*XXXmang			continue; */
+			printk("tulip_probe: warning, region 0x%x size 0x%x not available, continuing anyway\n",
+				   pci_ioaddr, tulip_tbl[chip_idx].io_size);
+		
 
 		pcibios_read_config_word(pci_bus, pci_device_fn,
 								 PCI_COMMAND, &pci_command);

                 reply	other threads:[~2000-01-25 20:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=388DF323.7B9EF164@linuxcare.com \
    --to=mang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox