On Tue, Dec 21, 2010 at 12:26 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > So what's the actual shared code with older megaraid_sas adapters after > this? It looks to me like you should simply add another driver for the > new hardware. > Christoph, The shared code with older megaraid_sas driver is all of the following functions: megasas_get_cmd() megasas_return_cmd() megasas_issue_polled() megasas_issue_blocked_cmd() megasas_issue_blocked_abort_cmd() megasas_is_ldio() megasas_queue_command() megasas_lookup_instance() megasas_slave_configure() megaraid_sas_kill_hba() megasas_check_and_restore_queue_depth() megasas_reset_timer() megasas_reset_bus_host() megasas_bios_param() megasas_service_aen() megasas_slave_alloc() megasas_complete_int_cmd() megasas_complete_abort() megasas_complete_cmd() megasas_transition_to_ready() megasas_teardown_frame_pool() megasas_create_frame_pool() megasas_free_cmds() megasas_alloc_cmds() megasas_get_pd_list() megasas_get_ld_list() megasas_get_ctrl_info() megasas_get_seq_num() megasas_register_aen() megasas_start_aen() megasas_io_attach() megasas_set_dma_mask() megasas_shutdown_controller() ... several more The new adapter needs about 4k of code that is in the existing driver. That is why we made this a combined driver. -Adam -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
