On Thu, Jul 13, 2000 at 11:55:27AM -0700, Deborah Wallach wrote:
>
> It implements a basic ethernet interface complete with and eth0
> interface. I've not tried to pass packets to it (yet) but will in the
> next week or two. I don't know what the DECWRL folks talked to with
> it. Persumably they wrote some host code. I plan to implement the
> other side shortly.
>
> We talk to it using either Linux (2.3.34) on an x86 PC or Windows 95/2000.
> I haven't used the windows version myself, so I don't know anything about
> it. Yes, we wrote some host code for the linux setup, but it's flaky (the
> host machine crashes fairly often while using usb to the itsy), but if you
> think it would be useful I can see if I can dig it up and get it posted
> somewhere.
I will be very interested by all those code (both client and host,
Win and Linux) since I already try to implement something like this.
I got the usb pipe #0 running correctly and Linux (2.3.99preX) configuring
it correctly but can get the other pipe running. On the windows side,
I ask a demonstrator for the SA-1111 to show me some code (both
WinCE embedded or WinDriver Host) and the only thing he could find
me is a USB Mouse Driver (really... they're very stupid sometime -
we really have a lot of fun imagining what we can do with a mouse
running a StrongArm :)
I can myself send you the module I create for the linux host
side, although the bulk pipes were never tested.
BTW, do you think we can used a common DeviceID/VendorID
for the code in the both kernel? Especially since the driver
implementation will all be the same (mainly a network driver
with a ppp-like connection).
>
> -Debby
--
-------------------------------* *-------------------------
Fabien Ni�oles / / [EMAIL PROTECTED]
Chevalier Servant de Sa Dame / / C15D FE9E BB35 F596 127F
Veneur Gris par la Clef / / BF7D 8F1F DFC9 BCE0 9436
Chaton pour Debian / / http://www.tzone.org/~fabien
--------------------------* *------------------------------
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
