* Confirmed this places pins in miniUART mode
(we don't want this mode however)
* We do need to fully understand *which* mode
the pins need to be in for PL011 mode.. however
the boot state of the Pi is PL011
* More general tab title "Decorators"
* Sentence casing "Window decorator:". Here the "Window" is OK,
there could be "OSD decorators" etc. in the future.
Let's say the timer is waken up when its hook is called. This patch
reduces ~41% wakeups during idle
Signed-off-by: Fredrik Holmqvist <fredrik.holmqvist@gmail.com>
* When the color of the "current color" swatch view
(the bigger one) changes because of a color drop, adopt the
new color just like when changing the color via other means.
* Remove the reference to BString::fPrivateData, as it currently really
is marked as private and as such disappeared from the docs.
* Add the various character methods that have been added in the
previous revisions.
* while it seemed to work before, BuildSetup was actually adding includes from the default boot platform, before BoardSetup had a chance of changing it.
Some issues in the Czech.keymap were discovered while creating
the Czech (Mac).keymap. These include the RCommand key not being
set, extra spaces in the option map, and characters defined in
0x7e and 0x7f which correspond to the sysreq and break keys.
* Enable/Disable makes more sense and matches
platform loader serial functions.
* Rework PL011 code after finding a PDF covering
the details of it.
* Rename UART global defines in loader to be more
exact about location
* This makes things a little more flexible and
the interface to use the uarts cleaner.
* May want to make a generic Uart wrapper
class in uart.h / uart.cpp and call drivers
as needed from there.
Top was using the 'theorical' interval value to determine the percentages.
The measured thread times were taken in an always a bit larger interval than
that theorical value, hence the negative '%' occuring regularly.
Should fix#4589.
fBackgroundImage wasn't being cleared when removing the desktop
background image because the loading process wasn't ignoring
loading failures (as is the "no background for this workspace" setting).
fBackgroundImage not being NULL was causing crashes mainly in
ScreenChanged(), where it was trying to re-center a non-existant
background. Was causing #7376 and maybe others.
In List Mode, consider the extra margin added to the right of
the last column when computing the Extent of the PoseView. This
was causing the ResizeToFit to resize a bit too small.
Fixes#4318
* Avoid name collisions
* This uart stuff may work better as a class at
some point, however I didn't want to rock the
u-boot boat *too* much as I don't have the
hardware to test.
* Add nested function wrappers to allow usage of other
uart drivers depending on board. We may want to use this
on other platforms at some point (haha, maybe)
In previous, it was still working as I was more interested into != 0 than
exact count. Still, for clarity sake, I add -l to get the actual count.
Thanks Axel.
* Thanks go out to Simon Arlott for replacing
the first32k.bin blob with assembly removing
the need for first32k.bin hack.
* This assembly is a modified version removing
the Linux kernel boot args.
* haiku_loader renamed to kernel.img will boot
on Raspberry Pi directly.
* Called mvattr, move is not yet implemented which is why it's not part of
the image yet.
* Defaults to rename, moving attributes needs an extra option.
* Suggestions welcome :-)
* The ShapeListView also knows the PathContainer and StyleContainer
* When constructing the drag message, also include a complete archive
of the dragged shapes, bundled with archives for each included path
and the style.
* When handling the drop, and it came from another I-O-M window,
exract the Shape archive bundle from the drag message. For the
Style and the included Paths, try to find an existing Style and
existing Paths and reference those in the added Shape(s) instead
of adding duplicates.
The bash script tried to verify the existence of a file,
but there were several fils fitting the wildcard expression.
So, [ -e .../*gcc ]; was interpreted as if it had too many
arguments. Replaced that expression by a count of files.
Fixes#8493.
