coreboot/payloads/libpayload
Julius Werner e39e2d8476 libpayload: Make USB transfer functions return amount of bytes
The USB bulk and control transfer functions in libpayload currently
always return 0 for success and 1 for all errors. This is sufficient for
current use cases (essentially just mass storage), but other classes
(like certain Ethernet adapters) need to be able to tell if a transfer
reached the intended amount of bytes, or if it fell short.

This patch slightly changes that USB API to return -1 on errors, and the
amount of transferred bytes on successes. All drivers in the current
libpayload mainline are modified to conform to the new error detection
model. Any third party users of this API will need to adapt their
if (...<controller>->bulk/control(...)) checks to
if (...<controller>->bulk/control(...) < 0) as well.

The host controller drivers for OHCI and EHCI correctly implement the
new behavior. UHCI and the XHCI stub just comply with the new API by
returning 0 or -1, but do not actually count the returned bytes.

BUG=chrome-os-partner:16957
TEST=None
BRANCH=None

CQ-DEPEND=CL:59674

Change-Id: Ic2ea2810c5edb992cbe185bc9711d2f8f557cae6
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/48308
Reviewed-by: Gabe Black <gabeblack@chromium.org>
Reviewed-by: Stefan Reinauer <reinauer@google.com>
Tested-by: Gabe Black <gabeblack@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
2013-06-24 14:03:27 -07:00
..
arch libpayload: Clean up CFLAGS 2013-06-20 17:49:58 -07:00
bin libpayload: Drop PowerPC architecture 2013-06-13 15:50:38 -07:00
configs libpayload: Make the region to scan for the cb tables configurable. 2013-06-20 02:14:21 -07:00
crypto libpayload: fix wrong endian assumption in sha1.c 2013-06-13 17:21:22 -07:00
curses PDCurses: pdcscrn.c: Use #ifdef instead of #if CONFIG_SPEAKER 2013-04-01 23:24:38 +02:00
drivers libpayload: Make USB transfer functions return amount of bytes 2013-06-24 14:03:27 -07:00
include libpayload: Have similar cache api on ARM and x86 2013-06-20 18:52:16 -07:00
libc libpayload: fix size_t handling 2013-03-26 19:35:28 +01:00
libcbfs libpayload: expose cbfs ram functions 2013-05-24 16:27:51 -07:00
liblzma libpayload: Don't do unaligned accesses during LZMA decompression 2013-03-13 23:42:09 +01:00
libpci libpayload: minor cleanups 2012-04-04 00:40:31 +02:00
sample fix compilation of hello.elf example payload. 2010-08-28 23:23:47 +00:00
tests libpayload: initial test case + tiny "framework" 2013-03-22 00:35:32 +01:00
util libpayload: Fix xcompile 2013-05-21 20:14:26 -07:00
Config.in libpayload: Drop PowerPC architecture 2013-06-13 15:50:38 -07:00
Doxyfile Run doxygen -u on doxygen configuration files 2010-06-28 10:40:38 +00:00
LICENSES Since some people disapprove of white space cleanups mixed in regular commits 2010-04-27 06:56:47 +00:00
Makefile libpayload: Drop PowerPC architecture 2013-06-13 15:50:38 -07:00
Makefile.inc libpayload: Clean up CFLAGS 2013-06-20 17:49:58 -07:00
README libpayload, superiotool: README: Prepend coreboot/ to path of change directory line 2013-04-04 17:22:15 +02:00

-------------------------------------------------------------------------------
libpayload README
-------------------------------------------------------------------------------

libpayload is a minimal library to support standalone payloads
that can be booted with firmware like coreboot. It handles the setup
code, and provides common C library symbols such as malloc() and printf().

Note: This is _not_ a standard library for use with an operating system,
rather it's only useful for coreboot payload development!
See http://coreboot.org for details on coreboot.


Installation
------------

 $ git clone http://review.coreboot.org/p/coreboot.git

 $ cd coreboot/payloads/libpayload

 $ make menuconfig

 $ make

 $ sudo make install (optional, will install into /opt per default)

As libpayload is for 32bit x86 systems only, you might have to install the
32bit libgcc version, otherwise your payloads will fail to compile.
On Debian systems you'd do 'apt-get install gcc-multilib' for example.


Usage
-----

Here's an example of a very simple payload (hello.c) and how to build it:

 #include <libpayload.h>

 int main(void)
 {
     printf("Hello, world!\n");
     return 0;
 }

Building the payload using the 'lpgcc' compiler wrapper:

 $ lpgcc -o hello.elf hello.c

Please see the sample/ directory for details.


Website and Mailing List
------------------------

The main website is http://www.coreboot.org/Libpayload.

For additional information, patches, and discussions, please join the
coreboot mailing list at http://coreboot.org/Mailinglist, where most
libpayload developers are subscribed.


Copyright and License
---------------------

See LICENSES.