Hi all,
0.3.14 was released mainly to add more 3 devices and to fix small
bug in pegasus_set_register macro. There will be no larger changes
in 0.3 version - only bugfixes.
Now i am writing 0.4-pre version of the driver which will uses URB
requests for all control messages. In current version i can't touch
HW from bottom-halves. I can't touch it even from as called top-halves
because there is no guarantee that the driver is accessed with the
correct process' context, which breach compatibility call
usb_control_msg(). AFAIK there is no priority of control msgs over
other type of transfers. This is about to be changed, but will
take time.
Until then i'll try to make this device working and i'll post 0.4-pre
immediately when i got it working somehow for testing/bug
fixing/comments.
Thanks to everybody for the help!
best,
Petkan
Jason Sharpee wrote:
>
> I just tried 3.14 as well with the same results. RX status -110 followed
> by TX status -110 messages and eth0 dropout.
>
> I noticed that the interrupt is being pulled and apparently there is
> nothing in the buffer (actual data size) for the data, compared to what
> it was expecting yielding the -110 message which gets passed back to the
> driver. Is this indicative that the physical device (Linksys 10/100) is
> getting confused and not responding to the HC driver request for data
> and/or is this a congestion issue of traffic on the USB bus and missing a
> control message? Does a -110 urb status happen quite often, or is this
> just a problem I am experiencing with my system configuration?
>
> The driver / device seem to deadlock on this failed data item and eth0
> stops xmitting data, hence my problem.
>
> Thanks for your time!
> -Jason
>
> On Fri, 9 Jun 2000, Rick Richardson wrote:
>
> > On Fri, Jun 09, 2000 at 01:58:56PM -0700, Stephen J. Gowdy wrote:
> > > Hi Rick,
> > > There is now a 3.14 version of the pegasus driver. Not sure it
> > > will make any difference though, but you might want to try it, I've
> > > attached it.
> >
> > Thanks for the newer driver. But I'm still seeing the same NFS
> > problems -- MP3 dropouts when rsize,wsize=1024, and also NFS server
> > not responding...OK when the size is bigger than that.
> >
> > My guess is its a receive side problem (dropped packets?). I suppose
> > I should collect some tcpdumps on the NFS server and on the client
> > (the iOpener), then start digging into the code.
> >
> > -Rick
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
