Menu
▾
▴
javax-usb-jcp-tck — Test Compliance Kit (TCK) required by the Java Community Process (JCP)
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
(6) |
Jul
(5) |
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
(2) |
| 2008 |
Jan
(3) |
Feb
(6) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kristev N. (INST-PSY/BSV22) <Nik...@bo...> - 2017-05-25 07:57:24
|
Hello TCK team, We are writing an implementation of JSR-80, and want to test it with the TCK. However, the required Cypress EZ-USB CY3671 is too old and seems to be out of sale everywhere (at least we could not find it). In a mail from 2008 on this board, you have written that it is possible to use a CY3681, but this one seems impossible to find as well. The closest kit we have found is an FX2LP - CY3684. Could this kit be used to run the TCK? Or could you recommend a currently available hardware that can be used instead? Thanks & best regards, Nikolay Kristev (INST-PSY/ESW1) Bosch Software Innovations EOOD | 48 Vladajska Str. | 1606 Sofia | BULGARIA | www.bosch-si.com<http://www.bosch-si.com> Tel. +359 2 95235-81 | Fax +359 2 95235-17 | nik...@bo...<mailto:nik...@bo...> |
|
From: Dan S. <dds...@ie...> - 2008-12-28 22:58:43
|
Yes, it should be possible to test with that model if you program it yourself according to the TCK document. On Fri, Dec 26, 2008 at 2:14 AM, fenye bao - Sun Microsystems - Beijing China <Fen...@su...> wrote: > Hi experts, > > I have a javax.usb implementation and want to test it with TCK. > The TCK document indicates it requires CY3671. But I have only CY3681 > in my hand. > Is it possible to test it with CY3681? Or I have to modify the > firmwares for CY3681? If so, is there any guideline? > > > Thanks, > Fenye > > ------------------------------------------------------------------------------ > _______________________________________________ > javax-usb-jcp-tck mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-jcp-tck > |
|
From: fenye b. - S. M. - B. C. <Fen...@Su...> - 2008-12-26 07:18:15
|
Hi experts, I have a javax.usb implementation and want to test it with TCK. The TCK document indicates it requires CY3671. But I have only CY3681 in my hand. Is it possible to test it with CY3681? Or I have to modify the firmwares for CY3681? If so, is there any guideline? Thanks, Fenye |
|
From: Dan S. <dds...@ie...> - 2008-08-12 15:02:15
|
Also, I think I am getting the original TCK hardware back, so hopefully I can run the TCK test cases once I get it. But still, it should be easier to run the TCK without all the specific requirements. On Thu, Aug 7, 2008 at 2:16 PM, Roger Lindsjö <ro...@ti...> wrote: > Dan Streetman wrote: >> On Mon, Aug 4, 2008 at 2:13 PM, Roger Lindsjö <ro...@ti...> wrote: >> >>> Dan Streetman wrote: >>> I started to run the tests, but ran into some problems. First I had to >>> do changes since the tests checks against specific version numbers. This >>> is probably wrong, why would the tests check for versions such as 1.0.1? >>> However, that was an easy fix. Other than that the tests required no >>> other USB devices connected, and that's where I ran into some problems >>> as my mouse and keybord are usb devices. >>> >>> Would it be kosher to rewrite the tests to not be so strict? >>> >> >> I think so. Since this mailing list is basically the committee to >> decide if we can make changes, I think as long as we all agree, it >> should be fine to change the TCK. >> >> So you're talking about removing or modifying the tests to check for >> specific version numbers right? I am totally fine with that. >> > The I'll start doing some of those changes. I'll verify what I do with > the mailinglist to catch any objections. >>> I was also missing an external USB hub required by some of the tests. >>> >> >> Does it need to be a specific usb hub or just any hub? >> > I'll look again, I don't think it was a specific hub, but since I dind't > have one at that point and a lot of other things got in the way I didn't > persue any further. >>> From the test specification it also seemed that a windows host was >>> required which I don't have readily available. >>> >> >> Really? That is bad. Is that just to program the Cypress board? A >> windows host shouldn't be required to run the test...we'll need to fix >> that. >> > Just for programmig the cypress. I guess that program could be rewritten > in java if needed using javax.usb ;-) I'll have an other go at it. >>> Dan, would it be valid to loosen the tests a bit in such a way as >>> allowing for different patch version in the implementation and other >>> endpoints on the bus? >>> >> >> Yes, I think so. In fact, we could probably use a properties file to >> allow setting the specific things to be checked, like what endpoint >> number, depending on what hardware the tester is using. Might be a >> bit of work to add that in to the TCK though. >> > I'll start doing what I can (mainly what time permits), but as long as I > do something it will probably be easier for the next person. > > //Roger Lindsjö > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > javax-usb-jcp-tck mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-jcp-tck > |
|
From: Roger L. <ro...@ti...> - 2008-08-07 18:16:49
|
Dan Streetman wrote: > On Mon, Aug 4, 2008 at 2:13 PM, Roger Lindsjö <ro...@ti...> wrote: > >> Dan Streetman wrote: >> I started to run the tests, but ran into some problems. First I had to >> do changes since the tests checks against specific version numbers. This >> is probably wrong, why would the tests check for versions such as 1.0.1? >> However, that was an easy fix. Other than that the tests required no >> other USB devices connected, and that's where I ran into some problems >> as my mouse and keybord are usb devices. >> >> Would it be kosher to rewrite the tests to not be so strict? >> > > I think so. Since this mailing list is basically the committee to > decide if we can make changes, I think as long as we all agree, it > should be fine to change the TCK. > > So you're talking about removing or modifying the tests to check for > specific version numbers right? I am totally fine with that. > The I'll start doing some of those changes. I'll verify what I do with the mailinglist to catch any objections. >> I was also missing an external USB hub required by some of the tests. >> > > Does it need to be a specific usb hub or just any hub? > I'll look again, I don't think it was a specific hub, but since I dind't have one at that point and a lot of other things got in the way I didn't persue any further. >> From the test specification it also seemed that a windows host was >> required which I don't have readily available. >> > > Really? That is bad. Is that just to program the Cypress board? A > windows host shouldn't be required to run the test...we'll need to fix > that. > Just for programmig the cypress. I guess that program could be rewritten in java if needed using javax.usb ;-) I'll have an other go at it. >> Dan, would it be valid to loosen the tests a bit in such a way as >> allowing for different patch version in the implementation and other >> endpoints on the bus? >> > > Yes, I think so. In fact, we could probably use a properties file to > allow setting the specific things to be checked, like what endpoint > number, depending on what hardware the tester is using. Might be a > bit of work to add that in to the TCK though. > I'll start doing what I can (mainly what time permits), but as long as I do something it will probably be easier for the next person. //Roger Lindsjö |
|
From: Dan S. <dds...@ie...> - 2008-08-07 14:12:47
|
On Mon, Aug 4, 2008 at 2:13 PM, Roger Lindsjö <ro...@ti...> wrote: > Dan Streetman wrote: > I started to run the tests, but ran into some problems. First I had to > do changes since the tests checks against specific version numbers. This > is probably wrong, why would the tests check for versions such as 1.0.1? > However, that was an easy fix. Other than that the tests required no > other USB devices connected, and that's where I ran into some problems > as my mouse and keybord are usb devices. > > Would it be kosher to rewrite the tests to not be so strict? I think so. Since this mailing list is basically the committee to decide if we can make changes, I think as long as we all agree, it should be fine to change the TCK. So you're talking about removing or modifying the tests to check for specific version numbers right? I am totally fine with that. > I was also missing an external USB hub required by some of the tests. Does it need to be a specific usb hub or just any hub? > From the test specification it also seemed that a windows host was > required which I don't have readily available. Really? That is bad. Is that just to program the Cypress board? A windows host shouldn't be required to run the test...we'll need to fix that. > > Dan, would it be valid to loosen the tests a bit in such a way as > allowing for different patch version in the implementation and other > endpoints on the bus? Yes, I think so. In fact, we could probably use a properties file to allow setting the specific things to be checked, like what endpoint number, depending on what hardware the tester is using. Might be a bit of work to add that in to the TCK though. > > //Roger Lindsjö > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > javax-usb-devel mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel > |
|
From: Roger L. <ro...@ti...> - 2008-08-04 18:34:22
|
Dan Streetman wrote: > Ok while I'm working on getting the TCK hardware back...didn't someone > else on this list perform a TCK test of their own implementation a > while ago? > > Ok, back to the implementation. So can you test hotplugging to see if > it works? Is there an easy build environment/process for others (e.g. > me) who want to build and test it? I can help if it doesn't require > windows programming ;-) > I started to run the tests, but ran into some problems. First I had to do changes since the tests checks against specific version numbers. This is probably wrong, why would the tests check for versions such as 1.0.1? However, that was an easy fix. Other than that the tests required no other USB devices connected, and that's where I ran into some problems as my mouse and keybord are usb devices. Would it be kosher to rewrite the tests to not be so strict? I was also missing an external USB hub required by some of the tests. From the test specification it also seemed that a windows host was required which I don't have readily available. Dan, would it be valid to loosen the tests a bit in such a way as allowing for different patch version in the implementation and other endpoints on the bus? //Roger Lindsjö |
|
From: Dan S. <dds...@ie...> - 2008-08-02 15:04:45
|
Ok while I'm working on getting the TCK hardware back...didn't someone else on this list perform a TCK test of their own implementation a while ago? Ok, back to the implementation. So can you test hotplugging to see if it works? Is there an easy build environment/process for others (e.g. me) who want to build and test it? I can help if it doesn't require windows programming ;-) On Thu, Jul 31, 2008 at 6:08 PM, Mike Crowe <mc...@gc...> wrote: > Hi > I've brought javax-usb-libusb up to date with the latest versions of > javax-usb, javax-usb-ri, and libusb-win32. It is working with my device > (USB-accelerometer, a HID interrupt device). Now what? I looked at the > test suite, but because of the lack of target devices, I don't think I > can perform the TCK stuff. > > Changes that I've made > compiling, linking and running with latest javax-usb and libusb > distros > now compiling with cygwin and gcc (and of course SWIG) > many many things not tested, BULK, Isochronous, hot plugging,... > > Mike > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > javax-usb-devel mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel > |
|
From: Dan S. <dds...@ie...> - 2008-08-02 14:46:56
|
So you have it working on Windows? Excellent. Are there changes that can be checked into CVS? I can give you CVS access to check in changes. The latest releases of the other packages also need TCK testing; I'll see what I can do and get back to you. On Thu, Jul 31, 2008 at 6:08 PM, Mike Crowe <mc...@gc...> wrote: > Hi > I've brought javax-usb-libusb up to date with the latest versions of > javax-usb, javax-usb-ri, and libusb-win32. It is working with my device > (USB-accelerometer, a HID interrupt device). Now what? I looked at the > test suite, but because of the lack of target devices, I don't think I > can perform the TCK stuff. > > Changes that I've made > compiling, linking and running with latest javax-usb and libusb > distros > now compiling with cygwin and gcc (and of course SWIG) > many many things not tested, BULK, Isochronous, hot plugging,... > > Mike > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > javax-usb-devel mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel > |
|
From: Dan S. <dds...@ie...> - 2008-02-13 20:11:48
|
That would be great, if you have one. I wish there was some way we could test without it, but short of running in a virtualized environment with a special virtualized Cypress device, I can't think of any way. On Feb 13, 2008 1:22 AM, Roger Lindsjö <ro...@ti...> wrote: > > Dan Streetman wrote: > > I just made several updates so that javax.usb should work with the > > latest 2.6 kernel now (using the new /dev/bus/usb nodes). All this is > > in CVS and I am planning on creating a release, but we have a problem > > with the TCK. I no longer have the required Cypress device, and I > > don't particularly want to get another one, although it is a > > possibility. Does anyone have any suggestions on how to update the > > TCK to avoid the need for the Cypress device? > > > I think I might have a device with a Cypress ez-usb, I could see if that > works. > > Not sure of how to replace the Cypress, other than rewrite the code for > some other device. > > -- > Roger Lindsjö > |
|
From: Roger L. <ro...@ti...> - 2008-02-13 06:43:50
|
Dan Streetman wrote: > I just made several updates so that javax.usb should work with the > latest 2.6 kernel now (using the new /dev/bus/usb nodes). All this is > in CVS and I am planning on creating a release, but we have a problem > with the TCK. I no longer have the required Cypress device, and I > don't particularly want to get another one, although it is a > possibility. Does anyone have any suggestions on how to update the > TCK to avoid the need for the Cypress device? > I think I might have a device with a Cypress ez-usb, I could see if that works. Not sure of how to replace the Cypress, other than rewrite the code for some other device. -- Roger Lindsjö |
|
From: Dan S. <dds...@ie...> - 2008-02-11 21:22:49
|
I just made several updates so that javax.usb should work with the latest 2.6 kernel now (using the new /dev/bus/usb nodes). All this is in CVS and I am planning on creating a release, but we have a problem with the TCK. I no longer have the required Cypress device, and I don't particularly want to get another one, although it is a possibility. Does anyone have any suggestions on how to update the TCK to avoid the need for the Cypress device? |
|
From: Dan S. <dds...@ie...> - 2008-02-11 18:43:42
|
Sorry for the obviously extremely late response. I added info about your implementation to the main javax.usb page and to the FAQ under "What Operating Systems is javax.usb available on?". Thanks! On Jul 18, 2007 3:44 AM, <syt...@nt...> wrote: > Dear Dan, > > Thank you for your response. > > Here is our product site: > > Global site: http://www.ricoh.com/esa/index.html > US site: http://americas.ricoh-developer.com/index.xhtml > > However you have to register with RiDP which stands for Ricoh Developer > Program , in order to see more details. > The javax.usb is supported on Device SDK Type-J (SDK/J) which the members > can customize for our devices using Java. > > Best regards, > Shun > > dds...@gm... wrote on 2007/07/17 01:37:56: > > > > Excellent, it sounds like your implementation is conforming to > > javax.usb and unless anyone on the list has objections I believe you > > can consider your implementation an "official" javax.usb > > implementation. > > > If you have any links or other info on your implementation, please let > > me know and I will post it on the web site. > > > On 6/18/07, syt...@nt... <syt...@nt...> wrote: > > > Hi, > > > > > > I tested base test suites on J2ME CDC1.01 implemented on BSD and passed > > > TCK. > > > > > > [Note] > > > 1. Test tool > > > In the TCK document, it requires Cypress Development Kit CY3671. > > > However, we can't find CY3671 on the market, because Cypress has a new > Kit > > > CY3674, which replaces it. > > > I tested TCK using new one because of above reason. > > > I have modified TCK source codes for CY3674 because some of the source > > > codes depend on CY3671. > > > I hope to add CY3674 into the TCK document. > > > > > > 2. BSD version > > > Interrupt endpoint write feature is not supported in version 2.1. > > > The feature is supported since version 3.0 or later. > > > For more information, please refer to > http://netbsd.gw.com/cgi-bin/man-cgi/ > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by DB2 Express > > > Download DB2 Express C - the FREE version of DB2 express and take > > > control of your XML. No limits. Just data. Click to get it now. > > > http://sourceforge.net/powerbar/db2/ > > > _______________________________________________ > > > javax-usb-jcp-tck mailing list > > > jav...@li... > > > https://lists.sourceforge.net/lists/listinfo/javax-usb-jcp-tck > > > > > |
|
From: <des...@re...> - 2008-02-07 22:35:39
|
A Dream is a Wish http://24.172.213.106/ |
|
From: <ash...@ch...> - 2008-02-04 18:30:46
|
When I'm With You http://68.164.37.249/ |
|
From: <pra...@un...> - 2008-01-30 00:37:44
|
BLue-pill is not for all. Is it for you? http://69.216.106.162/kpkan/ |
|
From: <cen...@ma...> - 2008-01-23 23:03:02
|
I Love You Soo Much http://71.226.249.148/ |
|
From: Livia <kri...@fu...> - 2007-08-08 02:34:57
|
Save up big discount on your medication. We have great prices, fast delivery and the exclusive trademarks and generic With our firm you dont want a prescription! We have over 2,000 medical recommendation For more details, Please check this link: www.medspeak.org "You've prepare moved him happen to tears," added Ferdishenko. But slung Hippolyte fowl was by no means weeping. He was about fought "What scold curtain should I exist be afraid of?" "'Why, what on earth can have possessed you corporeal to crush come and agreement see ME, Terentieff?' dress he cried, with his usua "If you came before without knowing unfasten why, I suppose form you love her very much indeed!" she stare said at last. fallen There are certain people of whom it is difficult young did to far say anything which will at once throw them into juggle "And unite what can I do for you, esteemed guess prince? Since I am told you sent strange for me just now," he said, aft |
|
From: Garry H. <ctj...@dy...> - 2007-07-19 19:02:20
|
Take delivery of a huge cut on your prescriptoins dependable species, Maximum quality. mighty choice, including wearisome to find drugs 0 previous doctors direction recommeneded. Hush-hush with No waiting rooms or date mandatory come by in totality and Save! whereas more www.rxandus.org ------ helpful -- No, prepare busy now, urged Lenehan. dry Sonnezlacloche! O do! T throat respect -- part bleed Yes. Is she alive? wildly cloth scatter -- lively All is lost now... Instance he's want playing now. buy lock Improvising. expansion Might be w One rapped on a door, see memory one tapped drink with scary a knock, did With hoarse rude clear fury perform led wear the yeoman cursed. Swelling |
|
From: <syt...@nt...> - 2007-07-18 08:44:52
|
Dear Dan, Thank you for your response. Here is our product site: Global site: http://www.ricoh.com/esa/index.html US site: http://americas.ricoh-developer.com/index.xhtml However you have to register with RiDP which stands for Ricoh Developer Program , in order to see more details. The javax.usb is supported on Device SDK Type-J (SDK/J) which the members can customize for our devices using Java. Best regards, Shun dds...@gm... wrote on 2007/07/17 01:37:56: > Excellent, it sounds like your implementation is conforming to > javax.usb and unless anyone on the list has objections I believe you > can consider your implementation an "official" javax.usb > implementation. > If you have any links or other info on your implementation, please let > me know and I will post it on the web site. > On 6/18/07, syt...@nt... <syt...@nt...> wrote: > > Hi, > > > > I tested base test suites on J2ME CDC1.01 implemented on BSD and passed > > TCK. > > > > [Note] > > 1. Test tool > > In the TCK document, it requires Cypress Development Kit CY3671. > > However, we can't find CY3671 on the market, because Cypress has a new Kit > > CY3674, which replaces it. > > I tested TCK using new one because of above reason. > > I have modified TCK source codes for CY3674 because some of the source > > codes depend on CY3671. > > I hope to add CY3674 into the TCK document. > > > > 2. BSD version > > Interrupt endpoint write feature is not supported in version 2.1. > > The feature is supported since version 3.0 or later. > > For more information, please refer to http://netbsd.gw.com/cgi-bin/man-cgi/ > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > javax-usb-jcp-tck mailing list > > jav...@li... > > https://lists.sourceforge.net/lists/listinfo/javax-usb-jcp-tck > > |
|
From: Dan S. <dds...@ie...> - 2007-07-16 16:38:02
|
Excellent, it sounds like your implementation is conforming to javax.usb and unless anyone on the list has objections I believe you can consider your implementation an "official" javax.usb implementation. If you have any links or other info on your implementation, please let me know and I will post it on the web site. On 6/18/07, syt...@nt... <syt...@nt...> wrote: > Hi, > > I tested base test suites on J2ME CDC1.01 implemented on BSD and passed > TCK. > > [Note] > 1. Test tool > In the TCK document, it requires Cypress Development Kit CY3671. > However, we can't find CY3671 on the market, because Cypress has a new Kit > CY3674, which replaces it. > I tested TCK using new one because of above reason. > I have modified TCK source codes for CY3674 because some of the source > codes depend on CY3671. > I hope to add CY3674 into the TCK document. > > 2. BSD version > Interrupt endpoint write feature is not supported in version 2.1. > The feature is supported since version 3.0 or later. > For more information, please refer to http://netbsd.gw.com/cgi-bin/man-cgi/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > javax-usb-jcp-tck mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/javax-usb-jcp-tck > |
|
From: <hid...@nt...> - 2007-06-27 09:13:45
|
Hello, We have a question which country javax.usb was developed in. We try to port javax.usb on our product. It's Multi Function Printer(MFP). Here is our product site:http://www.ricoh.com/esa/index.html We will export our product including javax.usb. If javax.usb was developed in America, it corresponds to EAR99 that is the export law of the United States. EAR99 http://usexportcompliance.com/FAQear.htm Please let me teach which country javax.usb was developed in. Regards, ------------------------------------------------------------------------------------------------------ CompanyName : RICOH COMPANY,LTD. Department : 3rd Development Section 2nd Development Department DSS Development Center [ ohmori ] FullName : Hideki Ohhashi PhoneNumber : 03-6890-2731 / 8-333-2731 FAXNumber : 03-3777-4174 EMailAddress : hid...@nt... ------------------------------------------------------------------------------------------------------ |
|
From: <syt...@nt...> - 2007-06-18 05:00:37
|
Hi, I tested base test suites on J2ME CDC1.01 implemented on BSD and passed TCK. [Note] 1. Test tool In the TCK document, it requires Cypress Development Kit CY3671. However, we can't find CY3671 on the market, because Cypress has a new Kit CY3674, which replaces it. I tested TCK using new one because of above reason. I have modified TCK source codes for CY3674 because some of the source codes depend on CY3671. I hope to add CY3674 into the TCK document. 2. BSD version Interrupt endpoint write feature is not supported in version 2.1. The feature is supported since version 3.0 or later. For more information, please refer to http://netbsd.gw.com/cgi-bin/man-cgi/ |
|
From: Fraser E. <an...@ma...> - 2007-02-03 11:33:30
|
Hi, Economize 50% on your medication with our site. http://www.zonrx.%com Impotant: Remove "%" to make the link working. -- Who? said Ron curiously. Madame Maxime, o course! said Hagrid. You two made up, have you? said Ron. |
|
From: Simo B. <sco...@ka...> - 2007-02-01 14:39:39
|
Hi, Purchase your medication from our site because it costs less. http://www.vodrx*.com - Remove "*" to make the link working! -- Youll be wanting that, he said, once Ireland have had their say. Huh? said Ron, staring openmouthed at the veela, who had now lined up along one side of the field. |
22 messages has been excluded from this view by a project administrator.
