You can subscribe to this list here.
| 2003 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct (5) | Nov (27) | Dec (9) | 
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 | Jan (2) | Feb (19) | Mar (13) | Apr (15) | May (11) | Jun (17) | Jul (31) | Aug (45) | Sep (10) | Oct (40) | Nov (39) | Dec (45) | 
| 2005 | Jan (113) | Feb (45) | Mar (38) | Apr (53) | May (11) | Jun (42) | Jul (56) | Aug (50) | Sep (32) | Oct (32) | Nov (47) | Dec (22) | 
| 2006 | Jan (19) | Feb (32) | Mar (40) | Apr (40) | May (41) | Jun (44) | Jul (37) | Aug (51) | Sep (30) | Oct (30) | Nov (51) | Dec (20) | 
| 2007 | Jan (7) | Feb (20) | Mar (17) | Apr (67) | May (13) | Jun (73) | Jul (16) | Aug (58) | Sep (29) | Oct (5) | Nov (74) | Dec (9) | 
| 2008 | Jan (17) | Feb (12) | Mar (65) | Apr (22) | May (40) | Jun (32) | Jul (11) | Aug (8) | Sep (3) | Oct (41) | Nov (34) | Dec (12) | 
| 2009 | Jan (44) | Feb (33) | Mar (16) | Apr (109) | May (11) | Jun (22) | Jul (21) | Aug (37) | Sep (5) | Oct (23) | Nov (7) | Dec (7) | 
| 2010 | Jan (36) | Feb (40) | Mar (35) | Apr (45) | May (42) | Jun (104) | Jul (135) | Aug (50) | Sep (65) | Oct (110) | Nov (129) | Dec (75) | 
| 2011 | Jan (105) | Feb (48) | Mar (93) | Apr (166) | May (169) | Jun (188) | Jul (106) | Aug (33) | Sep (85) | Oct (46) | Nov (102) | Dec (105) | 
| 2012 | Jan (81) | Feb (115) | Mar (56) | Apr (93) | May (56) | Jun (77) | Jul (88) | Aug (52) | Sep (72) | Oct (16) | Nov (70) | Dec (70) | 
| 2013 | Jan (23) | Feb (85) | Mar (38) | Apr (48) | May (40) | Jun (49) | Jul (33) | Aug (28) | Sep (66) | Oct (28) | Nov (28) | Dec (16) | 
| 2014 | Jan (33) | Feb (58) | Mar (17) | Apr (50) | May (16) | Jun (24) | Jul (19) | Aug (32) | Sep (10) | Oct (10) | Nov (4) | Dec (10) | 
| 2015 | Jan (11) | Feb (2) | Mar (4) | Apr (14) | May (1) | Jun (6) | Jul (16) | Aug (29) | Sep (6) | Oct (26) | Nov (10) | Dec | 
| 2016 | Jan | Feb (20) | Mar (6) | Apr | May (3) | Jun (3) | Jul | Aug (16) | Sep (6) | Oct | Nov (15) | Dec | 
| 2017 | Jan (1) | Feb (2) | Mar (4) | Apr | May (1) | Jun (3) | Jul | Aug | Sep | Oct (1) | Nov (1) | Dec (1) | 
| 2018 | Jan | Feb (8) | Mar (10) | Apr (16) | May | Jun (15) | Jul | Aug (3) | Sep (19) | Oct | Nov | Dec | 
| 2019 | Jan | Feb | Mar (1) | Apr (2) | May | Jun | Jul | Aug | Sep (3) | Oct | Nov | Dec | 
| 2020 | Jan | Feb | Mar | Apr (5) | May | Jun | Jul (7) | Aug | Sep | Oct | Nov | Dec | 
| 2021 | Jan (5) | Feb | Mar | Apr | May | Jun (5) | Jul (3) | Aug | Sep (6) | Oct (2) | Nov (4) | Dec | 
| 2022 | Jan (1) | Feb (1) | Mar | Apr (1) | May | Jun (5) | Jul | Aug | Sep | Oct | Nov | Dec | 
| 2023 | Jan (5) | Feb (1) | Mar | Apr (3) | May (1) | Jun | Jul | Aug | Sep | Oct | Nov | Dec | 
| 2024 | Jan | Feb (3) | Mar (1) | Apr (1) | May (11) | Jun (1) | Jul | Aug | Sep | Oct (3) | Nov (3) | Dec | 
| 
      
      
      From: Dan E. <Dan...@ne...> - 2006-05-05 09:26:05
      
     | 
| As Stephan says, you can't explicitly set the address from windows since it's done by the USB stack, and if a user program tried to change it independantly the framework would go wrong. =20 You don't use the device address for transfers but the handle of the device obtained from libusb. =20 Dan. ________________________________ From: lib...@li... [mailto:lib...@li...] On Behalf Of Andrew Xiang Sent: 05 May 2006 02:07 To: lib...@li... Subject: [Libusb-win32-devel] USB_REQ_SET_ADDRESS not implemented I notice that USB_REQ_SET_ADDRESS is not supported, And there is no support for address for the bulkwrite/read? =20 how come? =20 thanks Andrew =20 | 
| 
      
      
      From: Dan E. <Dan...@ne...> - 2006-05-05 09:24:11
      
     | 
| Andrew Xiang wrote: > I don't see the set_configuration 0x0900 come in on the device. > I see all the get_descriptor messages, and also, 0x880 to get the > configuration, but NOT the 0x0900.=20 >=20 > I wonder why? You'll have to provide more description than that for anyone to help. Please clarify what the number are you are quoting, e.g. the whole 8 bytes of the request in order, or name the bytes. Also, when do you see this happening? When you plug the device in, in which case it's just windows interrogating the device, or when you run your code. Dan. | 
| 
      
      
      From: Graeme G. <gr...@ar...> - 2006-05-05 08:26:32
      
     | 
| I've made a little more progress in understanding why I'm having so many troubles getting libusb running. I was under the impression that libusb0.sys needed the DDK to be built, and since I hadn't configured this, it wouldn't be built. It seems that libusb0.sys is built anyway, and this is what the operating system is choking on. If I substitute libusb0.sys from the binary distribution, it works OK, and I'm able to happily hack away at libusb0.dll. I'm using libusb-win32 version 0.1.10.0. I've got MingW 3.2.0-rc-3 installed. I've got the Latest XP DDK installed. I'm on a Windows 2k box. I don't understand how running "gmake DDK_PATH=<DDKDIR>" (where <DDKDIR> os "D:/WINDDK" in my case) is going to work. I can' find a reference to DDK_PATH anywhere, and the build doesn't fail if the path is wrong. It appears that the driver is being linked against MingW/liblibntoskrnl.a, rather than anything from the DDK. The libusb0.sys file that results is exactly the same length as the one in the binary distribution, but the binaries differ in 97 bytes (some presumably time stamp, but not all.) Could the version of MingW I'm using be the problem ? Any other ideas ? thanks, Graeme Gill. | 
| 
      
      
      From: Stephan M. <Ste...@ia...> - 2006-05-05 06:30:16
      
     | 
| > I notice that USB_REQ_SET_ADDRESS is not supported, Addresses are always assigned by the host controller driver not by the device driver, so there is no need for this feature. > And there is no support for address for the bulkwrite/read? What do you mean by this? What address? > > how come? > > thanks > Andrew > | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-05 01:04:48
      
     | 
| I notice that USB_REQ_SET_ADDRESS is not supported, And there is no = support for address for the bulkwrite/read? how come? thanks Andrew | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-05 00:50:14
      
     | 
| I don't see the support for the USB_REQ_SET_ADDRESS? Would you please add the support in there? thanks Andrew | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-04 13:42:41
      
     | 
| I don't see the set_configuration 0x0900 come in on the device. I see all the get_descriptor messages, and also, 0x880 to get the configuration, but NOT the 0x0900. I wonder why? -Andrew ----- Original Message ----- From: "Dan Ellis" <Dan...@ne...> To: <lib...@li...> Sent: Thursday, May 04, 2006 4:44 AM Subject: RE: [Libusb-win32-devel] usb_set_configuration error > Andrew Xiang wrote: > > How come there is not control message going to the USB device when > > doing usb_set_configuration??? > > There is a control message going to the USB device, but windows doesn't > allow it to be sent directly, since changing the configuration of a > device is something which must be administered by the stack, so is done > differently than normal control messsages. > > The DeviceIOControl call tells the driver to tell the USB stack to > change the configuration. > > Dan. > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd_______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > | 
| 
      
      
      From: Dan E. <Dan...@ne...> - 2006-05-04 08:44:16
      
     | 
| Andrew Xiang wrote: > How come there is not control message going to the USB device when > doing usb_set_configuration???=20 There is a control message going to the USB device, but windows doesn't allow it to be sent directly, since changing the configuration of a device is something which must be administered by the stack, so is done differently than normal control messsages. The DeviceIOControl call tells the driver to tell the USB stack to change the configuration. Dan. | 
| 
      
      
      From: Dan E. <Dan...@ne...> - 2006-05-04 08:40:49
      
     | 
| The call to bulk transfer will return an error, i.e. a return code less than 0. It's up to you how you recover. The device behaviour depends upon what chip you are using, but when it's plugged in again the OS will execute a USB reset, so the device will see that. =20 Whether you implement timeouts is completely up to you and your hardware configuration. It's probably a good idea because if the device gets stuck and stops consuming data, the host will keep retrying to send it, and as long as the device has died completely, the host won't stop. =20 Dan. ________________________________ From: lib...@li... [mailto:lib...@li...] On Behalf Of Andrew Xiang Sent: 03 May 2006 21:42 To: lib...@li... Subject: [Libusb-win32-devel] USB unplugged What happens when I am doing data bulk transfer and the USB cable is unplugged? How will the Host software know and recover? And how will the firmware recover. I assume when the host software recover, it can send over RESET tell the device to recover also?=20 =20 I guess it need to put some sort of timeout in the device also for the RX/TX. =20 =20 =20 -Andrew =20 | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-04 01:31:10
      
     | 
| How come there is not control message going to the USB device when doing 
usb_set_configuration???
static int usb_get_configuration(usb_dev_handle *dev)
{
  int ret;
  char config;
  ret = usb_control_msg(dev, USB_RECIP_DEVICE | USB_ENDPOINT_IN,
                        USB_REQ_GET_CONFIGURATION ,
                        0, 0, &config, 1, LIBUSB_DEFAULT_TIMEOUT);
  if(ret >= 0)
    {
      return config;
    }
  return ret;
}
int usb_set_configuration(usb_dev_handle *dev, int configuration)
{
  DWORD sent;
  libusb_request req;
  if(dev->impl_info == INVALID_HANDLE_VALUE)
    {
      usb_error("usb_set_configuration: error: device not open");
      return -EINVAL;
    }
  req.configuration.configuration = configuration;
  req.timeout = LIBUSB_DEFAULT_TIMEOUT;
  if(!DeviceIoControl(dev->impl_info, LIBUSB_IOCTL_SET_CONFIGURATION,
                      &req, sizeof(libusb_request),
                      NULL, 0, &sent, NULL))
    {
      usb_error("usb_set_configuration: could not set config %d: "
                "win error: %s", configuration, usb_win_error_to_string());
      return -usb_win_error_to_errno();
    }
  dev->config = configuration;
  dev->interface = -1;
  dev->altsetting = -1;
  return 0;
}
----- Original Message ----- 
From: "Stephan Meyer" <ste...@we...>
To: <lib...@li...>
Sent: Wednesday, May 03, 2006 3:47 PM
Subject: Re: [Libusb-win32-devel] simple example on bulkread/bulkwrite?
>
>> Does anyone have a simple example of bulkread/bulkwrite?
>>
>
> see attachment.
>
>>
>> Also, why no name show up for the device in the device manager? I ran the 
>> info maker and put in some names, but it did not show up on the device 
>> manager, I am running winxp.
>>
>>
>>
>> thanks
>>
>> Andrew
>>
>>
>
>
> _______________________________________________________________
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
>
> 
 | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-03 20:42:30
      
     | 
| What happens when I am doing data bulk transfer and the USB cable is = unplugged? How will the Host software know and recover? And how will the = firmware recover. I assume when the host software recover, it can send = over RESET tell the device to recover also?=20 I guess it need to put some sort of timeout in the device also for the = RX/TX. -Andrew | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-03 19:59:48
      
     | 
| Hi, Stephan, Thanks!! Also, why no unique name show up for the device in the device manager? I ran the info maker and put in the manufacture names, but it did not show up on the device manager, I am running winxp. -Andrew ----- Original Message ----- From: "Stephan Meyer" <ste...@we...> To: <lib...@li...> Sent: Wednesday, May 03, 2006 3:47 PM Subject: Re: [Libusb-win32-devel] simple example on bulkread/bulkwrite? > > > Does anyone have a simple example of bulkread/bulkwrite? > > > > see attachment. > > > > > Also, why no name show up for the device in the device manager? I ran the info maker and put in some names, but it did not show up on the device manager, I am running winxp. > > > > > > > > thanks > > > > Andrew > > > > > > > _______________________________________________________________ > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > > | 
| 
      
      
      From: Stephan M. <ste...@we...> - 2006-05-03 19:47:33
      
     | 
| > Does anyone have a simple example of bulkread/bulkwrite? > see attachment. > > Also, why no name show up for the device in the device manager? I ran the info maker and put in some names, but it did not show up on the device manager, I am running winxp. > > > > thanks > > Andrew > > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 | 
| 
      
      
      From: Andrew X. <and...@gm...> - 2006-05-03 16:13:35
      
     | 
| Does anyone have a simple example of bulkread/bulkwrite? Also, why no name show up for the device in the device manager? I ran = the info maker and put in some names, but it did not show up on the = device manager, I am running winxp.=20 thanks Andrew | 
| 
      
      
      From: Johannes E. <joh...@er...> - 2006-05-02 17:11:42
      
     | 
| On Tue, May 02, 2006, Graeme Gill <gr...@ar...> wrote: > There seems to be a fundamental shortcoming in the libusb API > definition. There is no way for a call to read() to timeout and > report the number of bytes it read up to the timeout, because > the return value is used for both status reporting, and > reporting the number of bytes it reads. > > By comparison, under MSWindows ReadFile() has a separate status > and number of bytes return, and under Unix, the timeout is > separated by the use of poll() or select() from the > file read() function. > > The libusb read() functions in practice seem to either read a number > of bytes into the caller buffer then return the timeout error > code to signal the timeout, leaving the caller > no way of knowing how many bytes have been read into their > buffer (MSWindows), or simply discard the bytes (OSX) and > returning 0 rather than -ETIMEDOUT. Yes, this is one of the things that is being fixed in libusb 1.0 int libusb_bulk(struct libusb_bulk_request *bulk, size_t *transferred_bytes); > Linux is even more bizarre, it seems to not signal a timeout > at all, but returns 8 (the packet size), and reads the packet > received into the buffer, but subsequent calls to read return > the same packet, over and over. (In fact to get it to return > a timeout error at all, and stop re-reading the same packet, > I had to apply the attached patch to linux.c). What version of libusb are you using? I'm pretty sure there was a bug similar to this that was resolved. It's not exactly clear to me what your patch is doing since some parts look completely wrong. JE | 
| 
      
      
      From: Graeme G. <gr...@ar...> - 2006-05-02 07:27:21
      
     | 
| There seems to be a fundamental shortcoming in the libusb API definition. There is no way for a call to read() to timeout and report the number of bytes it read up to the timeout, because the return value is used for both status reporting, and reporting the number of bytes it reads. By comparison, under MSWindows ReadFile() has a separate status and number of bytes return, and under Unix, the timeout is separated by the use of poll() or select() from the file read() function. The libusb read() functions in practice seem to either read a number of bytes into the caller buffer then return the timeout error code to signal the timeout, leaving the caller no way of knowing how many bytes have been read into their buffer (MSWindows), or simply discard the bytes (OSX) and returning 0 rather than -ETIMEDOUT. Linux is even more bizarre, it seems to not signal a timeout at all, but returns 8 (the packet size), and reads the packet received into the buffer, but subsequent calls to read return the same packet, over and over. (In fact to get it to return a timeout error at all, and stop re-reading the same packet, I had to apply the attached patch to linux.c). Graeme Gill. | 
| 
      
      
      From: <JC...@so...> - 2006-04-27 03:00:10
      
     | 
| DQpIaSBhbGwsDQoNCkkgYW0gdHJ5aW5nIHRvIGRldmVsb3AgYSBoYXJkd2FyZSB1c2ItcnMyMzIg Y29udmVydGVyLg0KDQpXaW5kb3dzIGJhc2VkIGNvbXB1dGVyIHdpdGggdXNiIHBvcnQgPC0+IHVz Yi1yczIzMiBjb252ZXJ0ZXIgPC0+IHJzLTIzMg0Kc2lnbmFscw0KDQpTaW5jZSBJIGFtIHBsYW5u aWcgdG8gdXNlIE1pY3Jvc29mdCBEZXZlbG9wcGVyIFN0dWRpbyA5NywgbWF5IEkgdXNlIHRoaXMN CmNvbXBpbGVyIHdpdGggbGlidXNiLXdpbjMyPw0KSWYgc28gd2hlcmUgY2FuIEkgZmluZCBhIG1h bnVhbCBvbiBob3cgdG8gdXNlIHRoZSBsaWItdXNiLWZ1bmN0aW9ucz8NCg0KVG8gbWFrZSB0aGlu Z3MgbW9yZSBjbGVhcjogIEkgbmVlZCBoZWxwIHRvIG1ha2UgYSAgd2luZG93cyBzb2Z0d2FyZSBp bg0Kb3JkZXIgdG8gdG8gZ2V0IHRob3NlIFJTMjMyIHNpZ25hbHMuDQoNCkFueSBsaW5rIG9yIGhl bHAgd2lsbCBiZSBhcHJlY2lhdGVkIGFuZCBzb3JyeSBpZiBJIGJvdGhlciB3aXRoIHNpbGx5DQpx dWVzdGlvbnMuDQoNCkphdmllcg== | 
| 
      
      
      From: Mark S. <ms...@ya...> - 2006-04-25 18:54:47
      
     | 
| I've written code to update firmware in a keyboard-like device.  Keyboards have an endpoint descriptor already for the LED byte.  You can write pattern sequence that is caught by the target as a programming command.  But I don't know enough about your particular device.
   
  
"Diego ." <di...@gm...> wrote:
    First of all, I would like to thank you for you quick reply to my enquiry.
  
The device is a special keyboard, it have only one key (the user of the PC have access to a one button. So,  he cannot sabotage the PC ). I need send to HID keyboard the active key configuration (for example, the button is an ENTER key or F1 key). And I need to send the firmware to the device for correct the possible bug in the firmware.
  
  best regards.
  
			
---------------------------------
Celebrate Earth Day everyday!  Discover 10 things you can do to help slow climate change. Yahoo! Earth Day | 
| 
      
      
      From: Robert M. <mar...@co...> - 2006-04-25 09:51:18
      
     | 
| Diego . wrote: > The device is a special keyboard, it have only one key (the user of the > PC have access to a one button. So, he cannot sabotage the PC ). I need > send to HID keyboard the active key configuration (for example, the > button is an ENTER key or F1 key). And I need to send the firmware to > the device for correct the possible bug in the firmware. Why do you develop that for yourself? Buy a KeyWarrior chip from us http://www.codemercs.com Our firmware is stable and several versions of the KeyWarrior are programmable. The IO-Warrior 40 Starter Kit is probably what you really need. It is complete wiht a single button to play with. Generating keyboard events from the button read can be done in your application if you need that. | 
| 
      
      
      From: Diego . <di...@gm...> - 2006-04-25 09:38:43
      
     | 
| First of all, I would like to thank you for you quick reply to my enquiry. The device is a special keyboard, it have only one key (the user of the PC have access to a one button. So, he cannot sabotage the PC ). I need send to HID keyboard the active key configuration (for example, the button is an ENTER key or F1 key). And I need to send the firmware to the device for correct the possible bug in the firmware. best regards. | 
| 
      
      
      From: Cory S. <co...@mo...> - 2006-04-24 20:26:33
      
     | 
| On 4/23/06, Jonathon Love - Haltech <jon...@ha...> wrote: > Cory, > > Do you have libftdi and libusb-win32 packaged in the same dll? I have not put them together in a DLL as a Windows driver because there is no need. I have a number of application specific exe's as well as an application specific DLL exposing a JNI interface -- all statically linked with libusb and libftdi. > I'd like to put them in the same dll, but I'd rather avoid figuring out > all the cygwin stuff. (So could I have a copy of yours?) > > Does mingw generate .lib files that VC++ can use? No, it doesn't. Though, I don't use VC++, so I don't really know how it may / may not interoperate with object files and libraries built with in MinGW with GCC. Best, Cory | 
| 
      
      
      From: Jonathon L. - H. <jon...@ha...> - 2006-04-24 07:17:19
      
     | 
| hmm, I'm confused. Quoting http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License [q] The most commonly used method for doing so [using an lgpl library in a proprietary program] is to use "a suitable shared library mechanism for linking". Alternatively, a statically linked library is allowed if either source code or linkable object files are provided. [/q] Surely this means I have to either have it in a dll, or provide object files? Also, looking at the lgpl (section 6) it seems like I have these obligations too. Any thoughts? with thanks Jonathon | 
| 
      
      
      From: Robert M. <mar...@co...> - 2006-04-24 06:26:03
      
     | 
| Diego . wrote: > I have programed an HID keyboard, but I need to send some configuration > bytes and the firmware that will be save into a eeprom. I'm thinking to > include one bulk endpoint into descriptors. But, how to communicate with > my "custom HID device" using the libusb? When I plug my device windows > uses his HID driver. Could I use libusb to perform a bulk transfer when > my HID device is under windows driver? Sending data to a HID keyboard is possible with the Windows HID driver if you use feature reports. Why do you want to change the firmware of a keyboard? Have a look at http://www.codemercs.com for a nice range of USB keyboard controllers. | 
| 
      
      
      From: Diego . <di...@gm...> - 2006-04-24 06:17:10
      
     | 
| Hello, I have programed an HID keyboard, but I need to send some configuration bytes and the firmware that will be save into a eeprom. I'm thinking to include one bulk endpoint into descriptors. But, how to communicate with my "custom HID device" using the libusb? When I plug my device windows uses hi= s HID driver. Could I use libusb to perform a bulk transfer when my HID devic= e is under windows driver? Thank, | 
| 
      
      
      From: Linus W. <tr...@df...> - 2006-04-24 05:36:26
      
     | 
| On Mon, 24 Apr 2006, Jonathon Love - Haltech wrote: LGPL questions? See http://www.gnu.org/copyleft/lesser.html http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License > In order to pass, along with our program we must provide: > > - object files (.lib files for VC++) for all our code No. > - libusb-win32 packaged in a separate dll (so our code isn't staticly linked > with it) No, static linking is OK. > - source code for libusb-win32 No, giving a reference to where it can be obtained like saying "it's on http://libusb-win32.sourceforge.net/ is OK, unless you changed some of libusb-win32 source code yourselves, in that case you have to provide a pointer to where the source code can be obtained. > - prominent notices saying that sections of our program are released under > the LGPL If you by "your program" refer to a bundle including portions of libusb-win32 then Yes. The typical way to do it is to say that it contains the LGPL library libusb-win32 and tell users where it may be downloaded. > - none of our own source code Correct, that's how LGPL works. Linus |