Development

ohci: Fix x86_64 usb tracing

Source Activity - Sat, 2016-04-23 19:26
Categories: Development

xhci: 1.1 spec actually specifies 1023 maximum scratch pads.

Source Activity - Sat, 2016-04-23 18:00
* While my test XHCI machine only requested 36, the spec for 1.1 actually states the controller can now "request up to 1023" * While my test XHCI machine only requested 36, the spec for 1.1 actually states the controller can now "request up to 1023"
Categories: Development

Ticket #12728 (xhci: invalid max scratchpad) closed

Latest Bugs & Tasks - Sat, 2016-04-23 17:57
fixed:

resolved via hrev50246.

1.1 spec bumped to 36. We actually are looking at number of scratch pads, but we had a low limit of 32 (which was the actual 1.0 count)

hrev50246 increased the maximum to a sane 48

Categories: Development

intel_extreme: Disable register dumps

Source Activity - Sat, 2016-04-23 14:13
* Could cause instability in rare cases. * Could cause instability in rare cases.
Categories: Development

Ticket #12728 (xhci: invalid max scratchpad) created

Latest Bugs & Tasks - Sat, 2016-04-23 05:06

In our driver, xhci scratchpads are fixed number, while later xhci 1.1 specs bumped them up. This results in an "Invalid number of scratchpads" error at boot.

xhci scratchpads need to be variable:

​https://www.coreboot.org/pipermail/seabios/2015-August/009627.html

​http://permalink.gmane.org/gmane.linux.usb.general/116329

XHCI_MAX_SCRATCHPADS

Categories: Development

[haiku-development] Re: Haiku network booting and packagefs

Development mailing list - Sat, 2016-04-23 00:45
OnWed,Mar30,2016at09:00:17AM+0200,IngoWeinholdwrote: methodisBOOT_METHOD_NETandinthiscasedeterminewhetherthe just-mountedbootvolumelookspackaged(thebootloaderonlychecksforthe existenceof/system/packages,sothatshouldbegoodenough). Thereisalreadyanlstatcallthere,soImodifiedtheconditionto testforeitherBOOT_VOLUME_BOOTED_FROM_IMAGEorBOOT_METHOD_NET.Ialso neededtoaddpackagefstothetgzarchivesoitcouldbeusedtomount thepackages. ...
Categories: Development

x86/kernel: Up kernel max page table to 16

Source Activity - Sat, 2016-04-23 00:05
* New Intel SkyLake seems to have 9 mapped ranges at boot. It seems like this define has been creeping up for a while. * Resolves the inital issue reported in #11377 on SkyLake as well. Bonefish mentioned it might need to be raised again... he had some good foresight there :-) * I'm seeing the same no bootable partitions issue though via USB after this raise. (maybe a USB 3.1 thing?) * New Intel SkyLake seems to have 9 mapped ranges at boot. It seems like this define has been creeping up for a while. * Resolves the inital issue reported in #11377 on SkyLake as well. Bonefish mentioned it might need to be raised again... he had some good foresight there :-) * I'm seeing the same no bootable partitions issue though via USB after this raise. (maybe a USB 3.1 thing?)
Categories: Development

bluetooth: Re-introduce to image

Source Activity - Fri, 2016-04-22 19:55
* Previous enablement broke gcc2 and hybrid builds * gcc2 builds fixed and tested working now * Fix Hybrid builds via missing MultiArch Jam * Sorry for the noise, enjoy early Bluetooth support * Previous enablement broke gcc2 and hybrid builds * gcc2 builds fixed and tested working now * Fix Hybrid builds via missing MultiArch Jam * Sorry for the noise, enjoy early Bluetooth support
Categories: Development

shutdown_media_server: Rely on actual instance

Source Activity - Fri, 2016-04-22 13:33
* Makes the shutdown process to rely on the instance that was running at the time the function is called. While it's unlikely anyone will see any change from that, this way we will not conflict in any case with the launch_daemon. * The reply could have been confused in a remote situation, make every request to use an it's own object. * In launch_media_server there was a wrong variable redefinition too. * Makes the shutdown process to rely on the instance that was running at the time the function is called. While it's unlikely anyone will see any change from that, this way we will not conflict in any case with the launch_daemon. * The reply could have been confused in a remote situation, make every request to use an it's own object. * In launch_media_server there was a wrong variable redefinition too.
Categories: Development
Syndicate content