Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 4 and Version 5 of Ticket #415


Ignore:
Timestamp:
2012-03-06T13:35:14Z (8 years ago)
Author:
Jiri Svoboda
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #415 – Description

    v4 v5  
    22
    33 Details::
    4   The current ```ata_bd``` driver is in fact a service spawned by the user when he/she needs to use the ATA block devices. The driver can handle ATA disks and ATAPI CD-ROMs. It supports CHS, 28-bit and 48-bit LBA addressing and only uses PIO transfers. There is no support for DMA, the PACKET feature set or any other fancy features such as S.M.A.R.T, removable devices, etc. The driver services a single controller which can have up to two disks attached. The current driver is ISA-based.
     4  The current ```ata_bd``` driver is in fact a service spawned by the user when he/she needs to use the ATA block devices. The driver can handle ATA disks and ATAPI CD-ROMs, to some degree. It supports CHS, 28-bit and 48-bit LBA addressing and only uses PIO transfers. There is no support for interrupts, DMA or any other fancy features such as S.M.A.R.T, removable media, etc. One invocation of the driver services a single controller on one of the four standard I/O base addresses, which can have up to two disks attached. The current driver is ISA-based.
    55
    6   The goal of this ticket is to use the old driver as an inspiration / foundation for the new driver, which should be implemented as a new driver process using the HelenOS Device Driver Framework (DDF). The new driver should be at least equally capable as the old one and could be perhaps further enhanced to support e.g. PCI and DMA. By virtue of being a DDF driver, there will be no limit on the number of supported controllers as all controllers will be discovered automatically and paired with the driver by DDF.
     6  The goal of this ticket is to use the old driver as an inspiration / foundation for the new driver, which should be implemented as a new driver process using the HelenOS Device Driver Framework (DDF). The new driver should be at least equally capable as the old one and could be perhaps further enhanced to support e.g. PCI, interrupts and DMA. By virtue of being a DDF driver, there will be no limit on the number of supported controllers as all controllers will be discovered automatically and paired with the driver by DDF.
    77
    88 What Gains and Benefits will this bring?::