David Hollis wrote:
>> So it's no longer complaining about anything except the rxqlen, but
>> unfortunately there is still no traffic getting in or out.
> It's not complaining about rxqlen, that's just a debug blurb. It sounds
> like the RX_CTL may not be getting set properly. Can you bring up th
On Wed, 2006-05-03 at 01:00 +0200, Mattias Bergsten wrote:
> Well, we've got some progress:
>
> usb 1-2.1: new high speed USB device using ehci_hcd and address 5
> usb 1-2.1: configuration #1 chosen from 1 choice
> asix 1-2.1:1.0: status ep1in, 8 bytes period 11
> eth1: register 'asix' at usb-000
David Hollis wrote:
> That's a good demonstration of testing code before you send it out! I
> meant to move that block that checks the PHY ID below the part where I
> actually read the PHY address but I didn't so it was reading from the
> wrong place. The attached patch seems to behave fine on x8
On Mon, 2006-05-01 at 23:17 +0200, Mattias Bergsten wrote:
> Had to upgrade to 2.6.17-rc3 to get the driver version to agree with
> the
> patch because of the restructuring. Tried with and without the patch
> on
> ppc but unfortunately does not work either way, without it's the same
> as
> before a
David Hollis wrote:
> On Sun, 2006-04-30 at 21:00 -0700, David Brownell wrote:
>> That PHY register failure would explain things ... maybe it's
>> a byteswap bug in that driver code?
>>
>
> This is the relevant portion from ax88772_bind():
>
> if (((ret = asix_read_cmd(dev, AX_CMD_READ_MI
On Sun, 2006-04-30 at 21:00 -0700, David Brownell wrote:
> That PHY register failure would explain things ... maybe it's
> a byteswap bug in that driver code?
>
This is the relevant portion from ax88772_bind():
if (((ret = asix_read_cmd(dev, AX_CMD_READ_MII_REG,
