I've been down this road before. This is the same chip that's in the
Entrega USB/Ethernet product and the Linksys USB10T. It's been suggested
to me that this is also the same chip in the 3Com product.
I spent quite some time trying to get firmware information of some type.
No luck. A quick inspection of the boards, however, suggests that these
are wired _very_ much alike. It might be possible that firmware to use
one of them will work with all of them.
Matt Dharm
On Sun, 19 Mar 2000, Michael Rothwell wrote:
> Here's some correspondance between Donand Becker and myself. The problem is,
> essentially, that this contains a programmable microcontroller. The Win98
> driver probably programs it. Kawasaki supplied only electrical information
> for it online. I'm trying to get more info from them. They wouldn't give it
> to Becker, though, so I'm not hopeful (doesn't mean I'm not stubborn).
>
> Follow-up:
>
> http://www.klsi.com/products/usbstandard.html
>
> The chip inside says "KL5KUSB101BCL"
>
> http://www.klsi.com/products/usb/KL5KUSB101DS_ver2_4.pdf
>
> Full chipset info, apparently!
>
> -M
>
> -----Original Message-----
> From: Michael Rothwell
> Sent: Sunday, March 19, 2000 5:12 PM
> To: '[EMAIL PROTECTED]'
> Cc: Michael Zappe
> Subject: NetGear EA101c USB to Ethernet
>
>
> I bought a NetGear EA101c USB to Ethernet adapter today, intending to hook
> it to an iOpener (http://www.linux-hacker.net/iopener/), which I special
> ordered. I've done a little looking around, but I've not found anything
> about Linux support for this gadget. With the aid of a screwdriver, the
> Linux kernel and the net, I determined that it's really a LiteOn LNE100TX
> ethernet chip inside. Unfortunately, I'm having trouble finding out anything
> about that device, as well. What's the current state of USB to Ethernet
> devices on Linux? If anyone knows anything about Linux ethernet drivers,
> it's you, so I thought I would ask. If there's anything I can so to help as
> well, let me know. Peeking through the files on the Win98 driver disk, I
> found a few more bits of info:
>
> NETEA101.INF:
>
> %USB\VID_0846&PID_1001.DeviceDesc% = NETGEARUsbEth, USB\VID_0846&PID_1001
>
> ... Vendor ID 0846 and Product ID 1001, I assume
>
>
>
> Opening the EA101ND4.SYS file up in Visual Studio, I found some more stuff.
>
> CompanyName: Kawasaki LSI U.S.A, Inc.
> ProductName: KSLI USB-Ethernet Adapter
> FileVersion: 02.00 02.02
> InternalName: USBENET.SYS
> ProductVersion: 02.00 02.02
>
> E:\SOURCE\Wolfe\NT50DDK\SRC\NETWORK\REESES\i386\free\USBENET.pdb
>
> ... wonder if it will work on 2000 as welll...
>
> Looks like an NDIS driver...
>
> DbgPrintFExFreePool
> ExAllocatePoolWithTag
> KeCancelTimer
> KeInitializeSpinLock
> KeInitializeEvent
> KeSetTimer
> KeInitializeDpc
> KefReleaseSpinLockFromDpcLevel
> KefAcquireSpinLockAtDpcLevel
> KeWaitForSingleObject
> IoFreeIrp
> IoBuildDeviceIoControlRequest
> KeSetEvent
> IofCallDriver
> PsCreateSystemThread
> KeInitializeTimer
> IoCancelIrp�InterlockedDecrement
> InterlockedIncrement
> PsTerminateSystemThreadntoskrnl.exe
> KKfLowerIrqlLKfRaiseIrqlHAL.dll
> NdisTerminateWrapper
> NdisMRegisterMiniport
> NdisInitializeWrapper
> NdisReadConfigurationNdisWriteErrorLogEntry
> NdisRegisterAdapterShutdownHandler
> NdisMSetAttributesEx
> NdisMGetDeviceProperty
> NdisAllocateSpinLock
> NdisCloseConfiguration
> NdisAllocateMemory
> NdisOpenConfiguration
> NdisBufferVirtualAddress
> NdisAllocatePacket
> NdisAllocateBuffers
> NdisFreeMemory
> NdisFreeSpinLock
> NdisFreePacket
> NdisFreeBuffer
> NdisDeregisterAdapterShutdownHandler
> NdisReleaseSpinLock
> NdisAcquireSpinLock
> NdisAllocateBufferPool
> NdisAllocatePacketPool
> NdisFreeBufferPool
> NdisFreePacketPool
> NdisQueryBuffer"NDIS_BUFFER_TO_SPAN_PAGES
> NdisQueryBufferOffset
> NdisAdjustBufferLengthNDIS.SYS
> USBD_GetUSBDIVersion
> USBD_ParseConfigurationDescriptor
> USBD_CreateConfigurationRequestUSBD.SYS
>
>
> -M
>
> -----Original Message-----
> From: Brad Hards [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 20, 2000 6:04 AM
> To: Michael Rothwell
> Subject: Re: [linux-usb] LiteOn LNE100TX/NetGear101c USB to Ethernet
>
>
> Michael Rothwell wrote:
> > The NetGear EA101c USB to Ethernet adapter ($39 @ Circuit City) uses a
> > LiteOn LNE100TX ethernet chip. The 2.2.12-20 (Redhat 6.1) kernel
> recognized
> > it on boot. It comes with only Win98 drivers (natch). I called NetGear.
> They
> > claimed ignorance. The Ethernet address gave away that it was LiteOn
> inside.
> > The kernel boot confirmed it. Does anyone know of any support for this
> > thing? It would be great to hook to an iopener!
>
> LiteOn LNE100TX is a Tulip based adapter chip (perhaps an inferior copy)
> see http://cesdis.gsfc.nasa.gov/linux/drivers/pnic.html and
> http://www.linksys.com/support/solution/nos/linux_lne100tx.htm for
> details.
> Did you open the dongle? What else was in the dongle - some form of USB
> microcontroller (Anchorchips maybe?) ?
>
> I am not sure what you mean by "recognized it on boot". Do you mean that
> some driver actually recognised the adapter? Or that the kernel knows
> about LNE100TX (aka tulip)?
>
> What boot (or dmesg or /var/log/messages) entries are applicable? What
> drivers did you have loaded?
>
> What does /proc/bus/usb/drivers and /proc/bus/usb/devices contain?
>
> If it is a tulip based adapter, then the missing magic is in the USB
> control/interrupt/bulk messages to LNE100TX part. As Vojtech pointed
> out, this needs to be provided by the manufacturer. Or potentially
> reverse engineered from Win98. Or maybe from the FreeBSD stuff, which
> does have a wider range of ethernet USB adapters (probably not this one
> though) than Linux.
>
> Also, the NetGear website claims it is a 10BaseT device, although the
> adapter should be 10/100 if it is really a tulip chipset.
>
> Brad
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Matthew Dharm Home: [EMAIL PROTECTED]
Engineer, Qualcomm, Inc. Work: [EMAIL PROTECTED]
It was a new hope.
-- Dust Puppy
User Friendly, 12/25/1998
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
