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
21 matches
Mail list logo
