Re: Linksys WUSB11 V 2.8; can't compile at76c503a sources

On Mon, 2004-01-19 at 14:41, Joerg Albert wrote:
> Hi,
> 
> On Sun, 18 Jan 2004, Ian B. Jacobs wrote:
> 
> > I sent email to the user list for at76c503a but I don't
> > see it in the archive; my apologies for writing to you
> > privately. You may forward my email to any list you wish.
> 
> your posting got piled with others for manual submission as you were not a
> list member (spam protection). But you should have gotten a mail saying
> so??

I don't believe I did (and I checked my spam filter as well).

> > My email is below. I am trying to use the berlios driver
> > with my WUSB11 v2.8 but I am having no luck, not even
> > compiling the source. Any help would be appreciated.
> > ...
> >   * variable static_fw has initialized but incomplete type
> >     [fw-pkg-i3861.h]
> >   * In function fw_dev_param, FIRMWARE_NAME_MAX is undeclared.
> >   * In function at76c50x_probe storage size of static_fw isn't known.
> >     [at76c503-fw_skel.c]
> >
> > /lib/modules/2.4.22-xfs/build points to
> > /usr/src/linux which points to
> > /usr/src/kernel-source-2.4.22-xfs
> >
> > I have not been able to figure out what I need to do to compile
> > successfully.
> 
> Sorry, my fault. The latest change didn't compile with < 2.4.23.
> I've just fixed it in the cvs, guess tomorrow (MEST) it is in the
> cvs snapshot. If impatient, use the cvs browser to look at e.g.
> at76c503-rfmd.c around #include <linux/firmware.h> - same change in all
> at76c50[35]-{i386[13],rmfd*}.c files.

Thanks!

> > I also note that when I tried to use version 0.11 of the driver [1],
> > I was able to compile and load the driver, but I was getting
> > tremendous packet loss when pinging the machine with the WUSB11
> > attached. Hence, I wanted to recompile from the source to see if that
> > helped.
> 
> I fear it won't, as 0.12 was mainly a try to get a common source for 2.4
> and 2.6 kernels. 

Ok. 

> What's your peer, an AP or another client? 

Another linux box in the internal network. Round-trip time is
a couple of milliseconds.

> Where do you see the loss?

Ping showed high packet loss. I'm happy to do more thorough debug,
but you'll have to guide me through it.

> I'd prefer to continue any discussion in the mailing list.

As would I. I'll let you know how the patch worked for me.

Thanks very much,

 _ Ian
-- 
Ian Jacobs ([email protected])   http://www.w3.org/People/Jacobs
Tel:                     +1 718 260-9447

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBADEKi3Vu9UJRDGtARAvp0AKCWVqhIztFTp6FUoNWL7uGyAjXQ+QCgguKm
B07Mg6p2/FWCN6TfL26Pxhg=
=BH6N
-----END PGP SIGNATURE-----