summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorwpaul <wpaul@FreeBSD.org>2000-11-16 19:56:09 +0000
committerwpaul <wpaul@FreeBSD.org>2000-11-16 19:56:09 +0000
commit7d8c4474eabedfa44c889c93748c3dbd3de0b9e2 (patch)
tree40f1e0bdb0ea1b5a3549ca34373604149d3c4edb /UPDATING
parentb593b76bee29d3f6951bb3facde86725c3061964 (diff)
downloadFreeBSD-src-7d8c4474eabedfa44c889c93748c3dbd3de0b9e2.zip
FreeBSD-src-7d8c4474eabedfa44c889c93748c3dbd3de0b9e2.tar.gz
When checking the device code in the probe routine, leave the chip in
16-bit mode. Technically, pcn_probe() is destructive because once the chip goes into 32-bit mode, the only way to get it out again is a hardware reset. And once the device is in 32-bit mode, the lnc driver won't be able to talk to it. So if pcn_probe() is called before the lnc probe routine, and pcn_probe() rejects the chip as one it doesn't support, the lnc driver will be SOL. I don't like this. I think it's a design flaw that you can't switch the chip out of 32-bit mode once it's selected. The only 'right' solution is for the pcn driver to support all of the PCI devices in 32-bit mode, however I don't have samples of all the PCnet series cards for testing.
Diffstat (limited to 'UPDATING')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud