Re: [PATCH] eepro100 device name <-> pci bus/slot/func mapping

From: Rask Ingemann Lambertsen (
Date: Fri Jun 02 2000 - 14:28:10 EST

Den 01-Jun-00 03:33:20 skrev Jeff Garzik fĝlgende om "Re: [PATCH] eepro100 device name <-> pci bus/slot/func mapping":

>Well crap. All of the drivers use base_addr regardless of PIO or MMIO,
>and none use mem_start/end AFAICS. It should be no trouble to simply
>assign mem_start/end for reporting purposes and ignore them otherwise,
>but having 'base_addr' be a short here is a real PITA, since it doesn't
>reflect real-life usage.

>IMHO we should ditch mem_start/end, OR ditch base_addr...

   What about drivers that use both? Such as wd.c:

eth0 Link encap:Ethernet HWaddr 00:00:C0:8F:3A:23
          inet addr: Bcast: Mask:
          UP BROADCAST RUNNING MTU:1500 Metric:1
          RX packets:2033384 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35016 errors:0 dropped:0 overruns:0 carrier:0
          collisions:431 txqueuelen:100
          Interrupt:10 Base address:0x310 Memory:cc000-d0000


| Rask Ingemann Lambertsen | E-mail: |
| Please do NOT Cc: to me or the | WWW: |
| mailing list. I am on the list.| "ThrustMe" on XPilot, ARCnet and IRC |
| 3 kinds of people: Those who can count & those who can't. |

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:16 EST