From: Oliver Neukum <oliver@neukum.org>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Date: Sun, 12 Jun 2005 17:22:09 +0200 [thread overview]
Message-ID: <200506121722.09813.oliver@neukum.org> (raw)
In-Reply-To: <20050612130527.GB9401@animx.eu.org>
Am Sonntag, 12. Juni 2005 15:05 schrieb Wakko Warner:
> Oliver Neukum wrote:
> > Am Sonntag, 12. Juni 2005 02:41 schrieb Wakko Warner:
> > > After doing some testing, I believe a patch that went into rc4 broke kaweth.
> > > The kaweth driver itself did not change from rc2 through rc6.
> > >
> > > As a test, I reverted a patch that went into rc4 which modified
> > > net/core/link_watch.c. Once I compiled the kernel, my netgear EA101 works
> > > again.
> > >
> > > The above is not cut'n'paste. There was 1 other addition (an include) that
> > > I removed from the patch inorder to revert it. The patch above was applied
> > > to 2.6.12-rc6 using -Rp1. This is why I believe that kaweth is broken.
> > > With my limited understanding of the kernel, it would appear that kaweth
> > > doesn't support netif_carrier_ok properly.
> > > Anyway, I found what caused it to break, but at this point, I do not have
> > > the required knowledge to do a proper fix.
> >
> > static void int_callback(struct urb *u, struct pt_regs *regs)
> > is supposed to handle the link state. Maybe it fails in your case. Could you
> > add a printk to this callback to check linkstate?
>
> I don't believe my case is very specific. I've tested this on 4 different
> systems with totally different configs. If it is at all specific, I believe
> it would be with the network adapter itself. I don't have any other usb
> adapters that use kaweth.
>
> Can you tell me where I need to add the printks?
In static void int_callback(struct urb *u, struct pt_regs *regs):
/* we check the link state to report changes */
if (kaweth->linkstate != (act_state = ( kaweth->intbuffer[STATE_OFFSET] | STATE_MASK) >> STATE_SHIFT)) {
<------- HERE please a printk for detecting a link state change
if (!act_state)
netif_carrier_on(kaweth->net);
else
netif_carrier_off(kaweth->net);
kaweth->linkstate = act_state;
}
<----------- HERE the value of linkstate is important
resubmit:
kaweth_resubmit_int_urb(kaweth, GFP_ATOMIC);
Regards
Oliver
next prev parent reply other threads:[~2005-06-12 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 0:41 Wakko Warner
2005-06-12 1:16 ` Wakko Warner
2005-06-12 7:57 ` Oliver Neukum
2005-06-12 13:05 ` Wakko Warner
2005-06-12 15:22 ` Oliver Neukum [this message]
2005-06-15 1:02 ` Wakko Warner
2005-06-15 6:29 ` Oliver Neukum
2005-06-15 11:31 ` Wakko Warner
2005-06-15 11:30 ` Oliver Neukum
2005-06-15 16:53 ` Wakko Warner
2005-06-15 16:52 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506121722.09813.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=wakko@animx.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®