RE: LAN91C and XSCALE

Tech-Archive recommends: Fix windows errors by optimizing your registry



Thank you Paul, Marco, and Dean!

With your excellent suggestions I am much closer, though still not
operational. It appears my main issue was I was using virtual addresses and
the driver was expecting physical ones. By changing the LAN91C111_Init.c
variable LAN91C111_ADDR to my physical address, 0x0c000000, I am no longer
getting the data abort.

However, I am still failing to complete the initilization process. My debug
logs seems to indicate that I am getting hung up attempting to verify the
adapter. It looks like this:

<=DriverEntry
=>MiniportInitialize
:SetupGPIOs
:Allocated TX buffer Successfully!
=>GetRegistrySettings
:BusType=0x01
:BusNumber=0x0
:New IRQ Value Found in Registry..overiding default
:New IOBase Address found in Registry...overiding default:
:BusNumber=0
:BusType=1
:IoBase=0x0c000300
:Interrupt=29
:Speed=254
:Duplex=254
<=GetRegistrySettings
:Interrupt Registered
:VirtualAlloc/Copy Succeed...
:Allocated Lookup Buffer Successfully
=>AdapterVerify
:A.IO= 0x 1d0300!
:Io= 0x 1d0300!
:BankSelect Constant= 0x3300!
:ERROR--Invalid Lan Chip (0x0) and Driver Combination.
<=AdapterVerify
:Adapter Failed to Verify!
<=Miniport Initialize
***NDIS*** Miniport Z

I am comfident that the chip ID will read as "9" because I do so in my
bootloader. So again I am left feeling like something is amis with the
address I am using, this time, the one loaded from the registry. Currently,
my Lan9001 Params look like this:

BusNumber=0
BusType=1
InterruptNumber=1D
IoBaseAddress=0C000300 ;Note I am adding 0x300 to my base address here.
;I do not in LAN91C111_INIT.C as it
appears to already
;account for it
Transceiver=1D
SysIntr=1D

If any of you have any other suggestions, I am all ears. It seems to me
that I must be very close if I can read the constant 0x3300 used to signify
the presence of the chip. Does anyone know what the A.IO and IO addresses
are / signify? In the mean time, I guess I need to try and determine what
exactly is the difference between the NdisRawWrite and ReadPorts, and the
ReadPort and WritePort implemented in my bootloader.

Thanks again to all for your help!

.



Relevant Pages

  • PATCH: docs for updated sk98 from vendor
    ... +Marvell Yukon/SysKonnect SK-98xx Gigabit Ethernet Adapter family driver for LINUX ... the driver is integrated in the linux kernel source. ... both link partners are allowed to send PAUSE frames ...
    (Linux-Kernel)
  • Re: how hot is my xeon?
    ... What does the 'sensors' command show? ... We are now going to do the I2C/SMBus adapter probings. ... (confidence 8, driver `eeprom') ... Found unknown chip with ID 0xf211 ...
    (Debian-User)
  • Re: [RFC][PATCH] SPI subsystem
    ... Are you expecting the adapter ... > driver to handle the fact that its transfer routine could be called ... > a message or another CS line which is really a GPO pin used for register ... For example a char LCD with SPI interface ...
    (Linux-Kernel)
  • Re: Ataptec SCSI card problem
    ... I tried to install this card debian 4.0, ubuntu 7.10, Fedora Core 8, ... Slackware 12 and I have always the same message from scsi card. ... what it looks like to me, the problem is to be found in the driver, rather ... SCSI adapter family, which means that they can be used in two modes, i.e. ...
    (comp.os.linux.hardware)
  • [PATCH 2/10] cxgb3 - main source file
    ... the Chelsio T3 network adapter driver. ... * This file is part of the Chelsio T3 Ethernet driver for Linux. ... * ones for any additional queues. ... +static int init_smt ...
    (Linux-Kernel)