nihilazo
/
rockbox
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
CONSTRUCTION AREA
35,677 Commits 1 Branch 0 Tags 176 MiB
C 88.8%
C++ 5.2%
Assembly 2%
TeX 1.5%
Lua 0.7%
Other 1.5%
Go to file
Aidan MacDonald 24294bda15 usb: ensure RX buffers are a multiple of the packet size 
When performing an OUT transfer which is not a multiple of the
max packet size, the last packet of the OUT transfer should be
a short packet. However, there's no guarantee the host sends
the expected amount of data in the final packet.

The DWC2 USB controller handles this case by accepting any size
packet and copying it out to memory. So if the packet is bigger
than expected, it'll overrun the caller's buffer and Bad Things
will happen.

The USB 2.0 spec seems to endorse this behavior. Section 8.5.1
says "an ACK handshake indicates the endpoint has space for a
wMaxPacketSize data payload." So it is possible that other USB
controllers share the DWC2's behavior.

The simplest solution is to force all USB RX buffers to be big
enough to hold the transfer size, rounded up to a multiple of
the max packet size. For example, a transfer of 700 bytes would
require a 1024-byte buffer if the MPS = 512 bytes.

Change-Id: Ibb84d2b2d53aec8800a3a7c2449f7a17480acbcf
 		2021-10-16 21:14:42 +01:00
android android: Fix configure script for "newer" versions of the NDK 2020-04-13 16:51:58 +02:00
apps Open_plugins.c bugfix address of packed struct element 2021-10-16 11:04:17 -04:00
backdrops New port: Shanling Q1 native 2021-07-13 22:01:33 +01:00
bootloader Sansa E200v1 Bootloader ensure USB unplug is detected 2021-10-04 16:42:36 -04:00
debian Prepare new maemo release 2013-03-10 12:12:38 +01:00
docs usb: introduce new control request API 2021-10-16 15:58:43 -04:00
firmware usb: ensure RX buffers are a multiple of the packet size 2021-10-16 21:14:42 +01:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb Nuke the never-functional iriver ifp-7xx port 2021-04-26 07:42:58 -04:00
icons Revert Non-Alpha Updated 8x8 tango icons 2020-10-25 16:21:58 +00:00
lib metadata/mp3data.c init vars & add sanity checks 2021-08-11 22:40:09 -04:00
manual Shanling Q1: minor update to keymap 2021-08-25 23:28:59 +01:00
packaging Prepare unofficial pandora release 2013-03-10 14:09:30 +01:00
rbutil Revert "rbutil: Remove done() signal from Themes Install window." 2021-08-04 19:10:34 +02:00
tools languages: Prefer the translated <dest> over a <voice> that is identical to English 2021-09-29 10:54:19 -04:00
uisimulator sim: change Eros Q native bitmap to a symlink 2021-07-18 14:15:25 +01:00
utils Remove the (very) incomplete port for the Tatung TPJ-1102 2021-08-14 16:29:39 -04:00
wps New port: Shanling Q1 native 2021-07-13 22:01:33 +01:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore jztool: New utility for installing a bootloader on FiiO M3K 2021-04-17 20:23:19 +00:00
.gitreview misc: Add a .gitreview file for better gerrit integration 2021-06-24 07:22:19 -04:00

docs/README 

               __________               __   ___.
     Open      \______   \ ____   ____ |  | _\_ |__   _______  ___
     Source     |       _//  _ \_/ ___\|  |/ /| __ \ /  _ \  \/  /
     Jukebox    |    |   (  <_> )  \___|    < | \_\ (  <_> > <  <
     Firmware   |____|_  /\____/ \___  >__|_ \|___  /\____/__/\_ \
                       \/            \/     \/    \/            \/

Build Your Own Rockbox

1. Clone 'rockbox' from git (or extract a downloaded archive).

   $ git clone git://git.rockbox.org/rockbox

     or

   $ tar xjf rockbox.tar.bz2

2. Create a build directory, preferably in the same directory as the firmware/
   and apps/ directories. This is where all generated files will be written.

   $ cd rockbox
   $ mkdir build
   $ cd build

3. Make sure you have mips/m68k/arm-elf-gcc and siblings in the PATH. Make sure
   that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
   a particular version depending on what player you are compiling for. These
   can be generated using the rockboxdev.sh script in the /tools/ folder of the
   source.

   $ which arm-elf-eabi-gcc
   $ which perl

4. In your build directory, run the 'tools/configure' script and enter what
   target you want to build for and if you want a debug version or not (and a
   few more questions). It'll prompt you. The debug version is for making a
   gdb version out of it. It is only useful if you run gdb towards your target
   Archos.

   $ ../tools/configure

5. *ploink*. Now you have got a Makefile generated for you.

6. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

   $ make
   $ make zip

7. unzip the rockbox.zip on your music player, reboot it and
   *smile*.

If you want to build for more than one target, just create several build
directories and create a setup for each target:

   $ mkdir build-fuzeplus
   $ cd build-fuzeplus
   $ ../tools/configure

   $ mkdir build-xduoox3
   $ cd build-xduoox3
   $ ../tools/configure

Questions anyone? Ask on the mailing list or on IRC. We'll be happy to help you!