All,
After much testing and abuse the latest version of the ibm isa/pcmcia token
ring drivers are finally available for inclusion in the 2.2.x kernel and
pcmcia_cs packages.
Attached are two files, ibmtr-2.2.18p17.patch.gz which contains the patch
for ibmtr.[ch] for the kernel, this patch is
All,
After much testing and abuse the latest version of the ibm isa/pcmcia token
ring drivers are finally available for inclusion in the 2.2.x kernel and
pcmcia_cs packages.
Attached are two files, ibmtr-2.2.18p17.patch.gz which contains the patch
for ibmtr.[ch] for the kernel, this patch is
> Doesn't work for all devices. Also since base_addr is truncated to
> 16-bits when passed to ifconfig, this gets even nastier for userspace.
You do the best you can with what's available :)
> ...and noone but the driver can trust this information to be pointing to
> an up-to-date struct
Hi Andrew,
Take a look at the olympic driver (drivers/net/tokenring/olympic.c)
function olympic_proc_info. This is called from a read into the proc
filesystem. When we get the read we want to print out details on
all the olympic devices in the system so we have to scan the
pci tree and find a
>> hi all,
>> given struct netdevice for any pci network device, is there any way to
get
>> corresponding
>> "struct pci_dev".
> No.
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice. (Or do a similar match search
on
hi all,
given struct netdevice for any pci network device, is there any way to
get
corresponding
"struct pci_dev".
No.
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice. (Or do a similar match search
on base_addr)
Hi Andrew,
Take a look at the olympic driver (drivers/net/tokenring/olympic.c)
function olympic_proc_info. This is called from a read into the proc
filesystem. When we get the read we want to print out details on
all the olympic devices in the system so we have to scan the
pci tree and find a
Doesn't work for all devices. Also since base_addr is truncated to
16-bits when passed to ifconfig, this gets even nastier for userspace.
You do the best you can with what's available :)
...and noone but the driver can trust this information to be pointing to
an up-to-date struct
8 matches
Mail list logo
