R-BENADJILA

R-BENADJILA pushed to nexus6 at T-TROUCHKINE/garp

  • 505a530dbb Make the script to reset USB device more flexible (add a name parameter as ARG1).

8 years ago

R-BENADJILA pushed to nexus6 at T-TROUCHKINE/garp

  • a964bfc8fb Small fix in the USB reset script (base dir).

8 years ago

R-BENADJILA pushed to nexus6 at T-TROUCHKINE/garp

  • 4f61a85099 Add a software way to reset USB device connection to the host.

8 years ago

R-BENADJILA pushed to nexus6 at T-TROUCHKINE/garp

  • 04f49ff0eb New config for Nexus6 that removes the annoying automatic Power Management of SoC Idle states.

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

  • be9076f084 Add a toy example of creating a Kernel thread and pinning/migrating it on a specific CPU (this will be useful to perform fault attacks).

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

  • 5fd1e3e6be The 'find.py' hack should not be needed anymore thanks to our symbol introspection from inside the kernel module!

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

  • d19477aa26 Some cleanup of trash files from git.

8 years ago

R-BENADJILA pushed to master at T-TROUCHKINE/garp

  • 26718e59d9 Initial commit for the Garp project. Everything should be here to compile the kernels and driver for Nexus4 and Nexus5. The Makefile should generate the following targets (where X is either 4 or 5): $ make init => initalize everything (kernel sources, toolchains, boot images). $ make NexusX_kernel => compile the kernel for NexusX. $ make NexusX_kernel_clean => clean the kernel for NexusX. $ make NexusX_driver => compile the driver for NexusX. $ make NexusX_driver_clean => clean the driver for NexusX. $ make NexusX_bootimg => generate the boot image for NexusX. $ make mrproper => clean everything and reset the folder to its initial state. The produced boot image and driver are places in the 'build' folder, and are ready to be pushed on the target.

8 years ago