From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Hänel-Baas, Alexander" <alexander.haenel-baas@sieb-meyer.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: CONFIG_PREEMPT_RT_FULL an usb gadget
Date: Thu, 29 Aug 2013 13:35:21 +0200 [thread overview]
Message-ID: <20130829113521.GB15360@linutronix.de> (raw)
In-Reply-To: <9BA84827B30CBE4996725F98F7DC91232F954E81@SMExchange01.siebmeyer.org>
* Hänel-Baas, Alexander | 2013-08-27 14:54:35 [+0000]:
>Hello rt-community,
Hi,
>i use the kernel 3.10.4 with the 3.10.4-rt-1 patch
>and the usb RNDIS connection to a windows pc.
So you use an x86 based UDC/machine if you are using v3.10.4-rt1 here.
>In the kernelconfig i set the low-latency desktop with CONFIG_PREEMPT_LL=y and the usb Ethernet gadget works fine.
>
>Now i change the kernelconfig to CONFIG_PREEMPT_RT_FULL=Y and now it is not possible to get a working usb gadget connection.
Is a different gadget working? Say usb-storage against Windows oder
g_ncm against Linux?
>In both situation i see that windows detect the RNDIS device in the device manager.
>
>The next step was to enable the USB gadget debugging messages to see what is going on.
>At this time I see many usb-gadget outputs:
>
>#dmesg
>[ 84.085953] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER
>[ 84.093266] g_ether gadget: rndis reqa1.01 v0000 i0000 l4096
>[ 84.093621] g_ether gadget: rndis req21.00 v0000 i0000 l36
>[ 84.101284] g_ether gadget: rndis reqa1.01 v0000 i0000 l4096
>[ 84.101680] g_ether gadget: rndis req21.00 v0000 i0000 l36
>[ 84.109265] g_ether gadget: rndis reqa1.01 v0000 i0000 l4096
>[ 84.109663] g_ether gadget: rndis req21.00 v0000 i0000 l36
>[ 84.109782] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER
>...
>
>But I can't find a difference between the working config (low-latency)
>and the full-rt configuration.
>
>What can I do to get a working fully pre-emptible usb gadget?
Try to enable lock debuging and see if the kernel complains about
something.
So after enabling debug you don't see a difference in the communication?
Can you try against Linux RNDIS and see if that is working? If that also
fails then you get a chance to debug.
>
>kind regards
>Alexander Haenel-Baas
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-29 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 14:54 CONFIG_PREEMPT_RT_FULL an usb gadget Hänel-Baas, Alexander
2013-08-29 11:35 ` Sebastian Andrzej Siewior [this message]
[not found] ` <9BA84827B30CBE4996725F98F7DC91232F955F47@SMExchange01.siebmeyer.org>
2013-08-29 18:58 ` AW: " Sebastian Andrzej Siewior
2013-09-03 7:02 ` AW: " Hänel-Baas, Alexander
2013-09-12 11:41 ` Hänel-Baas, Alexander
2013-10-11 9:39 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2013-10-14 14:26 Hänel-Baas, Alexander
2013-10-18 14:35 ` Sebastian Andrzej Siewior
2014-04-07 19:30 ` David Lopo
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=20130829113521.GB15360@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alexander.haenel-baas@sieb-meyer.de \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).