mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 06:37:43 +00:00
Kernel/AHCI: Don't enable interrupts in the AHCIPort constructor
On my bare metal machine, enabling it as this point causes it to instantly send an interrupt, and we're too early in the process to be able to handle AHCI interrupts. The interrupts were being enabled in the initialize function anyway. Confirmed to happen on: - 8086:9ca2 (Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)) - 8086:3b22 (Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06))
This commit is contained in:
parent
f255993349
commit
84fc498b9f
1 changed files with 0 additions and 2 deletions
|
@ -50,8 +50,6 @@ AHCIPort::AHCIPort(const AHCIPortHandler& handler, volatile AHCI::PortRegisters&
|
|||
}
|
||||
m_command_list_region = MM.allocate_kernel_region(m_command_list_page->paddr(), PAGE_SIZE, "AHCI Port Command List", Region::Access::Read | Region::Access::Write, Region::Cacheable::No);
|
||||
dbgln_if(AHCI_DEBUG, "AHCI Port {}: Command list region at {}", representative_port_index(), m_command_list_region->vaddr());
|
||||
|
||||
m_interrupt_enable.set_all();
|
||||
}
|
||||
|
||||
void AHCIPort::clear_sata_error_register() const
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue