While struct tm makes things more confusing than they need to be,
nothing in the API prevents handling those. So let's just accept them.
Fixes some strange cases in the cookie test suite (with a cookie set to
expire in year 101 B.C.)
* We could also check to make sure it isn't 0xffff and
bail if it is... not really a solution but helps
prevent kdl's if our mapped memory is corrupted.
* That seems like more of a hack though, i'd like to
solve the real problem.
* Open the window a bit bigger so the scroll bar in the "Notifications"
view isn't activated.
* Make the window horizontally resizable.
* Sentence casing
This was hardcoded to pipe A on my laptop, but it's better to set both
pipes so it work in more cases.
Eventually I should see why my SandyBridge laptop is failing to move its
LVDS panel to pipe B...
This fixes miqlas Thinpad X200s and possibly some other machines. Thanks
for letting me experiment with the hardware!
Some libraries buildsystems (eg. zlib) somehow prevent the symbol from
being exported. We should fix that, but binaries with missing symbols
are already out there, so we need to handle them in any case.
* Seems more common to have > 16 USB ports on xHCI
hubs (18 on my XPS 13 root hub)
* This fixes 'hub supports more ports than we do' error
* The FreeBSD USB driver works a lot like ours and
sets the maximum USB ports on a hub to 255
* Doesn't solve #12885 but fixes one of the errors
The format for the .comment string changed at some point, and this
fallback code would always fail for files built only with "new" versions
of gcc.
Also consider gcc 5 to be ABI version 4, since it is still compatible
with the old ABI (and provides a new one side by side).
See https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html
for infos on GCC ABI changes in GCC 5.
I've no idea why this was what "save image" did, but apparently it's
done so since this code was imported into the trunk in the very first
commit. Now it saves PNGs, which is what users expect.
Fixes#5011.
Qt Creator now has a "generic project" mode, in which it just acts
as an auto-completing code editor. I tried using it on the entire
Haiku project at once, but it's just too much for Qt Creator to handle.
So instead, I created a script which generates project files for
any given directory in the tree, as well as sets up the proper include
directories. The project files themselves are .gitignore'd; use the script
to create them.
Works on Haiku. Did not test on Linux with a crosstools setup; but
it should work there too.
This however doesn't help with the 64bit float operations that
gcc emits when assigning the physical framebuffer address in kernel_args,
which is a packed struct...
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.
