Fix a misplaced variable declaration in block-vvfat.c
-- Heikki Lindholm
--- qemu/block-vvfat.c 2005-12-20 00:11:49.0 +0200
+++ qemu-build/block-vvfat.c2006-04-22 09:48:23.0 +0300
@@ -1578,10 +1578,12 @@
mapping = find_mapping_for_cluster(s, cluster_num);
if
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
the attached patch adds a check to configure to see whether the compiler
really exists. If configure is called with --cc , but the given compiler
doesn't exist, configure currently fails without giving a good reason.
(In my case I ran "./confi
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
[EMAIL PROTECTED] wrote:
I have fixed this issue, also I have found the segfault on usb_del.
Patch is attached.
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.
Hm. There also seems to be s
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
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
>
> 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
[EMAIL PROTECTED] wrote:
In which case did it not work, when I test it, it is functioning (only
with libusb)
usb_add host:04b6x0005
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 synt
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
[EMAIL PROTECTED] wrote:
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
11 matches
Mail list logo
