Re: How to Disable Ethernet

Thanks Paul,

I dont mind living with it but I dont know how to make my
driver behave correctly with it. It receives constant
interrupts which are not intended for it (the interrupt and
mask do not overlap). How should I handle this? I have
been struggling with this for 2 weeks. I am porting the
91C96 driver to winCE 4.2 and the OS just gets stuck
calling this ISR over & over. The interrupt is disabled in
OEMInterruptHandler. It is reenabled/cleared at the end of
the interruptHandler per what I have read in the mesage
archives. In addition, I verify the hardware interrupt is
completely cleared (no pending hardware interrupt) prior to
leaving the interrupt handler. I also changed the SYSINTR
value to a unique value (it no longer uses SYSINT_SMSC).

Any help would be greatly appreciated. I can not find any
formal documentation on this anywhere.

-Jeff


>-----Original Message-----
>Disable it? Program the OS into flash or wherever it will
be permanently
>stored and remove the KILT component from the OS. If you
have to use
>Ethernet to download, you're going to have to live with
sharing the port...
>
>Paul T.
>
>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
>news:126501c55262$caea6a00$a601280a@xxxxxxxxxx
>> Hi Paul,
>>
>> How can I be sure that KITL is no longer accessing it?
>> When I run my driver, I get interrupts from the 91C96 that
>> should not be occuring (i.e. the interrupt does not match
>> the mask). If I add a 10 second delay to the end of my
>> InterruptHandler, no interrupts occur during that time.
>> However, immediately upon return from the InterruptHandler
>> a new interrupt is generated. There must be some other
>> code that is accessing the 91C96 that I have not properly
>> turned off.
>>
>> Thanks for the help! -Jeff
>>
>>>-----Original Message-----
>>>If the cable is connected, there's a reasonable chance
>> that you'll get
>>>network traffic. Are you sure you're not seeing broadcast
>> packets from
>>>other machines on your network getting to your Windows CE
>> device?
>>>
>>>Is the device configured for DHCP? Maybe it's trying to
>> get an IP address
>>>from a DHCP server?
>>>
>>>Other 'things' in the system aren't going to access the
>> chip directly, once
>>>you've removed KITL. Everything will go through the
>> driver. That doesn't
>>>mean that many network services won't be sending and
>> receiving data, though.
>>>
>>>Paul T.
>>>
>>>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>>>news:0c7a01c55203$37f77170$a401280a@xxxxxxxxxx
>>>>I am adding an NDIS driver to a PXA255 board. OS is winCE
>>>> 4.2 I want to make sure that nothing else accesses the
>>>> 91C96 ethernet chip other than my driver. To do this I
>>>> modified "OEMKitlInit" to only return FALSE to disable
>>>> KITL. In addition, under platform settings->build options
>>>> I unchecked "KITL" & "CE Target Control support".
>>>>
>>>> With KITL supposedly turned off and no ethernet drivers
>>>> added to the build I am still seeing constant access
to the
>>>> 91C96 chip. The TX light is constantly going & the
>>>> interrupt is constantly going.
>>>>
>>>> QUESTION : what else is accessing the 91C96? Have I
>>>> properly disabled KITL?
>>>>
>>>> The following environment variables are also set:
>>>> BSP_NOSHAREETH=1
>>>> KERNELNOSHAREETH=1
>>>> BSP_NOSERIAL=1
>>>>
>>>> Thanks in advance for any help -Jeff
>>>
>>>
>>>.
>>>
>
>
>.
>
.

Relevant Pages

  • Re: Patch available for shared em interrupts (Re: em, bge, network problems survey.)
    ... I'm seeing some patterns here with all of the network driver problem ... Are you experiencing network hangs and/or "timeout" messages on the ... If your em device is using a shared interrupt, ... Note that this patch will not help you if you are not using the em ...
    (freebsd-stable)
  • Re: splxxx level?
    ... ::> a question about interrupt priority levels. ... ::> There are currently three entry points into the driver: ... the network reception can cause a buf to be completed ... :: the appropriate spl level regardless. ...
    (freebsd-arch)
  • Re: splxxx level?
    ... :> I'm almost to testing on my AoE driver for 4.x and have ... :> a question about interrupt priority levels. ... the network reception can cause a buf to be completed ... the appropriate spl level regardless. ...
    (freebsd-arch)
  • Re: SMSC91C111 interrupt service routine
    ... I disconnect the chip from the network and it passed ... the SMSC driver activates the ... you enable device interrupt you get an interrupt event (for frames in RX ... I tried to put a breakpoint at the beginning of the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64
    ... If the system fails in ACPI mode, but works in non-ACPI mode, ... Using ACPI for SMP configuration information ... Using IOAPIC for interrupt routing ... Non-volatile memory driver v1.2 ...
    (Linux-Kernel)
Loading