Author: pluto Date: Thu Mar 10 23:34:19 2005 GMT Module: SOURCES Tag: LINUX_2_6 ---- Log message: - iRiver's iFP portable music players.
---- Files affected: SOURCES: iriverfs-r0.1.0.1.patch (NONE -> 1.1.2.1) (NEW) ---- Diffs: ================================================================ Index: SOURCES/iriverfs-r0.1.0.1.patch diff -u /dev/null SOURCES/iriverfs-r0.1.0.1.patch:1.1.2.1 --- /dev/null Fri Mar 11 00:34:19 2005 +++ SOURCES/iriverfs-r0.1.0.1.patch Fri Mar 11 00:34:14 2005 @@ -0,0 +1,5944 @@ +diff -uprN -X ../dontdiff linux-2.6.9/COPYING.iriverfs linux-2.6.9-iriverfs-stable/COPYING.iriverfs +--- linux-2.6.9/COPYING.iriverfs 1969-12-31 19:00:00.000000000 -0500 ++++ linux-2.6.9-iriverfs-stable/COPYING.iriverfs 2004-10-23 11:42:21.000000000 -0400 +@@ -0,0 +1,341 @@ ++ ++ GNU GENERAL PUBLIC LICENSE ++ Version 2, June 1991 ++ ++ Copyright (C) 1989, 1991 Free Software Foundation, Inc. ++ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ++ Everyone is permitted to copy and distribute verbatim copies ++ of this license document, but changing it is not allowed. ++ ++ Preamble ++ ++ The licenses for most software are designed to take away your ++freedom to share and change it. By contrast, the GNU General Public ++License is intended to guarantee your freedom to share and change free ++software--to make sure the software is free for all its users. This ++General Public License applies to most of the Free Software ++Foundation's software and to any other program whose authors commit to ++using it. (Some other Free Software Foundation software is covered by ++the GNU Library General Public License instead.) You can apply it to ++your programs, too. ++ ++ When we speak of free software, we are referring to freedom, not ++price. Our General Public Licenses are designed to make sure that you ++have the freedom to distribute copies of free software (and charge for ++this service if you wish), that you receive source code or can get it ++if you want it, that you can change the software or use pieces of it ++in new free programs; and that you know you can do these things. ++ ++ To protect your rights, we need to make restrictions that forbid ++anyone to deny you these rights or to ask you to surrender the rights. ++These restrictions translate to certain responsibilities for you if you ++distribute copies of the software, or if you modify it. ++ ++ For example, if you distribute copies of such a program, whether ++gratis or for a fee, you must give the recipients all the rights that ++you have. You must make sure that they, too, receive or can get the ++source code. And you must show them these terms so they know their ++rights. ++ ++ We protect your rights with two steps: (1) copyright the software, and ++(2) offer you this license which gives you legal permission to copy, ++distribute and/or modify the software. ++ ++ Also, for each author's protection and ours, we want to make certain ++that everyone understands that there is no warranty for this free ++software. If the software is modified by someone else and passed on, we ++want its recipients to know that what they have is not the original, so ++that any problems introduced by others will not reflect on the original ++authors' reputations. ++ ++ Finally, any free program is threatened constantly by software ++patents. We wish to avoid the danger that redistributors of a free ++program will individually obtain patent licenses, in effect making the ++program proprietary. To prevent this, we have made it clear that any ++patent must be licensed for everyone's free use or not licensed at all. ++ ++ The precise terms and conditions for copying, distribution and ++modification follow. ++ ++ GNU GENERAL PUBLIC LICENSE ++ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION ++ ++ 0. This License applies to any program or other work which contains ++a notice placed by the copyright holder saying it may be distributed ++under the terms of this General Public License. The "Program", below, ++refers to any such program or work, and a "work based on the Program" ++means either the Program or any derivative work under copyright law: ++that is to say, a work containing the Program or a portion of it, ++either verbatim or with modifications and/or translated into another ++language. (Hereinafter, translation is included without limitation in ++the term "modification".) Each licensee is addressed as "you". ++ ++Activities other than copying, distribution and modification are not ++covered by this License; they are outside its scope. The act of ++running the Program is not restricted, and the output from the Program ++is covered only if its contents constitute a work based on the ++Program (independent of having been made by running the Program). ++Whether that is true depends on what the Program does. ++ ++ 1. You may copy and distribute verbatim copies of the Program's ++source code as you receive it, in any medium, provided that you ++conspicuously and appropriately publish on each copy an appropriate ++copyright notice and disclaimer of warranty; keep intact all the ++notices that refer to this License and to the absence of any warranty; ++and give any other recipients of the Program a copy of this License ++along with the Program. ++ ++You may charge a fee for the physical act of transferring a copy, and ++you may at your option offer warranty protection in exchange for a fee. ++ ++ 2. You may modify your copy or copies of the Program or any portion ++of it, thus forming a work based on the Program, and copy and ++distribute such modifications or work under the terms of Section 1 ++above, provided that you also meet all of these conditions: ++ ++ a) You must cause the modified files to carry prominent notices ++ stating that you changed the files and the date of any change. ++ ++ b) You must cause any work that you distribute or publish, that in ++ whole or in part contains or is derived from the Program or any ++ part thereof, to be licensed as a whole at no charge to all third ++ parties under the terms of this License. ++ ++ c) If the modified program normally reads commands interactively ++ when run, you must cause it, when started running for such ++ interactive use in the most ordinary way, to print or display an ++ announcement including an appropriate copyright notice and a ++ notice that there is no warranty (or else, saying that you provide ++ a warranty) and that users may redistribute the program under ++ these conditions, and telling the user how to view a copy of this ++ License. (Exception: if the Program itself is interactive but ++ does not normally print such an announcement, your work based on ++ the Program is not required to print an announcement.) ++ ++These requirements apply to the modified work as a whole. If ++identifiable sections of that work are not derived from the Program, ++and can be reasonably considered independent and separate works in ++themselves, then this License, and its terms, do not apply to those ++sections when you distribute them as separate works. But when you ++distribute the same sections as part of a whole which is a work based ++on the Program, the distribution of the whole must be on the terms of ++this License, whose permissions for other licensees extend to the ++entire whole, and thus to each and every part regardless of who wrote it. ++ ++Thus, it is not the intent of this section to claim rights or contest ++your rights to work written entirely by you; rather, the intent is to ++exercise the right to control the distribution of derivative or ++collective works based on the Program. ++ ++In addition, mere aggregation of another work not based on the Program ++with the Program (or with a work based on the Program) on a volume of ++a storage or distribution medium does not bring the other work under ++the scope of this License. ++ ++ 3. You may copy and distribute the Program (or a work based on it, ++under Section 2) in object code or executable form under the terms of ++Sections 1 and 2 above provided that you also do one of the following: ++ ++ a) Accompany it with the complete corresponding machine-readable ++ source code, which must be distributed under the terms of Sections ++ 1 and 2 above on a medium customarily used for software interchange; or, ++ ++ b) Accompany it with a written offer, valid for at least three ++ years, to give any third party, for a charge no more than your ++ cost of physically performing source distribution, a complete ++ machine-readable copy of the corresponding source code, to be ++ distributed under the terms of Sections 1 and 2 above on a medium ++ customarily used for software interchange; or, ++ ++ c) Accompany it with the information you received as to the offer ++ to distribute corresponding source code. (This alternative is ++ allowed only for noncommercial distribution and only if you ++ received the program in object code or executable form with such ++ an offer, in accord with Subsection b above.) ++ ++The source code for a work means the preferred form of the work for ++making modifications to it. For an executable work, complete source ++code means all the source code for all modules it contains, plus any ++associated interface definition files, plus the scripts used to ++control compilation and installation of the executable. However, as a ++special exception, the source code distributed need not include ++anything that is normally distributed (in either source or binary ++form) with the major components (compiler, kernel, and so on) of the ++operating system on which the executable runs, unless that component ++itself accompanies the executable. ++ ++If distribution of executable or object code is made by offering ++access to copy from a designated place, then offering equivalent ++access to copy the source code from the same place counts as ++distribution of the source code, even though third parties are not ++compelled to copy the source along with the object code. ++ ++ 4. You may not copy, modify, sublicense, or distribute the Program ++except as expressly provided under this License. Any attempt ++otherwise to copy, modify, sublicense or distribute the Program is ++void, and will automatically terminate your rights under this License. ++However, parties who have received copies, or rights, from you under ++this License will not have their licenses terminated so long as such ++parties remain in full compliance. ++ ++ 5. You are not required to accept this License, since you have not ++signed it. However, nothing else grants you permission to modify or ++distribute the Program or its derivative works. These actions are ++prohibited by law if you do not accept this License. Therefore, by ++modifying or distributing the Program (or any work based on the ++Program), you indicate your acceptance of this License to do so, and ++all its terms and conditions for copying, distributing or modifying ++the Program or works based on it. ++ ++ 6. Each time you redistribute the Program (or any work based on the ++Program), the recipient automatically receives a license from the ++original licensor to copy, distribute or modify the Program subject to ++these terms and conditions. You may not impose any further ++restrictions on the recipients' exercise of the rights granted herein. ++You are not responsible for enforcing compliance by third parties to ++this License. ++ ++ 7. If, as a consequence of a court judgment or allegation of patent ++infringement or for any other reason (not limited to patent issues), ++conditions are imposed on you (whether by court order, agreement or ++otherwise) that contradict the conditions of this License, they do not ++excuse you from the conditions of this License. If you cannot ++distribute so as to satisfy simultaneously your obligations under this ++License and any other pertinent obligations, then as a consequence you ++may not distribute the Program at all. For example, if a patent ++license would not permit royalty-free redistribution of the Program by ++all those who receive copies directly or indirectly through you, then ++the only way you could satisfy both it and this License would be to ++refrain entirely from distribution of the Program. ++ ++If any portion of this section is held invalid or unenforceable under ++any particular circumstance, the balance of the section is intended to ++apply and the section as a whole is intended to apply in other ++circumstances. ++ ++It is not the purpose of this section to induce you to infringe any ++patents or other property right claims or to contest validity of any ++such claims; this section has the sole purpose of protecting the ++integrity of the free software distribution system, which is ++implemented by public license practices. Many people have made ++generous contributions to the wide range of software distributed ++through that system in reliance on consistent application of that ++system; it is up to the author/donor to decide if he or she is willing ++to distribute software through any other system and a licensee cannot ++impose that choice. ++ ++This section is intended to make thoroughly clear what is believed to ++be a consequence of the rest of this License. ++ ++ 8. If the distribution and/or use of the Program is restricted in ++certain countries either by patents or by copyrighted interfaces, the ++original copyright holder who places the Program under this License ++may add an explicit geographical distribution limitation excluding ++those countries, so that distribution is permitted only in or among ++countries not thus excluded. In such case, this License incorporates ++the limitation as if written in the body of this License. ++ ++ 9. The Free Software Foundation may publish revised and/or new versions ++of the General Public License from time to time. Such new versions will ++be similar in spirit to the present version, but may differ in detail to ++address new problems or concerns. ++ ++Each version is given a distinguishing version number. If the Program ++specifies a version number of this License which applies to it and "any ++later version", you have the option of following the terms and conditions ++either of that version or of any later version published by the Free ++Software Foundation. If the Program does not specify a version number of ++this License, you may choose any version ever published by the Free Software ++Foundation. ++ ++ 10. If you wish to incorporate parts of the Program into other free ++programs whose distribution conditions are different, write to the author ++to ask for permission. For software which is copyrighted by the Free ++Software Foundation, write to the Free Software Foundation; we sometimes ++make exceptions for this. Our decision will be guided by the two goals ++of preserving the free status of all derivatives of our free software and ++of promoting the sharing and reuse of software generally. ++ ++ NO WARRANTY ++ ++ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY ++FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN ++OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES ++PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED ++OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ++MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS ++TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE ++PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, ++REPAIR OR CORRECTION. ++ ++ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING ++WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR ++REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, ++INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING ++OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED ++TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY ++YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER ++PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE ++POSSIBILITY OF SUCH DAMAGES. ++ ++ END OF TERMS AND CONDITIONS ++ ++ How to Apply These Terms to Your New Programs ++ ++ If you develop a new program, and you want it to be of the greatest ++possible use to the public, the best way to achieve this is to make it ++free software which everyone can redistribute and change under these terms. ++ ++ To do so, attach the following notices to the program. It is safest ++to attach them to the start of each source file to most effectively ++convey the exclusion of warranty; and each file should have at least ++the "copyright" line and a pointer to where the full notice is found. ++ ++ <one line to give the program's name and a brief idea of what it does.> ++ Copyright (C) <year> <name of author> ++ ++ This program is free software; you can redistribute it and/or modify ++ it under the terms of the GNU General Public License as published by ++ the Free Software Foundation; either version 2 of the License, or ++ (at your option) any later version. ++ ++ This program is distributed in the hope that it will be useful, ++ but WITHOUT ANY WARRANTY; without even the implied warranty of ++ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ++ GNU General Public License for more details. ++ ++ You should have received a copy of the GNU General Public License ++ along with this program; if not, write to the Free Software ++ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ++ ++ ++Also add information on how to contact you by electronic and paper mail. ++ ++If the program is interactive, make it output a short notice like this ++when it starts in an interactive mode: ++ ++ Gnomovision version 69, Copyright (C) year name of author ++ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. ++ This is free software, and you are welcome to redistribute it ++ under certain conditions; type `show c' for details. ++ ++The hypothetical commands `show w' and `show c' should show the appropriate ++parts of the General Public License. Of course, the commands you use may ++be called something other than `show w' and `show c'; they could even be ++mouse-clicks or menu items--whatever suits your program. ++ ++You should also get your employer (if you work as a programmer) or your ++school, if any, to sign a "copyright disclaimer" for the program, if ++necessary. Here is a sample; alter the names: ++ ++ Yoyodyne, Inc., hereby disclaims all copyright interest in the program ++ `Gnomovision' (which makes passes at compilers) written by James Hacker. ++ ++ <signature of Ty Coon>, 1 April 1989 ++ Ty Coon, President of Vice ++ ++This General Public License does not permit incorporating your program into ++proprietary programs. If your program is a subroutine library, you may ++consider it more useful to permit linking proprietary applications with the ++library. If this is what you want to do, use the GNU Library General ++Public License instead of this License. +diff -uprN -X ../dontdiff linux-2.6.9/Documentation/filesystems/iriver.txt linux-2.6.9-iriverfs-stable/Documentation/filesystems/iriver.txt +--- linux-2.6.9/Documentation/filesystems/iriver.txt 1969-12-31 19:00:00.000000000 -0500 ++++ linux-2.6.9-iriverfs-stable/Documentation/filesystems/iriver.txt 2004-10-23 12:15:50.000000000 -0400 +@@ -0,0 +1,488 @@ ++------- ++License ++------- ++ ++Copyright (C) Geoff Oakham, 2004; <[EMAIL PROTECTED]> ++ ++This driver is free software; you can redistribute it and/or modify it under ++the terms of the GNU General Public License as published by the Free Software ++Foundation; only version 2 of the License. ++ ++This program is distributed in the hope that it will be useful, but WITHOUT ANY ++WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A ++PARTICULAR PURPOSE. See the GNU General Public License for more details. ++ ++You should have received a copy of the GNU General Public License in the files ++"COPYING" or "COPYING.iriverfs"; if not, write to the Free Software Foundation, ++Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ++ ++-------------------------- ++Release notes for iRiverFS ++-------------------------- ++ ++Oct 23, 2004 (version 0.1.0.1) ++ -fixed support for older and newer kernels (pre and post 2.6.8.1) ++ -made 'delta' more flexible in the data it accepts. (Backpatched ++ from the 'dev' branch.) ++ -more documentation of the USB timing bug. (See the developing ++ branch for more information.) ++ ++Oct 6, 2004 (version 0.1.0.0) ++ (no changes) ++ ++Oct 4, 2004 (version 0.1.0.0pre7) ++ -port to linux-2.6.9pre3 ++ ++Sep 30, 2004 (version 0.1.0.0pre6) ++ -gcc-2.95 preprocessor bug fix didn't make it into pre5. (Fixed) ++ -added support for renaming directories ++ -fixed a file renaming bug. (Involved moving files to or from '\') ++ -changed the public api for renaming files/directories ++ ++Sep 27, 2004 (version 0.1.0.0pre5) ++ -mount now returns 'busy' when the device fails startup test. (Of all ++ the error messages mount(5) returns, this one seems the best fitting.) ++ -fixed static linking (ie, non-module) the driver. ++ -fixed gcc-2.95 preprocessor bug ++ -added security options ++ -disabled directory renaming (Because it doesn't work.) ++ ++ -documented konqueror's chopy behaviour during file uploads ++ ++ (Footnote: there were several different patches in circulation ++ with the name 'pre5'. "pre5" and "pre5c" were private releases, ++ while "pre5b" was the official release.) ++ ++Sep 21, 2004 (version 0.1.0.0pre4) ++ -hot-unplugging is now handled gracefully. (Well, more graceful than segfaulting.) ++ -no longer attempts usb_reset() if the device is busy. ++ -"halted endpoints" are now checked for and handled. ++ -fixed 'du' problem ++ ++Sep 18, 2004 (version 0.1.0.0pre3) ++ -fixed segfault-on-insmod that existed in pre1 and pre2. (I left the ++ memory allocation debugging flag on, which doesn't play nicely with ++ kernels that aren't configured to support it. My bad.) ++ ++ -added kconfig dependency on 'experimental' and 'usb'. ++ ++Sep 14, 2004 (version 0.1.0.0pre2) ++ ++ -fixed bug in iriver_lookup: there was a problem when looking up ++ non-existant entries in unloaded directories. Test case: mkdir ++ /mnt/a/debug/d1/d5 (where d5 didn't exist before). ++ ++ -applied a temporary work-around that deals with usb_control_msg ++ returning '-EPIPE'. (See BUGS) ++ ++Sep 3, 2004 (Forth public release; first SourceForge release; version 0.1.0.0pre1) ++ ++ The biggest news is I've joined the ifp-driver project and this project ++ has become a package of ifp-driver. I owe a big thanks to Jun and the ++ ifp-driver mailing list for making it this far. ++ ++ From here, I hope to stabilize the codebase within a few releases and ++ fork the first 'stable' branch: ifp-linux-filesystem-0.1.0.0 ++ ++ ---------- ++ change log ++ ---------- ++ ++ -"find bug" squished ++ -"konqueror bug" and stability problems are gone ++ -data corruption -- missing; hopefully squished ++ -improved self-testing on mount ++ -new info I've code-named "delta" is printed on mount. (On my ifp5xx, ++ delta is always 1.8.6.22. I'm curious what other devices return.) ++ -more stack abuse eliminated ++ -more ifp-specific code removed from inode.c ++ -inode/dentry refrence counting fixed ++ ++ This release was tested with linux-2.6.8.1 ++ ++Aug 2, 2004 (Third public release) ++ ++ ---------- ++ change log ++ ---------- ++ ++ -[new!] File rename support. (Directory renaming is untested.) ++ ++ -reading mp3 files on old device is now possible if you rename ++ them. (In the future, the driver could do this automatically.) ++ ++ -improvements in stability and memory management. ++ ++ ---------------- ++ outstanding bugs ++ ---------------- ++ [For more details, see the 'bugs' section below.] ++ ++ -Using Konqueror locks up the system. [still] ++ ++ -Data corruption bug. (Rare, and relatively harmless for music.) ++ ++July 23, 2004 (Second public release) ++ ++ ---------- ++ change log ++ ---------- ++ ++ -Support for ifp7xx/8xx devices has been added. (Thanks to David for ++ pointing out this was missing, and then helping me fix it!) ++ ++ -"It seems there's a matter with df." [fixed] Thanks to Boris for ++ brining this to my attention. ++ ++ -Bug fixed that prevented a new directory from being created inside ++ another new directory. [found by David and Jim] ++ ++ -Stack abuse [using the kernel call stack to allocate large buffers] is ++ gone. [found by segfault] ++ ++ -CPU abuse fixed--driver now sleeps while waiting for flush() to ++ complete. ++ ++ -interal refactoring--I'm slowly separating kernel-specific code from ++ iFP-specific code. In the future, it might be possible for ifp-line ++ and this driver to share some source code. ++ ++July 14, 2004 (First public release) ++ ++ ------- ++ summary ++ ------- ++ ++ This driver mounts iRiver "iFP" mp3 players as filesystems. It is ++ intended as a replacement for iRiver's "Manager" software available for ++ other platforms. ++ ++ This project his reached "dogfood" status for me, so I'm releasing it ++ for public comment and [dis]approval. I haven't tested it with any ++ other computer or player, so I'd very much appreciate feedback from ++ others. ++ ++ I hope you find this useful, ++ ++ Geoff Oakham <[EMAIL PROTECTED]> ++ ++Requirements: ++ ++ -linux 2.6.x ++ -kernel sourcecode [enough to compile modules] ++ -development tools (gcc, etc.) ++ -iRiver flash player (aka "iFP") ++ -virtual memory, enough to temporarily hold entire files* ++ ++ This driver has been reported to work with iFP3xx, 5xx, 7xx and 8xx models. ++ ++* modern desktops shouldn't have a problem with memory use. This warning is ++ for people attempting to use this on a 486: you will need a swap partition.. ++ if not two. ++ ++BUGs & other unresolved problems: ++ ++ Konqueror's progress metre: ++ Currently, when Konqueror uploads files to the device, its ++ progress metre "jumps" after writing each file. The jerky ++ behaviour confuses Konqueror and prevents it from esitmating ++ the total transfer time. (Instead is displays "stalled".. ++ which is disconcerting to the user.) ++ ++ This is a quirk of the current implementation. It would be ++ possible (and relatively easy) to fix if someone discovered how ++ to append to exisiting files. (This would allow uploads to ++ happen in several steps, instead of all at once. That would ++ also mean the device wouldn't have to lock up during uploads.) ++ ++ [no intention of fixing.. see above discussion.] ++ ++ usb protocol stall: ++ It appears during large downloads on a moderately loaded system, ++ my ifp device does a "usb protocol stall". (This only happens ++ with my uhci host--my ohci host hasn't done this yet.) ++ ++ Details: ++ -when sending the 'DOWNLOAD' control message, the system ++ returns EPIPE, which in this context means "protocol stall" ++ (according to the USB spec, and I've verified with code ++ it isn't a functional staff.. aka 'halt'). ++ ++ -sleep()ing for a few cycles and re-issuing the control ++ code seems to work around the problem 90% of the time. ++ (At most.) ++ ++ -The other 10% of the time, we reach EOF one block ahead ++ of schedual. (To me, this means that one of those ++ control messages I presumed failed, succeeded eventually.) ++ ++ -According to the USB spec, 'protocol stall' is ++ supposed be returned when the command we sent isn't ++ valid. (Either the command or its parameters.) ++ ++ Thoughts: ++ I haven't seen a way for the device to tell us "wait, ++ I'm not ready to send you more data"; however, that's ++ supposed to be built-in to the usb protocol itself. ++ (On the other hand, they didn't appear to use this ++ feature for uploading.. but they might be buffering ++ data in RAM. *shrug*) ++ ++ A potential short-term solution is to pace requests for ++ data. (Ie cap our bandwidth usage.) ++ ++ [update oct 3, 2004] ++ Doesn't seem to be related to usb changes mentioned ++ below. ++ ++ [update oct 6, 2004] ++ In a discussion on linux-usb-devel, we suspect this ++ is a timing issue. Here's a quick test I ran: ++ ++ wall time | speed Bps | EPIPEs | changes <<Diff was trimmed, longer than 597 lines>> _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
