And any reason for not posting this to David and the linux-usb-devel
mailing list?
thanks,
greg k-h
> Doesn't the usbdnet.c driver support the Zaurus?
usbdnet.c I saw was for 2.4.19, and ate data from time to time. It was
piece of junk.
> And any reason for not posting this to David and the linux-usb-devel
> mailing list?
I'll do that once I test it. [That should be in about 5 minutes.]
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
> Doesn't the usbdnet.c driver support the Zaurus?
Both the Zaurus and the iPAQ are using a SA1110 which is already supported
by usbnet.
Nicolas
Yes, but that's on the client side of USB, right? Pavel's patch is for
the host side, which I think was supported by usbdnet for the Zaurus.
Or am I just really confused?
greg k-h
> On Fri, Oct 18, 2002 at 09:38:49PM -0400, Nicolas Pitre wrote:
> > On Fri, 18 Oct 2002, Greg KH wrote:
> >
> > > Doesn't the usbdnet.c driver support the Zaurus?
> >
> > Both the Zaurus and the iPAQ are using a SA1110 which is already supported
> > by usbnet.
>
> Yes, but that's on the client side of USB, right? Pavel's patch is for
> the host side, which I think was supported by usbdnet for the Zaurus.
If both clients i.e. the iPAQ and the Zaurus are actually a SA1110, and if
the iPAQ is already supported on both sides, then the Zaurus should work out
of the box.
Nicolas
These patches will apply to recent 2.4.20pre kernels too, if anyone
is sufficiently impatient to try... :)
> If both clients i.e. the iPAQ and the Zaurus are actually a SA1110, and if
> the iPAQ is already supported on both sides, then the Zaurus should work out
> of the box.
Yes, but out of the www.handhelds.org box, not Sharp's box.
Zaurus doesn't have a stock www.handhelds.org kernel; there's a
different usb slave/target device driver, which uses different
framing for the Ethernet packets. Pavel's patch teaches "usbnet"
about one of those protocols. (The other is MSFT-friendly.)
It's worth mentioning the Yopy here too: Zaurus isn't the only
SA-1110 based Linux PDA, and its distro is evidently closer to
the iPAQ distros (but you won't need a WinCE-ectomy). Current
versions of "usbnet" have support for a recent YOPY version; they
use different USB vendor and product IDs "out of the box".
- Dave
> Zaurus doesn't have a stock www.handhelds.org kernel; there's a
> different usb slave/target device driver, which uses different
> framing for the Ethernet packets. Pavel's patch teaches "usbnet"
> about one of those protocols. (The other is MSFT-friendly.)
>
> It's worth mentioning the Yopy here too: Zaurus isn't the only
> SA-1110 based Linux PDA, and its distro is evidently closer to
> the iPAQ distros (but you won't need a WinCE-ectomy). Current
> versions of "usbnet" have support for a recent YOPY version; they
> use different USB vendor and product IDs "out of the box".
Why not using the same (the best which ever it is) driver instead of
reinventing the wheel for every SA1110-based devides out there?
Nicolas
>>Zaurus doesn't have a stock www.handhelds.org kernel; there's a
>>different usb slave/target device driver, which uses different
>>framing for the Ethernet packets. Pavel's patch teaches "usbnet"
>>about one of those protocols. (The other is MSFT-friendly.)
>>
>>It's worth mentioning the Yopy here too: Zaurus isn't the only
>>SA-1110 based Linux PDA, and its distro is evidently closer to
>>the iPAQ distros (but you won't need a WinCE-ectomy). Current
>>versions of "usbnet" have support for a recent YOPY version; they
>>use different USB vendor and product IDs "out of the box".
>
>
> Why not using the same (the best which ever it is) driver instead of
> reinventing the wheel for every SA1110-based devides out there?
I think that on the host side the evidence is that "usbnet" is that
driver, and Pavel's patch is big step forward. It forces all the
remaining questions onto the slave/target side (PDA for now).
Now, on the device side ... that's not really my call, but I agree
that'd be a good way to go. The question is what's "best"?
Last I looked, no www.usb.org class spec or IETF RFC (even I-D)
standardized a reasonably simple/robust "IP-over-USB", so there
are only vendor-specific solutions. Some of them deal with odd
hardware quirks, others deal with MSFT interop. Lots of vendor
expectations have unfortunately been set on the MSFT side, where
creating product interop problems is sometimes seen as a win in
terms of market control or "product differentiation".
- Dave
> > > > Doesn't the usbdnet.c driver support the Zaurus?
> > >
> > > Both the Zaurus and the iPAQ are using a SA1110 which is already supported
> > > by usbnet.
> >
> > Yes, but that's on the client side of USB, right? Pavel's patch is for
> > the host side, which I think was supported by usbdnet for the Zaurus.
>
> If both clients i.e. the iPAQ and the Zaurus are actually a SA1110, and if
> the iPAQ is already supported on both sides, then the Zaurus should work out
> of the box.
No.
You'd be right if you ran iPAQ's rom on zaurus. But sharp's rom uses
diferent protocol, so this is still needed. Reflashing zaurus is
possibility, but not everyone does that, (cf card needed), and if you
reflash to change protocol (noone does that) your zaurus will be
incompatible with every other zaurus.
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.