Our code to assign outputs to pipes isn't working at the moment. Outputs
stay assigned to whatever the BIOS has set up. I tried to fix this but
didn't find a way yet (only more black screens).
As a workaround, always set both pipes A and B to always point to the
same frame buffer. This gets the display running properly on my Haswell
machine again, however mode setting is still not possible (so you can
only use the mode set by the BIOS).
* beaglebone vs beagleboard
* While the boards are almost the same, they have
diff. FDT's now (more memory, different layout etc)
* Make u-boot script more rpi-like
(depend on u-boot for initial addresses)
* Wasn't working, still doesn't.
This change allows for the HaikuDepot desktop application to query the server application
over HTTP for data regarding packages across the various repositories that the have been
configured on the desktop environment. Previously it was 'hard-coded' to only
communicate about the HaikuPorts repository.
from a stock GDB source tree.
I was getting tired of doing it manually.
Note the prefix is not exactly the same as the buildtools since the
machine triplet is different, but it's not an issue.
Tested with arm and ppc with GDB 7.8. Might need patching gdbTarget for other archs,
as stock GDB doesn't know about Haiku.
* Remove enqueue_time again.
* Lateness seems generally useless. No way to get something useful
experimentally. The commit noise however was useful, the port wait is
behaving more in accordance with the lateness calculus.
* Fixes#12817 and possibly #12594.
* Commit 337c4ccf introduced usage of plain memcpy in
get_next_frame_no_debugger(), when the frame is already
known to be on the kernel stack. However, it also needs
to check that the end of the frame is still within the
stack bounds. Otherwise this can cause a KDL if bp does
not point to a valid complete frame anymore and is
near a page boundary. Although with commit e477b10c such
cases should already be avoided, it's still safer to
check this here in case of e.g. analyzing broken stacks.
* No need to continue walking the stack when a zero return
address is found, only bogus frames will follow
* Fixes KDLs seen when using the system profiler, due to
a bug that will be fixed in the next commit...
It appears this would only happen when opening a new window (not an
existing one) for a folder that was set to icon-view.
Regression from hrev48734 (Layout API commit). Fixes#13000.
Add missing "printchar.c", which is only used in DEBUG mode. The
function was recovered from original regex sources.
Note that the gnu regexp library is deprecated, and so is its
replacement, gnu rx. GNU suggests using the regex implementation from
the glibc, but that one isn't as portable.
Thanks to Andrew Lindesay for the investigations and initial patch!
Fixes#12952.
Removed the unneeded UI versions of Noto. According to the FAQ [1], those
"have tighter vertical metrics, and some glyphs that would be clipped are
redrawn to fit within the constrained space", which doesn't seem necessary
for Haiku. Could be re-added, of course, if it turns out otherwise...
Added Noto CJK fonts. All of them contain the glyphs for jp, kr, sc, tc.
Only differ in their default language.
Icon size is only a boolean here (true for a large icon, false
otherwise). Using B_LARGE_ICON directly is not appropriate.
As found by Murai Takashi, but there was a second case in the same file
which I also fixed.
ticket : #12955
As reported in #6301, some BIOSes rely on these byte to detect an unused
partition entry (set to 0) from an used one (set to some other value),
and only later notice that the CHS is invalid and LBA should be used.
Apply the patch that Ingo had attached to the ticket back then.
As far as I can tell, the protective MBR in GPT only happens to use the
same way to mark the partition as used (in case you try to plug a GPT
drive to a BIOS that does only CHS). So, using the same value should not
lead to the MBR being identified as a protective MBR by GPT aware
systems (that is detected using the partition type and partition size).
Fixes#6301.
This allows you to drag and drop list items more easily, but,
removes the ability to drag and drop color squares in Appearance from
one list item to another. Changing selected list items while dragging
was more of a helpful side-effect for Appearance but isless reasonable
default behavior.
Fixes#12990
Partially regression on #8618
