More on the Orinoco + XI-825 + StrongARM platform...

[David Gibson]

On Sat, Feb 23, 2002 at 10:31:22PM -0700, Ben Greear wrote:
> 
> >>>>eth1: Tx error, status 1 (FID=0212)
> >>>>eth1: Tx error, status 1 (FID=0264)
> >>>>eth1: Tx error, status 1 (FID=02FD)
> >>>>eth1: Tx error, status 1 (FID=018E)
> >>>>eth1: Tx error, status 1 (FID=037B)
> >>>>eth1: Tx error, status 1 (FID=01F4)
> >>>>eth1: Tx error, status 1 (FID=025F)
> >>>>eth1: Tx error, status 1 (FID=0314)
> >>>>eth1: Tx error, status 1 (FID=02E0)
> >>>>
> >>>>
> >>>Looks like one of the all-too-numerous generic errors we're fighting
> >>>at the moment :-(
> >>>
> >>
> >>Is there anywhere I can look to see what 'status 1' might mean?
> >>I got over my fear of hacking drivers (hopefully that is a good
> >>thing :))
> >>
> >
> >Status 1 is a "retry error" which I believe means that the firmware
> >has retransmitted the packet as many times as it's going to, hasn't
> >gotten an acknowledgement, and so has given up.
> 
> I added some __packed__ attributes to some structures, and now I
> rarely get this error above (and it works fine on the strongarm
> w/out compiling with the compile hack!)

Ok, where did you add these, precisely.  I thought I already had
__packed__ attributes in the relevant places, but apparently not.

> I still get shitty (200kbps) rates when transferring with both
> adapters in 'auto' mode.  However, if I fix it at 11Mbps, it runs
> at almost 900Mbps.

There still seem to be problems in the driver with setting the
transfer rates.  I'm still working on this.

-- 
David Gibson			| For every complex problem there is a
david at gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson