Now lcd_framebuffer is the only framebuffer in the system. We still use a ARM-buffered buffer
which serve as an intermediate buffer for copying, to accomodate the requirement of the controller.
We implement lcd_update_rect() properly using this new scheme (this requires two little quirks),
this allows to implement lcd_blit_yuv with the right semantic (bypasses the framebuffer). YUV to RGB
conversion is still done in software but the DCP CSC should be able to do that but the hardware rotation
scheme is not the same as our software so it will require some tricks.
Change-Id: I0752e9c2f1a705d2e6a6010084e1f150965d8370
The old touchscreen_get() needed an external button_get() call. Now two APIs are
added that do this call internally. This way they behave similar to get_action.
The old API is preserved (but renamed) since it's used in reversi.
Change-Id: I24902c64a357f2fdd7d0c2f5371cbfd20f34f1c8
Plugins revert to grid mode currently. If they create a list the list ends
up in grid mode as well even if they use point mode due to settings in the core.
The expectation is that the lists use whatever mode they also use in the core.
Force setting in menu to have them behave the same in core and plugins.
Change-Id: I9534b2f21ccfa920eb2e48f66b04ecbda7a59011
Ubuntu defines _FORTIFY_SOURCE=2, which causes glibc longjmp() to check sp
when gcc optimization is enabled. The check does not allow longjmp() to be
used for switching threads and results in a "longjmp causes uninitialized
stack frame" error. This disables the check.
Change-Id: Idb8877b43ce711df880ca88875ba5477445a577a
Hoshi locations were hardcoded and only for board sizes 9, 13 and 19.
This new way has identical results for those board sizes, but
also places hoshi on other size boards.
There are no real standards for where hoshi should go on boards other
than 9, 13 and 19, but I think the results obtained are aesthetically
pleasing (and certainly better than not having any hoshi at all).
Change-Id: I08e449f17d782d212d5b1e16ebd7df52aec9ffb9
Reviewed-on: http://gerrit.rockbox.org/68
Reviewed-by: Björn Stenberg <bjorn@haxx.se>
Reviewed-by: Frank Gevaerts <frank@gevaerts.be>
ata_removable() and ata_present() no longer exist (ATA drives are never
removable with our current drivers), so storage.c shouldn't try to call
them from the wrapper functions. This was never noticed because these
wrapper functions are only used for multidriver code, which happens not
to be used with ATA currently.
Change-Id: Icb5e8cb27cdbef3edc0e51c35dc40dadf4f9de29
Use two stage amplification (PGA gain and digital stage gain)
combined to extend recgain range to -17.25 +60.0dB.
Change-Id: I4df8af801730b7efb2d35096de077ba31d331222
Scrollstrip (as well as scrollwheel on ipods/sansas) works like
quadrature encoder. The states of input lines are tracked by the
gpio ISR and when the sequence is correct, appropriate button
event is pushed to the button queue directly. The downside of
this implementation is that scrollstrip doesn't emit _REL
events which has some weird consequences. For the scrollwheels
some hack have been crafted in action system to accomodate for
this. I don't like this approach. IMO the correct fix is to
properly emit _REL event when the user stops interacting with
the device or reverses the direction of the move. This patch
implements timeout which forces to emit _REL when expired.
Change-Id: I588ac5810dd2ab00c68935d23a62979cb1c2a912
Reading from /dev/r0Btn only allowed to read one button at a time. Reading GPIO
directly via ioctl() doesn't have this limitation.
This adds a more complete GPIO list also.
Change-Id: If47b0846472f0817305dbf930731255f875e0269
Author: Lorenzo Miori
Retrieve the processes running at startup and compare with a list of
potentially problematic ones. Right now this is Itunes which is known to be
able to cause problems when trying to install the bootloader on an Ipod. No
user notification yet.
This adds the implementation for Windows.
Change-Id: I5ce8a85da52e0ed8f523b5ae6fb5d8f14f6a14c9
Change the none action return value so the various action layers don't get confused by ACTION_TOUCHSCREEN return codes which shouldn't be happening (i.e when a long press region overlaps a short press region whihc has the none action)
Change-Id: I63db2c0b49597ada2c5ebd0ef98e99aeef4f522a
The SSND bit is intended to be right after the t_aiff-sized header.
Someone got cast vs + precedence rules wrong here.
Change-Id: Iccec75043ed5e35724331f9833b24f7e3b90c447
