search for: debug_mode

rakewx.rb: - Added a $debug_build variable so when we do eventually we can also release non debug builds. I did not make this a constant on purpose so in the package tasks we can change it to false if we want to always make non debug builds by default. - Changed wx_config to use the $debug_build variable rakemswin.rb: - Updated the copyright year. - removed the $DEBUG const and make use of

...bdev/secboot.h index 24d98878bb93..785e2c553392 100644 --- a/drm/nouveau/include/nvkm/subdev/secboot.h +++ b/drm/nouveau/include/nvkm/subdev/secboot.h @@ -30,6 +30,7 @@ * @base: base IO address of the falcon performing secure boot * @managed_falcons: bitfield of falcons managed by this ACR * @debug_mode: whether the debug or production signatures should be used + * @wpr_set: whether the WPR region is currently set */ struct nvkm_secboot { const struct nvkm_secboot_func *func; @@ -44,6 +45,8 @@ struct nvkm_secboot { u32 wpr_size; bool debug_mode; + + bool wpr_set; }; #define nvkm_secboo...

...recycled object (My guess is that its asking for junk Memory Address). Here''s the relevant code and error. The exception is being thrown on the last line of the code: producer_args = {:report_id => report.id, :args => YAML.load(report.args)} producer_args.merge!(:debug_mode => true) if @debug_mode task.middleman.new_worker(:class => "#{task.worker_name}_#{TaskManager::Task::WORKER_POSTFIX}".to_sym, :job_key => producer_key, :args => producer_args )...

...t respond. I can see that mongrel is still running if I to a (ps -A). Running (top) shows that mongrel is consuming around 34M of memory and using no .01% CPU. I''m running mongrel in development mode, yet no entries are making it to (deveopment.log). I''m also running mongrel in debug_mode and no entries are being added to any of the log files in the mongrel_debug directory. BTW, I am running mongrel on port 50042 because this is the port I''ve been given permission to run Mongrel on. 2) After hitting mongrel with a bunch of (curl locahost:50042) calls, I did (lsof -i -P...

This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send the code to manage then, but hopefully the

This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send the code to manage then, but hopefully the

This revision includes initial signed PMU firmware support for GM20B (Tegra X1). This PMU code will also be used as a basis for dGPU signed PMU firmware support. With the PMU code, the refactoring of secure boot should also make more sense. ACR (secure boot) support is now separated by the driver version it originates from. This separation allows to run any version of the ACR on any chip,

Hi everyone, Apologies for the big patchset. This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send