Hello Lonnie.
Lonnie Mendez wrote:
> Johannes Schindelin wrote:
>
>>
> Seeing as there is a release coming up this is most definitely not a
> good thing. Initial testing yielded lots of this.
> I'd like to see my all-in-one patch stripped out. Then simply
> modifying the linux redirector to
Hello Johannes,
I have to admit that your post did piss me off a little bit. But on the
other hand it would not help anybody, if I would shoot back, so I will
try to be as polite as possible.
My first note is on your first message, which I really have not
received. It is probably my fault, but I
Hello Johannes,
Thanks for your comments.
Johannes Schindelin wrote:
> I am quite sure you put a lot of work into this patch, but you sure make it
> hard to appreciate, too.
>
> First note that applying such a huge patch is bad. Let me help you (a little
> more than last time)
Sorry I dont know
Hello,
As Fabrice pointed out to me yesterday, it takes time to understand the
new usb api. To make this process easier I have assembled a small
documentation.
You will find it here:
http://217.20.126.200/tino/usb_api.pdf
http://217.20.126.200/tino/usb_api.odg
the patch which applies cleanly agai
Hello Fabrice,
This patch introduces an already fixed bug with linux guest os. The
message is: "controller still running". The attached patch fixes this
problem.
Believe me it would save both of us a lot of time, if you would simply
add the large usb patch.
With kind regards,
Tino H. Seifert
Fab
Hello everybody,
As Fabrice is already adding some changes to cvs. The patch is getting
smaller (by fivehundert lines today). If we keep this speed the patch
will be gone in only 9 more days.
Here is the patch - as allways applying cleanly to todays cvs:
http://217.20.126.200/tino/usb-2006-04-24.
Hello,
Lonnie Mendez wrote:
>
> That works but not in the literal means of the attached device
> actually functioning (see below). Here is something interesting:
>
> (qemu) usb_add mouse
> Controller 001: uhci
> 001:001 = mouse
> Summary: 1 USB Controller, 1 USB Devices
> (qemu
Hello Fabrice,
I can understand, that you are not so happy with such an huge patch. But
sorry it can't be done with just patching the state machine. The main
problem is, that the cvs source needs the usbhub. But this hub is not
operational at its current state. So in fact whenever we try to find a
Lonnie Mendez wrote:
> [EMAIL PROTECTED] wrote:
>
> Sorry about that. I was used to the previous syntax:
> usb_add host:04b6:0005
>
> My guess is that the new syntax is to distinguish it from the
> busaddr:addr syntax? It would seem checking for length would
> differentiate the two in that ca
>
> Adding a device by Vendor id and Product id doesn't seem to work.
> If this is intentional then perhaps the functionality should be
> restored. qemu users will find this convenient as it is a
> fixed/static identification for a single usb device which is most
> likely going to be the commo
Sorry have forgotten the patch.
>
--- qemu-2006-04-22/hw/usb.c 2006-04-22 14:44:21.0 +0200
+++ qemu/hw/usb.c 2006-04-22 17:24:06.0 +0200
@@ -403,73 +403,74 @@
/* this function adds a newly created device and cares for the attach and
handles all errors */
-int add_usb_dev
Hello Lonnie,
Lonnie Mendez wrote:
> [EMAIL PROTECTED] wrote:
>
>> Next problem:
>> Linux does not recognize it, if I add a "tablet" while linux is allready
>> running. The attach is not delivered to the operating system.
I have solved the problem, it was located in a rejected diff. (it was
the re
Hello,
I have made a new patch which includes all changes from yesterday,
because there were already inconsistencies Also attached is the log of
my USB scanner (The last lines are repeated for ever). It is recognized
but when the first bulk packet is send to it, I get a ETIMEDOUT Error
and I don't
Hello,
Lonnie Mendez wrote:
>
> There are of course more bugs I've found. Namely being able to
> usb_add any particular string with that string showing up as a new
> device even though no valid entry for it exists.
I have fixed this issue, also I have found the segfault on usb_del.
Patch is att
you are too fast for me :)
Lonnie Mendez wrote:
> lo. The attached patch applied on top of your patchset seems to
> work as far as signaling resume goes.
>
>
>
>
___
Qemu-de
Hello,
Lonnie Mendez wrote:
> Lonnie Mendez wrote:
>
>>
>> The port registers on the uhci controller shows no appropriate
>> response to an HCHALT command that is issued and so the hcd puts the
>> controller into global suspend.
>
> The problem is more likely that the controller is being suspe
Hello Lonnie,
First, thank you for the answer.
Lonnie Mendez wrote:
> [EMAIL PROTECTED] wrote:
>
>> printer was not even detected under qemu. So I started to work on it.
>>
> Are you sure such vast changes are necessary? What was it exactly
> that happened when you attached the printer/scanne
Hello everybody,
I have extended the USB support for Qemu. The patch is included and
compiles just fine against todays cvs repository. As explained below,
this patch touches 15 different files, which makes it not so easy to
keep it applying on that very fast developing project. Thats why I would
a
18 matches
Mail list logo
