On Monday 06 August 2007, Tobias wrote:
> > The rndis_host driver isn't expected to work with all RNDIS
> > devices, that's why it's still "EXPERIMENTAL". You could find
> > out what's wrong and fix it. :)
> >
>
> Ok but it is the right driver to start work with it, right ?
It's the only hos
David Brownell schrieb:
> On Monday 06 August 2007, you wrote:
>
>> Hi,
>>
>> i have an USB Host to Host Bridge (PL-2502) which can act like an rndis
>>
>
> You don't mean PL-2501 do you? The Prolific website doesn't
> talk about a new PL-2502 chip.
>
> Of course it doesn't include any sp
On Monday 06 August 2007, you wrote:
> Hi,
>
> i have an USB Host to Host Bridge (PL-2502) which can act like an rndis
You don't mean PL-2501 do you? The Prolific website doesn't
talk about a new PL-2502 chip.
Of course it doesn't include any specs for the PL-2501 either,
which makes it hard t
Hi,
i have an USB Host to Host Bridge (PL-2502) which can act like an rndis
device. On a windows pc i only have to use the linux.inf file with a small
modifaction to get it work (i have changed the vendor and product id). Which
driver on linux should be used ? I thought rndis_host would be the
Hi,
I have tried running a the udhcpd server on the gumstix (pxa255) device
which has made the setup of Windows easier. However the problem is
still there.
After some arbitrary time the USB layer on windows freezes. This may
vary between seconds and hours.
Two ways to fix it.
- Unplug the
On Tuesday 26 September 2006 7:57 am, Dmitry Antipov wrote:
> Hello,
>
> I'm working with PXA27x hardware and going to check USB ethernet gadget
> (RNDIS mode)
> with 2.6.18 on PC host. After a short investigation, I was stucked because:
Yes, there are bugs there ... I thought they'd been fixed,
Hello,
I'm working with PXA27x hardware and going to check USB ethernet gadget (RNDIS
mode)
with 2.6.18 on PC host. After a short investigation, I was stucked because:
1) help on CONFIG_USB_ETH_RNDIS (taken from drivers/usb/gadget/Kconfig) says
that
RNDIS-aware configuration will be secon
David Brownell wrote:
> On Tuesday 22 August 2006 3:30 pm, Grahame Jordan wrote:
>> The device connects OK but after a short time it disconnects and in some
>> cases the networking layer on Windows freezes until the USB cable is
>> pulled out. Once the usb cable is put back in Widows reestablishe
Hi David,
>Which versions of Windows and Linux?
>
>
>
>
>
I am using a gumstix kernel PXA255 2.6.17gum and it also happens on
2.6.11gum
Windows - WinXP SP2, WinXP SP1, Win2000 SP4
WinXP SP2 works the better kinda
>But agreed ... I keep meaning to point this out to the EU as a
>clear example
On Tuesday 22 August 2006 3:30 pm, Grahame Jordan wrote:
> Hi,
>
> I have developed a device using a Gumstix (PXA255). The USBnet works
> perfectly on Linux using CDC ethernet, however when it comes to running
> it on Windows (RNDIS) which unfortunately will be the main target it
> breaks real
Hi,
I have developed a device using a Gumstix (PXA255). The USBnet works
perfectly on Linux using CDC ethernet, however when it comes to running
it on Windows (RNDIS) which unfortunately will be the main target it
breaks really badly.
It is clear that the RNDIS driver on Linux is incomplete b
On Tue, 30 May 2006 17:28:08 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> said:
>> If so, could you give details about how udev should be configured
>> (e.g., set bConfigurationValue through sysfs) ?
Alan> That's exactly right. The udev script should do something
Alan> like this:
Alan>
On Tue, 30 May 2006, Giridhar Pemmasani wrote:
> I need help configuring udev for this. Right now, without enabling
> RNDIS_HOST, device's probe function never gets called (presumably
> because no valid configurations are found in choose_configuration). Is
> it possible for udev to inform the kern
On Tue, May 30, 2006 at 04:58:58PM -0400, Giridhar Pemmasani wrote:
> On Mon, 29 May 2006 11:18:59 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> said:
>
> Alan> This change isn't needed. If you are using an out-of-tree
> Alan> driver like ndiswrapper then you can just as easily set up a
> Ala
On Mon, 29 May 2006 11:18:59 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> said:
Alan> This change isn't needed. If you are using an out-of-tree
Alan> driver like ndiswrapper then you can just as easily set up a
Alan> udev script to install the configuration you want when the
Alan> device i
On Mon, 29 May 2006 11:18:59 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> said:
>> This requires RNDIS host to be compiled into kernel itself - it
>> won't work if RNDIS is compiled as module.
Alan> Why do you say that? CONFIG_USB_NET_RNDIS_HOST will be set if
Alan> RNDIS is configured a
On Sun, 28 May 2006, Giridhar Pemmasani wrote:
>
> Since 2.6.16-rc1, when RNDIS devices are not configured; when a device
> is attached, following messages are logged by kernel:
>
> usb 1-1: new full speed USB device using uhci_hcd and address 2
> usb 1-1: default language 0x0409
> usb 1-1: n
Since 2.6.16-rc1, when RNDIS devices are not configured; when a device
is attached, following messages are logged by kernel:
usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: default language 0x0409
usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1:
Original Message-
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 14, 2006 9:06 AM
> To: linux-usb-devel@lists.sourceforge.net
> Cc: Vivek Dharmadhikari
> Subject: Re: [linux-usb-devel] rndis
>
> On Thursday 13 April 2006 5:57 pm, Vivek Dharmadhik
:06 AM
To: linux-usb-devel@lists.sourceforge.net
Cc: Vivek Dharmadhikari
Subject: Re: [linux-usb-devel] rndis
On Thursday 13 April 2006 5:57 pm, Vivek Dharmadhikari wrote:
> I want to have understanding about how the linux rndis module works.
> The linux rndis module uses 4 endpoint and t
On Thursday 13 April 2006 5:57 pm, Vivek Dharmadhikari wrote:
> I want to have understanding about how the linux rndis module works. The
> linux rndis module uses 4 endpoint and the status end point is one among
> them.
Start by reading the RNDIS spec.
-
Hello list
I am working on gadget driver for Analog Devices's vox160 chip. I have
finished the controller driver and is using the g_ether to interface
with windows usb host using rndis.
I want to have understanding about how the linux rndis module works. The
linux rndis module uses 4 endpoint a
--- David Brownell <[EMAIL PROTECTED]> wrote:
> On Monday 28 November 2005 11:26 am, Tony Riederer
> wrote:
> > In testing my usb ethernet gadget (RNDIS) vs.
> windows
> > XP (SP2) I am encountering a condition where the
> XP
> > machine hangs up during a file transfer or
> continuous
> > ping.
On Mon, Nov 28, 2005 at 12:22:00PM -0800, David Brownell wrote:
> This is clearly a nasty bug in Microsoft's software.
> It should not be even _possible_ for their network
> stack to lock up like that.
We have seen plenty of them during the development of the RNDIS driver;
the stack is pretty unst
On Monday 21 November 2005 12:32 pm, Javier Campos wrote:
> Hi all,
>
> Attempting to use the gadget layer for ethernet with a windows host gives me
> some problems. I am using the gadget backport in 2.4 on a Texas Instrument
> 2420
> omap board.
That would be _which_ backport?
- The stuff in
On Monday 28 November 2005 11:26 am, Tony Riederer wrote:
> In testing my usb ethernet gadget (RNDIS) vs. windows
> XP (SP2) I am encountering a condition where the XP
> machine hangs up during a file transfer or continuous
> ping. By 'hang' I mean that you can no longer access
> any of the network
In testing my usb ethernet gadget (RNDIS) vs. windows
XP (SP2) I am encountering a condition where the XP
machine hangs up during a file transfer or continuous
ping. By 'hang' I mean that you can no longer access
any of the network connections on the XP machine
including the LAN interface. Pulling
In testing my usb ethernet gadget (RNDIS) vs. windows
XP (SP2) I am encountering a condition where the XP
machine hangs up during a file transfer or continuous
ping. By 'hang' I mean that you can no longer access
any of the network connections on the XP machine
including the LAN interface. Pulling
Hello Javier,
On Monday 21 November 2005 21:32, Javier Campos wrote:
> Attempting to use the gadget layer for ethernet with a windows host
> gives me some problems. I am using the gadget backport in 2.4 on a
> Texas Instrument 2420 omap board.
>
> The problem is that if the USB cable is connected
Hi all,
Attempting to use the gadget layer for ethernet with a windows host gives me
some problems. I am using the gadget backport in 2.4 on a Texas Instrument 2420
omap board.
The gadget drivers are statically compiled into the kernel and the Linux
initscripts do the "ifconfig usb0 " on the linu
David -
I finally got back to the RNDIS problem we were having with our board (PPC
with net2280). The problem was actually in net2280.c little endian
conversion of the last n bytes (less than 4) in read_fifo. We are still
running the net2280 in PIO mode. I spent a lot of time trying to get dma
Resuming the host made transmisison work again. Other
than that, no problems.
So I'm poking at this driver a bit more ... that "filter flags"
patch, from this morning, might help you.
But then I noticed there are a lot of OIDs in there which
are either optional (notably, for statistics) or not eve
Robert Schwebel wrote:
Dave, could you do the ping test on your NetChip machine?
New hardware config: with XP, set up with bridging and
static IP, it worked fine too. Until one of the power
saving modes kicked in ... at which point the infinite
wisdom of XP decreed that it was time to issue a fe
I've had a WinME host pinging a gadget-2.6/net2280 system for
over half an hour with no problems now. I'll leave it doing
that until I need those systems for something else; how long
did it take for the problem to show up?
After about 44 hours I stopped that test. It was still pinging
just fine
Robert Schwebel wrote:
Hi,
We have recently updated our local tree to David's bk-2.4 but still see
transmission stops with the RNDIS driver on PXA. It can easily be
reproduced by pinging from a Windows host to the gadget; after some
minutes the pings are simply not answered any more.
Are they re
On Thu, 2004-05-13 at 22:50, Robert Schwebel wrote:
> We have recently updated our local tree to David's bk-2.4 but still see
> transmission stops with the RNDIS driver on PXA. It can easily be
> reproduced by pinging from a Windows host to the gadget; after some
> minutes the pings are simply not
Hi,
We have recently updated our local tree to David's bk-2.4 but still see
transmission stops with the RNDIS driver on PXA. It can easily be
reproduced by pinging from a Windows host to the gadget; after some
minutes the pings are simply not answered any more.
We are in the process of debuggin
On Tue, 2004-04-27 at 18:22, David Meggy wrote:
> On Tue, 2004-04-27 at 18:07, David Brownell wrote:
> > What does /proc/rndis/0 (or whatever) have to say? At a guess,
> > I'd say that it'll NOT be in the RNDIS_DATA_INITIALIZED state,
> > it'll be in RNDIS_INITIALIZED instead.
>
> yep, that's cor
On Tue, 2004-04-27 at 18:07, David Brownell wrote:
> What does /proc/rndis/0 (or whatever) have to say? At a guess,
> I'd say that it'll NOT be in the RNDIS_DATA_INITIALIZED state,
> it'll be in RNDIS_INITIALIZED instead.
yep, that's correct
~ # cat /proc/rndis/000
Config Nr. 0
used : y
st
David Meggy wrote:
Hmm, why isn't it xmitting?
Regardless of any Windows problems, I put a printk at the top of
ether.c: eth_start_xmit, which never gets called. And I see at line
2427: net->hard_start_xmit = eth_start_xmit;
So this should really be getting called.
Here is a little snippet of my
David Meggy wrote:
CDC ethernet works again (dumb mistake on my part). I still get the
warning message, but at least it works.
If you change bcdUSB to "0110" (1.1), does Windows like it better?
RNDIS still doesn't work. Same messages as Friday afternoon. Any
suggestions are appreciated.
Grab t
Hmm, why isn't it xmitting?
Regardless of any Windows problems, I put a printk at the top of
ether.c: eth_start_xmit, which never gets called. And I see at line
2427: net->hard_start_xmit = eth_start_xmit;
So this should really be getting called.
Here is a little snippet of my networking
~ # mo
CDC ethernet works again (dumb mistake on my part). I still get the
warning message, but at least it works.
RNDIS still doesn't work. Same messages as Friday afternoon. Any
suggestions are appreciated.
David
--
David Meggy
Engineering
Technical Solutions I
Hi again
slowly moving closer. I really hope that this is about the last thing I
have to fix before everything works. Maybe that is just wishful
thinking.
I did a quick check and decided to back to g_ether (CDC), after I had
made the fixes to get the device working for the g_zero tests. CDC no
As a rule, when I hook up a link and it doesn't behave, that's
exactly what's wrong. I've not yet gotten around to making
ZCIP automate everything.
As soon as I try and configure an IP address in Windows, I get either a
never ending hourglass or a blue screen of death. It depends on the
Window
On Fri, 2004-04-23 at 15:41, David Brownell wrote:
> Looks like good progress...
:) slowly but surely
> Did you make sure to set both ends of the link up in compatible
> ways ... like being the only two hosts on 192.168.4.* and with
> netmask 255.255.255.0? (Or something similar, not necessaril
Looks like good progress...
David Meggy wrote:
I didn't have the rndis.c debug on with the debug parameter turned on
I also had another login open running tcpdump -i usb0, but it showed
nothing happening
here is a dump
Using /lib/modules/2.4.25-vrs2.rndis/kernel/drivers/usb/gadget/n9604.o
~ # mod
On Wed, 2004-04-21 at 21:46, David Brownell wrote:
> Are you sure control-OUT works for your n9604_udc driver?
More sure now.
> You should be able to use "gadget zero" on that hardware
> with "usbtest" from a Linux 2.6 host ... one testcase
> gives a pretty good workout to ep0out, run it all day
By the way, after you get past that "control OUT not working yet"
issue with your new UDC driver, you might also see a problem
with the original "linux.inf" I sent out.
This patch should help.
- Dave
--- 1.1/Documentation/usb/linux.inf Tue Mar 30 16:25:48 2004
+++ edited/Documentation/usb/linu
David Meggy wrote:
Hi Dave
I've upgraded to the latest 2.4-gadget bitkeeper tree. CDC ethernet
still works and RNDIS still doesn't. Here are my updated messages.
~ # modprobe g_ether
Using /lib/modules/2.4.25-vrs2.rndis/kernel/drivers/usb/gadget/g_ether.o
usb0: Ethernet Gadget, version: St Patri
Hi Dave
I've upgraded to the latest 2.4-gadget bitkeeper tree. CDC ethernet
still works and RNDIS still doesn't. Here are my updated messages.
~ # modprobe g_ether
Using /lib/modules/2.4.25-vrs2.rndis/kernel/drivers/usb/gadget/g_ether.o
usb0: Ethernet Gadget, version: St Patrick's Day 2004
usb0
David Meggy wrote:
The current version is St Patrick's Day 2004, and I just
did the quick'n'dirty backport (compile testing only) and
pushed it into my gadget-2.4 tree. That's got the latest
RNDIS support (but not "linux.inf"), including that patch.
It might needs some tweaks to build on ARM/vrs2
On Tue, 2004-04-20 at 18:03, David Brownell wrote:
> David Meggy wrote:
>
> > ~ # modprobe g_ether
> > Using /lib/modules/2.4.25-vrs2/kernel/drivers/usb/gadget/rndis.o
> > Using /lib/modules/2.4.25-vrs2/kernel/drivers/usb/gadget/g_ether.o
> > usb0: Ethernet Gadget, n9604, version: Bastille Day 200
David Meggy wrote:
Would it possible to get a USB analyzer screen shot or some other sort
of log file with RNDIS starting up on windows. Without a working RNDIS
device here, it is a little hard to figure out what is going wrong, and
what is going right
The version in the gadget-2.4 tree just did t
David Meggy wrote:
~ # modprobe g_ether
Using /lib/modules/2.4.25-vrs2/kernel/drivers/usb/gadget/rndis.o
Using /lib/modules/2.4.25-vrs2/kernel/drivers/usb/gadget/g_ether.o
usb0: Ethernet Gadget, n9604, version: Bastille Day 2003
usb0: RNDIS activated
usb0: CDC host enet BE7D181ABDB5
~ # usb0: full
On Tue, 2004-04-20 at 12:41, David Brownell wrote:
> I'm not particularly a Windows expert myself, but I was quite
> pleased to see this work on net2280 the first time I tried ...
Hi Dave
Would it possible to get a USB analyzer screen shot or some other sort
of log file with RNDIS starting up on
On Tue, 2004-04-20 at 12:41, David Brownell wrote:
> > On Windows XP, after installing the linux.inf file from
> > linux/Documentation/usb/, I get a message from windows "This device
> > cannot start. (Code 10)"
>
> Did you try applying the patch I sent? I'm not sure it'd
> make a difference, but
David Meggy wrote:
Hi
I've written a National 9603/4 driver (not quite ready for submission
yet), and I'm trying to get RNDIS to work with it. CDC ethernet works
with a Linux host, but I can't get the RNDIS driver to work with
Windows.
A driver for another controller sounds great! Nothing too p
Hi
I've written a National 9603/4 driver (not quite ready for submission
yet), and I'm trying to get RNDIS to work with it. CDC ethernet works
with a Linux host, but I can't get the RNDIS driver to work with
Windows.
On Windows XP, after installing the linux.inf file from
linux/Documentation/usb
Joe Schmo wrote:
Hi
I'm trying to get the gadget RNDIS driver working, but I'm unsure on the
inf file for windows. Robert said in a previous posting that Microsoft
had examples but
http://www.google.com/search?q=microsoft+RNDIS+inf+template, just comes
up with linux mailing list archives. Wh
Hi
I'm trying to get the gadget RNDIS driver working, but I'm unsure on the inf
file for windows. Robert said in a previous posting that Microsoft had
examples but http://www.google.com/search?q=microsoft+RNDIS+inf+template,
just comes up with linux mailing list archives. Where can I get an e
61 matches
Mail list logo
