From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shreyansh Jain Subject: Re: [PATCH v4 00/17] Introduce SoC device/driver framework for EAL Date: Sat, 15 Oct 2016 19:23:15 +0530 Message-ID: References: <1473410639-10367-1-git-send-email-shreyansh.jain@nxp.com> <1476539108-13170-1-git-send-email-shreyansh.jain@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , To: Return-path: Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0082.outbound.protection.outlook.com [104.47.38.82]) by dpdk.org (Postfix) with ESMTP id 5AE5072FA for ; Sat, 15 Oct 2016 15:51:52 +0200 (CEST) In-Reply-To: <1476539108-13170-1-git-send-email-shreyansh.jain@nxp.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Saturday 15 October 2016 07:14 PM, Shreyansh Jain wrote: [...] > > 4) Design considerations that are same as PCI: > - SoC initialization is being done through rte_eal_init(), just after PCI > initialization is done. > - As in case of PCI, probe is done after rte_eal_pci_probe() to link the > devices detected with the drivers registered. > - Device attach/detach functions are available and have been designed on > the lines of PCI framework. > - PMDs register using DRIVER_REGISTER_SOC, very similar to > DRIVER_REGISTER_PCI for PCI devices. > - Linked list of SoC driver and devices exists independent of the other > driver/device list, but inheriting rte_driver/rte_driver, these are > also part of a global list. > [...] Two points which I missed in the Cover letter: 1. DRIVER_REGISTER_* has been replaced with RTE_PMD_REGISTER_*. 2. This is an experimental series. Verification of this has been done using NXP's PMD (to be published on ML soon) without using default scan/match helpers. - Shreyansh